/
Okta Bypass - No longer supported

Okta Bypass - No longer supported

Description of Issue
  • The Okta Bypass is no longer supported as of 8-6-2024

  • If in use currently, the bypass can remain until moved to Tyler's gateway

Context
  • Okta

  • TID-W

  • Tyler Identity Workforce

  • Bypass

  • Hub

  • EERP

  • Federation

Cause
  • Tyler has partnered with Okta as the foundational authentication

  • Bypassing the Okta login screen does not remove it from the authentication process underneath

Resolution

Users can check the box to remember the user on most IdPs to store their Okta token to limit the amount of logins

Additional Information

 

Related content

Generate a Client Secret for Microsoft Integration with OKTA
Generate a Client Secret for Microsoft Integration with OKTA
More like this
Okta Login Receives - 400 Bad Request Error Code Access Denied - for Single User
Okta Login Receives - 400 Bad Request Error Code Access Denied - for Single User
More like this
OKTA - Log in access - Azure MFA configuration error
OKTA - Log in access - Azure MFA configuration error
More like this
Change Okta mappings to use Usernames
Change Okta mappings to use Usernames
More like this
Accessing Okta Authentication Logs Within Admin Center
Accessing Okta Authentication Logs Within Admin Center
More like this
Reset Okta AD Agent password from Admin Center
Reset Okta AD Agent password from Admin Center
More like this