Assigned Application Missing From User Okta Dashboard

An assigned application does not display a tile on the Okta End-User Dashboard when the application visibility settings hide the icon, a provisioning task fails, or the user is missing an external ID. Resolve this by updating the application visibility settings, resolving any failed tasks on the Tasks page, and verifying the user assignment.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Application Assignment
• End-User Dashboard

This issue occurs due to one of the following reasons:

• The application visibility is set to Do not display application icon to users under the General tab of the application.
• Assigning the application triggered a corresponding task that failed.
• The user is missing the external ID in the application user assignment window.

How is the missing application tile resolved?

Update the application visibility settings, resolve any failed tasks, and verify the user assignment by following these steps.

1. Clear the Do not display application icon to users checkbox under the General tab of the application.

   Review the application visibility settings to ensure the application icon displays to users.

   

2. Navigate to Dashboard > Tasks.

3. Locate the "Application assignments encountered errors" events and apply the corresponding resolution:

   • Invalid password or strong password required: Check the Okta legacy password policy to ensure it satisfies the service provider complexity requirements. Ensure the user account configured under the API integration for the application has permission to set passwords in the target application.
   • Unable to assign licenses to the user: Check the license selected in the user or group application assignment. Verify that the licenses are available on the service provider side.
   • Username already exists or is unavailable: Determine whether the user has already created a personal account for the application with the same username that Okta attempts to use during provisioning.
   • Required attribute is missing a value: Determine what attributes the service provider considers required. Verify that the required attributes are populated in the user profile by comparing the user profile with another successfully provisioned user or by navigating to the application profile in the Profile Editor to view the required attributes.
   • Invalid permissions or credentials: Ensure that the account configured in the Provisioning tab of the application has the appropriate level of elevation on the service provider side (for example, a Google Workspace Super Administrator account or a Microsoft Office 365 Global Administrator). Test the provisioning credentials to rule out an expired password, a changed password, or a deactivated account.

4. Verify the user assignment to the application to ensure the external ID displays and no red dots hide provisioning error messages next to the user name.