Convert to SSO account

Convert Document360 account to SSO account

Single Sign-On or SSO allows user authentication and access to multiple applications or websites with a single login event. You can login to your SSO account with your SSO credentials to access the portal/site. You can easily convert your Document360 account(s) to SSO account(s) without altering the roles and access. This option simplifies and speeds up the conversion process for users and readers.

NOTE

User type conversion is applicable only in SAML and OpenID configured projects.

Converting regular Document360 users to SSO accounts

1. Navigate to Settings () in the left navigation bar in the Knowledge base portal.

2. In the left navigation pane, navigate to Users & permissions > Users.

3. Select the checkbox of the desired users.

4. Click the Convert to SSO account option above the list of users.

   

   An Account convert confirmation popup appears.

5. Select the checkbox and click the Yes button.

   

NOTE

• When a user is converted to an SSO account, all their contributions will be retained. However, the previous contributions of the user will appear as Anonymous.

• The User that performs the conversion cannot convert their own Document360 account to SSO account.

• If you convert a Document360 owner account to SSO account, both the regular Document360 account and the SSO account will be available to that owner account. As a result, there will be two accounts for the same user.

• Users must be added and configured as SSO accounts in Document360 with the appropriate access permissions for successful login.

Converting regular Document360 readers to SSO readers

1. In the left navigation pane, navigate to Knowledge base site > Users & permissions > Readers & groups > Readers.

2. Select the checkbox of the desired readers.

3. Click the Convert to SSO account option above the list of readers.

   

   An Account convert confirmation popup appears.

4. Select the checkbox and click the Proceed button.
   

   

NOTE

SSO account cannot be converted to Document360 account.

Troubleshooting

If you encounter any issue during SSO login after converting users, refer to the following common error and its solution:

Failed to parse token response body as JSON

Error: An error was encountered while handling the remote login. Failed to parse token response body as JSON. Status Code: 200. Content-Type: text/html; charset=UTF-8. SSO authentication may fail during login between Document360 and the Identity Provider (IdP) if the client credentials are sent in a format that the IdP does not support.

Steps to resolve:

To resolve this issue,

Verify IdP support for client authentication method

1. Check the supported client authentication methods in your Identity Provider (IdP).

2. Ensure that the method used by Document360 is supported.

   In some cases, SSO authentication may fail if the client credentials are sent in the request body but the IdP does not support this method. For example, enabling support for client_secret_post in the IdP configuration can resolve such issues.

Update IdP configuration

1. If the IdP does not support credentials in the request body, enable support for client_secret_post

2. Save the updated configuration in your IdP.

3. Attempt to log in again using SSO after updating the configuration.

Following the above steps should resolve the issue.