ā08-17-2020 04:21 AM - edited ā08-17-2020 05:02 AM
This is a LDAP enabled system and I have checked the LDAP and it appears to be syncing correctly.
I have to use the locally defined administrator account to login.
This was working, however, I am currently unable to login to my Inbox or the Cisco Unity Connection Administration page with my AD username and password.
I can use the dial into vm and it works with the pin but prefer the web Inbox.
Has Anyone had this happen to them?
When i try i get this:
Solved! Go to Solution.
ā08-17-2020 07:10 AM
Make sure users are enabled for web inbox, that they show correctly synced to LDAP and that the LDAP sync/authentication is correct, and that the user/pwd are correct, the user might also be locked directly in LDAP.
If no avail, you can get a sniffer to see what is sent to LDAP and what LDAP replies.
ā08-18-2020 06:42 AM
LDAP Integration has two components: LDAP Synchronization (creates the user accounts) and LDAP Authentication (authentication via LDAP rather than via local database).
You have configured LDAP Synchronization and created user accounts successfully. In order for users to use their LDAP credentials to log into the Unity Connection GUI (Web Inbox or admin) you would also need to configure LDAP Authentication, which is a separate step. If you have not yet configured LDAP Authentication, then whatever "Web Password" is configured in Unity Connection itself is the password they would use to log into Web Inbox.
As for enabling users for Web Inbox, this is part of "Class of Service" in Unity Connection. CoS in UConn determines which features (especially licensed features) a user has access to. So, for any user that you would like to have use the Web Inbox you would need to look at which CoS they have assigned to their account and ensure that it has "Allow Users to Use the Web Inbox and RSS Feeds" checkbox checked.
HTH. Let us know if you have more questions.
Maren
ā08-17-2020 07:10 AM
Make sure users are enabled for web inbox, that they show correctly synced to LDAP and that the LDAP sync/authentication is correct, and that the user/pwd are correct, the user might also be locked directly in LDAP.
If no avail, you can get a sniffer to see what is sent to LDAP and what LDAP replies.
ā08-18-2020 05:31 AM
This gets a little deep for me...
I don not know how to do this "Make sure users are enabled for web inbox,"
When I look at the user (me) in unity, i see that i am "Integrate with LDAP Directory"
I then try to login to the inbox and it fails.
I go to "change password" the choose pin drop down contains only "Voicemail".
So, i go to user basics and set myself for "Do Not Integrate with LDAP Directory" and save.
Then I go to "change password" and now the "choose pin" drop down contains both "Web Application" and "Voicemail".
Then i set a password, now i can login to unity admin and my inbox and they both work for me.
Can you explain why LDAP might not be working for this?
I know I am not locked in LDAP, as I am using my computer.
ā08-18-2020 06:42 AM
LDAP Integration has two components: LDAP Synchronization (creates the user accounts) and LDAP Authentication (authentication via LDAP rather than via local database).
You have configured LDAP Synchronization and created user accounts successfully. In order for users to use their LDAP credentials to log into the Unity Connection GUI (Web Inbox or admin) you would also need to configure LDAP Authentication, which is a separate step. If you have not yet configured LDAP Authentication, then whatever "Web Password" is configured in Unity Connection itself is the password they would use to log into Web Inbox.
As for enabling users for Web Inbox, this is part of "Class of Service" in Unity Connection. CoS in UConn determines which features (especially licensed features) a user has access to. So, for any user that you would like to have use the Web Inbox you would need to look at which CoS they have assigned to their account and ensure that it has "Allow Users to Use the Web Inbox and RSS Feeds" checkbox checked.
HTH. Let us know if you have more questions.
Maren
ā08-18-2020 08:08 AM
LDAP auth was it.
When the team changed LDAP servers, LDAP Setup and Directory Configuration were updated but the auth was not done.
Thank You,
Allen
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide