10-09-2012 01:10 PM - edited 03-17-2019 02:41 PM
I am using CUP 8.6(4) with CUCM 8.6(2a) and MS AD. I have CUCM configured to sync the database and authenticate using LDAP. The AD account provided by the AD team is a service account for UC and works fine for CUCM database access as well as Jabber for Windows. When I use the same account for Jabber on MAC or iPad, the user sees Invalid Credentials. If I use my AD account (which is configured with the same access on AD), the LDAP search works and no problems. I'm using the UPN user name in CUP LDAP profile and I'm using the DN in CUCM. Windows jabber-config.xml uses the userID directly.
Can anyone offer options on what could cause an account not to work on MAC/iPad? (it works on Windows)
Why does a different account work perfectly (same settings)?
Is there a Log on MAC that can provide more details on the "Invalid Credentials" message?
Thanks in advance for any assistance.
11-08-2012 05:02 AM
Enable detailed Logging under Help. Log out and then back in. Go back to help and "Report a Problem". That should give you some detailed logs to look through.
11-11-2012 10:21 AM
Please double check your LDAP Profile settings, making sure your
02-11-2013 11:07 AM
Were you able to resolve this? I'm getting the same behavior. In the Mac Jabber log, it's noting LDAP error 49. We've tried:
02-11-2013 11:15 AM
Could be unrelated, but here's some stuff that doesn't seem to work nice on macs:
- Using TCP 389 on some OSX vers seems hit and miss. Switching to 3268 for the GC works more consistently.
- Having an LDAP filter embeeded in the LDAP profile (on the search base) seems to break some of the Jabber mobile clients and mac.
- I use DN to bind in CUPS... not UPN.
02-11-2013 12:23 PM
Thanks for the reply.
Using 3268/Global Catalog
Using UPN, per Cisco SRND for CUPS. DN was used in the beginning, but neither had a positive impact either way.
02-11-2013 09:56 PM
I opened a TAC case and the engineer found this bug CSCuc06732. It talked about the & character causing issues with the login. I subsequently found it was more than just the & that caused issues with Jabber for MAC authentication. We also found < or > caused the failure as well. I would try a password with just basic alphanumeric and see if it works. Then you can adjust.
You do need UPN (user@domain) for authentication. I was using Global Catalog 3268.
02-12-2013 07:07 AM
I must be hitting some other bug. I'll have to open a TAC case as well. We've tried UPN with an overly weak password to rule that out.
03-02-2013 04:31 PM
I had the same issue described here. As soon as I removed the & from the password everything was fine. (the bug was filed after my case so I wonder if I helped find it.)
Then, I switched to LDAPS on both CCM and CUPS. It broke again.
First, the CUP directions for installing the certificate are incorrect.
CM configured for AD integration over 636 SSL
CUP configured for AD integration over 636 TLS
All certs are signed by CA
I can log in and authenticate to the admin page to both systems via AD
I can log in to Jabber for MAC, but the directory search says 'invalid credentials'
I can log in to Jabber for Windows and search just fine, but the protocol says LDAP, so it probably fails back to unsecure when it can't connect?
Again, This works without LDAPS for MAC, but not with it enabled.
This is what I followed for the CUPS cert install.
Not sure if this is the issue or if it is still special characters in my password. I have validated that none of the following are in my AD bind password:
&, <, >, /, \
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: