After configuring Active Directory as the desired authentication service, an administrator is not able to login into Prism Central using a privileged account.
Which configuration must be checked first?
After configuring Active Directory as the desired authentication service, an administrator is not able to login into Prism Central using a privileged account.
Which configuration must be checked first?
When facing login issues after configuring Active Directory as the authentication service, the first configuration to check is Role Mapping. Role Mapping ensures that users from Active Directory are correctly assigned the appropriate roles and permissions within Prism Central. Without proper role mapping, even privileged accounts may not have the necessary permissions to access the system, causing login issues.
Checking the local user account configuration should be the first step considering the context of the issue occurring after configuring Active Directory as the authentication service. Before implementing Active Directory authentication, Prism Central likely relied on local user accounts for login credentials. After transitioning to Active Directory authentication, it's possible that the local user account configuration might not have been updated or could have been affected by the change, leading to login issues with privileged accounts.