Launch Windows PowerShell with elevated privileges (as Administrator).

Login to your primary ADFS server with sufficient permissions.So how do you fix this? Turns out there is a way to configure Microsoft ADFS to allow for a small time skew. If you look careful enough, you may notice that the response from the IdP to CUCM Pub comes 1 second after it is expected.

In the logs, 12:33:40,009 DEBUG fappend.SamlLogger - SPACSUtils.getResponse: got response= IdP-URL/adfs/services/trust Once the issue is re-created, launch RTMT and download “Cisco SSO” logs, just the like guide tells. Time to collect some relevant logs and dig deeper.įrom the Troubleshooting section of the SSO Configuration Guide, we learn that in order to get any meaningful logs on SSO, we need to set the SAML logs to “debug” level by executing set samltrace level debug command in the CUCM Pub’s CLI. Naturally, one would follow the instructions and verify that time between the CUCM Pub and IdP (in this case, Microsoft ADFS) is in sync. Run “utils ntp status” from the CLI to check this status on Cisco Unified Communications Manager.” Please verify the NTP configuration on both servers. This may be caused when time is out of sync between the Cisco Unified Communications Manager and IDP servers. Upon launching Jabber, the following message would appear: I came across an interesting issue with Jabber shortly after implementing a Single Sign-On for one of the clusters.

Cisco jabber for windows tftp 443