Troubleshoot issues with Okta integration on Hexnode UEM

1. Error 404 page not found.

Description:

Error message displayed when the user tries to self-enroll their devices in Hexnode using Okta credentials.

Probable cause:

This error might occur if while integrating Okta with Hexnode, domain name might have been specified in the incorrect format portal name-admin.okta.com.

Possible solution:

You need to delete the previous Okta domain configured in Hexnode and reconfigure Okta domain again in Hexnode, and make sure that the domain name is in the format “portal name.okta.com”.

2. No browsers detected! Install one to complete authentication to enroll in Hexnode.

Description:

This error message is displayed while trying to self-enroll Samsung Knox device/devices enrolled in Android Enterprise as Device Owner.

Probable cause:

Case 1: In case of Samsung Knox devices, you might get this error during Self-enrollment using Okta authentication if you have enabled the option Disable system applications in the Samsung Knox portal while configuring the Device Owner profile.

Case 2: In case of devices enrolled under Android Enterprise as Device Owner, you might get this error while self-enrolling using Okta credentials, if you have disabled Enable system applications in Enroll > Platform-Specific > Android > Android Enterprise.

Probable solution

Case 1: For Samsung Knox devices, Disable the option Disable system applications in the Samsung Knox portal while configuring Device Owner profile.

Case 2: For Android Enterprise devices, Enable the option Enable system applications in Enroll > Platform-Specific > Android > Android Enterprise in the Hexnode UEM portal.

3. This Okta user does not exist. Please contact your administrator.

Description:

This error message is displayed when an admin technician attempts to log in to Hexnode UEM portal using Okta credentials, despite having enabled SSO login with Okta.

Probable cause:

The reason for this error could be that the technician account, with which you are attempting to sign in, is not associated with the Okta domain that is linked with Hexnode.

Probable solution

Ensure that the technician account you are using is associated with the currently configured Okta domain and, verify that the “Okta” option under “Allowed SSO logins” is checked. Navigate to Admin > Technician and Roles > Global SSO Login Settings > Allowed SSO logins. Under Allowed SSO logins, check Okta to enable it.

4. Sync error! The API token associated with the Okta account is no longer valid.

Description:

This error message is displayed when the Hexnode technician tries to sync Okta domain with the Hexnode portal.

Probable cause:

The possible reasons for this error could be:

• The API token used for configuring Okta domain in Hexnode might have expired.
• The API token used for configuring Okta domain in Hexnode could have been deleted.

Probable solution

Login to your Okta account with required privileges to create API token (Security > API > Tokens > Create token) and upload the token back in Hexnode portal (Admin > Okta > Token).

5. Sync error! The Okta account used for the configuration no longer has administrator privileges.

Probable cause:

The possible reasons for this error could be:

Case 1: The user account which was used to configure Okta in Hexnode could have been deleted from the Okta domain.

Case 2: The role of the user account that was previously used to configure Okta in Hexnode might have been changed.

Probable solution

Case 1: If the user account which was previously used to configure Okta in Hexnode is deleted, then delete the Okta domain from the Hexnode portal and reconfigure Okta in Hexnode with any other user account which has the required admin privileges.

Case 2: If the user account used to set up Okta in Hexnode had its roles changed, then assign it back to the role with administrator privileges that was previously used for Okta configuration.