Ensure users can successfully sign in to Workvivo using Okta Single Sign-On (SSO) by confirming the Workvivo application is correctly assigned and visible within the user’s Okta tenant.
Error Message
If a user encounters the error:
“HTTP 500: Internal Server Error”
when attempting to sign in, this typically indicates an application assignment or visibility issue on the Okta side, rather than a problem with Workvivo itself.
In most cases, this error occurs because the Workvivo application is not correctly assigned to the user or is not configured to appear as a launchable app (chiclet) in Okta.
Using Okta SSO with Workvivo
Where the issue occurs
This error is generated during the Okta authentication flow, before the login request reaches Workvivo.
Because the authentication does not complete successfully in Okta, Workvivo is unable to process the login request.
Common Cause
In most cases, the affected user is experiencing one of the following:
The Workvivo application is not assigned to the user in Okta
The application is assigned but not visible as a chiclet
“Show App Icon” is disabled in the Okta application settings
The user’s assignment or role configuration has become out of sync
How to Resolve the Issue
The Okta Administrator should complete the following steps:
Sign in to the Okta Admin Console
Navigate to Applications
Open the Workvivo application
Select Assignments
Confirm the user is assigned to the application
In the application settings, ensure:
Show App Icon is enabled
If the issue persists:
Remove the user from the Workvivo application
Re-assign the user to the application
If custom roles are in use:
Temporarily revoke any non-default roles
Re-apply the required roles after reassignment
Once these steps are completed, the user should be able to sign in successfully.
Additional Information
This error message is generated by Okta, not Workvivo
Workvivo does not control Okta application assignments or visibility settings
Role reassignment may be required if custom roles are configured
Changes in Okta may take a short time to fully apply
Testing the login in a private or incognito browser window is recommended to avoid cached session issues
Still Having Issues?
If the Okta configuration above has been confirmed as correct and the user is still unable to sign in, please contact Workvivo Support for further assistance and investigation.