Okta Verify authentication issues when users sign in from WebView If the same Okta Verify account is used in a different user profile, the authentication fails. When a Windows device has multiple operating system (OS) user profiles and the same account is added to Okta Verify on several user profiles, the most recent enrollment by the last user profile works. Okta Verify authentication issues when users have multiple OS profiles This only affects Safari users with macOS Big Sur and earlier. Users don’t receive device lifecycle messagesĭevice lifecycle messages aren't available on macOS devices that use an SSO extension profile. Solution: The user must restart Okta Verify. Apple has fixed the issue for macOS Monterey. This is a known issue for macOS Big Sur and earlier. MacOS occasionally fails to prompt users for Touch ID when they authenticate with Okta Verify Solution: Click the Sign in with your browser instead link to access the app. Okta Verify single sign-on (SSO) fails when users try to access a Google Drive File Stream native app protected by a policy that allows passwordless access. Users can’t access Google Drive File Stream native appOkta Solution: Use the org URL instead of the admin portal URL. However, if the user enters their admin portal URL (for example, ), they're redirected to their org URL, but enrollment isn’t automatically triggered. If a user doesn't have any Okta Verify account, enrollment is automatically triggered when they enter their org URL (for example, ) in a browser. Okta Verify enrollment isn’t automatically triggered when an admin portal URL is used Ask users to click Sign in with Okta FastPass when they sign in to apps. In step 5, select the Show the “Sign in with Okta FastPass” button checkbox. Rule 2: Any service account, signing in from any device can access the app with any two factors.Įnable Okta FastPass. Rule 1: A non-service account, signing in with a device that is either registered and not managed or registered and managed with any one authentication factor. This issue occurs if you’re using a service account and your authentication policy rules are: Okta isn't able to probe for device context, so users are denied access when they authenticate with a username and password. Users enrolled in Okta Verify are denied access when attempting to access an app To resolve this issue, delete the user enrollment from Okta. Users aren't able to remove their account from Okta Verify if they're deleted from Active Directory To avoid this issue, make sure Okta FastPass is set up for all orgs. If you're using Okta FastPass to sign in to a multi-org environment and Okta FastPass isn't set up for all orgs, the Okta FastPass enrollment prompt might not appear. User don’t receive the Okta FastPass setup prompt when multiple orgs exist Solution: Delete unwanted Okta Verify enrollments from the Admin Console. Even if the user is able to enroll into Okta Verify successfully, they won't be able to access any Okta-protected applications. QR codes generated before a user is deactivated in AD remain valid until they time out. If the user is deactivated in AD before they scan the QR code, they can still scan the QR code and enroll in Okta Verify. When an Active Directory (AD)-sourced user prepares to set up Okta Verify from the Settings page on the End-User Dashboard, the enrollment QR code is displayed. Therefore, the message might reference the wrong device management solution and include a link that points to the wrong enrollment website.Įnd users who are deactivated in AD are able to enroll in Okta Verify When multiple device management configurations exist for the same platform, the remediation message pulls information from the earliest configuration you created. When a user on an unmanaged device tries to access an app associated with one of the configurations and the authentication policy requires devices to be managed, Okta displays an "Additional setup required" remediation message that includes the name of the solution and a link to their enrollment site. This issue occurs when an org has multiple device management configurations for the same platform and each configuration integrates with a different solution (for example, one of your Windows device management configurations integrates with Intune and another with Workspace ONE). Users on unmanaged devices receive an erroneous MDM remediation message Before you contact Okta Support, review this list to determine if the issue you encounter is a known problem that might have a workaround.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |