Applies to: Okta
Issue Summary
When an administrator modifies a user's User name directly within Okta (Okta.com), the user may experience login failures or be unable to access the Cloud Portal.
Depending on the specific Okta integration mode configured within your Cloud Portal organization (ORG), administrative intervention is required to re-establish secure access for the updated username.
Resolution
Option 1 (Auth (SSO) Only Mode)
Under the Auth (SSO) Only configuration, user management is handled independently in both systems. Changes made in Okta do not automatically sync or overwrite existing records in Cloud Portal.
To change the username:
- Log in to Cloud Portal as an Administrator.
- Navigate to the Users tab.
- Locate the user's historical profile and click Remove User to purge the obsolete account entry.
- Click Add User > New Account.
- Enter the relevant information to create a brand-new SSO account matching the user’s updated Okta username.
The user can now log in successfully using their new Okta credentials.
Option 2 (Auth & Provisioning Mode)
Under the Auth & Provisioning configuration, user provisioning is dynamically bound between the two platforms. To push a primary username change and clear the underlying identity cache, the provisioning link must be re-cycled on the Okta tenant side.
To change the username:
- Log in to your corporate Okta Admin Console (Okta.com).
- Navigate to Applications > Applications.
- Select the connected Hanwha Vision Cloud app.
- Navigate to the Assignments tab.
- Locate the affected user under the People list, and click X (Unassign) to completely remove them from the app.
- Click Save.
- Wait a few moments, then click Assign > Assign to People to re-add the user to the Hanwha Vision Cloud app using their newly updated username.
The updated provisioning signal will automatically stream to the Cloud Portal, allowing the user to log in seamlessly with their new identity.
Comments
0 comments
Article is closed for comments.