A User Cannot Sign In After Directory Integration is Configured
Problem A user cannot sign in after directory integration is configured.
Possible Cause There is a problem with the user's Active Directory account.
Solution Check your Active Directory Server to see whether the user has an account and whether it is active.
Possible Cause The user's email account might not be valid.
Solution Ensure that the user has a valid email account. The accepted format is firstname.lastname@example.org.
Possible Cause The user might not be configured in the Cisco Unified Communications Manager (CUCM) directory.
Solution Verify that the user appears in the users list in CUCM. Users can sign in, even before the user account is imported into your Cisco Webex Meetings Server database. When LDAP authentication is enabled and a user tries to sign in, your system verifies that the email address exists in the database (local or remote user). If the user exists, it checks for the field ADUserID in the database for this user. The system populates this field after you perform a directory synchronization. If the field is empty, the system checks the CUCM database to see whether the user exists there. If the user exists in the CUCM database, the system updates the ADUserID fields for the user record in the database. Authentication continues and succeeds, as long as the user exists in the CUCM database and provides the correct credentials. After the first sign in, the system treats the user as an Active Directory synchronized user.