This task is for users with the OC System Administrator role.
After setting up your external user management system, you may find a reason to convert users between federated identity providers (Okta or Azure AD) and the locally managed system (OpenCities). For example, during onboarding, you may have created an account directly in OpenCities and then set up an external user management source, like Azure AD. When the users are synced from an external user management source, they skip users created locally in OpenCities. You can use this option to change where the user's identity is sourced and ensure all your users are managed from a single source.
Change Where a User's Identity is Managed
You can change where a user's identity is managed in Admin Management. Here's how to do it:
- From the main menu, go to More > Users > Admin Management.
- Select the user you want to edit from the list or use their Name or Email to search for them.
- Under Source, use the drop-down menu to select how to manage the user. You can choose from the federated identity providers you have enabled (e.g., Okta, Azure AD ) or Local (OpenCities).
- Select Save to be taken back to the list of users.
Once you've changed a user from Local to Azure AD or Okta, that user cannot log in to OpenCities until the next sync for those services. These syncs regularly happen overnight.
If you need to synchronize sooner than the automatic process, you can do this manually by going to More > External User Management and selecting Sync Now. Please note that syncing manually may impact your site performance.
Once you've changed a user from Azure AD or Okta to Local, that user will temporarily lose access and be sent an automatic password reset email. The user will need to reset their password before being able to log in again.
What Else?
- About the External User Management module
- Set up the Okta or Azure AD connector
- Learn more about Users and Roles