LDAP, SAML, SSO...an alphabet soup of acronyms you should know if you can't log in

[heidi_schnakenb]

If you are having trouble logging in to the platform, receive error messages, or are working with users who have trouble with their log in credentials, this is known as issues with platform security. Because this is one of the most common head-scratchers that come up for users, we're offering a series of articles that will help you understand the different aspects of platform security troubleshooting. We broke down the content into two groups: LDAP troubleshooting and SAML troubleshooting. If you want to put your log in stumbling blocks to an end, this alphabet soup is for you.

• KB0539111: Troubleshooting LDAP issues in ServiceNow
  • KB0538787: Determining if SAML or LDAP is being used in the instance
  • KB0538642: Determining if the OU definition has changed
  • KB0538674: Determining if the certificate expired on the instance
  • KB0538675: Determining if the LDAP server is down
  • KB0538724: Determining if the main and failover LDAP servers are running
  • KB0538740: Determining if the LDAP source is missing or misconfigured
  • KB0538726: Determining if the wrong LDAP server is configured
  • KB0538725: Determining if a user is marked inactive or locked
• Troubleshooting SAML or SSO issues in ServiceNow
  • KB0538787: Determining if SAML or LDAP is being used in the instance
  • ServiceNow Wiki: Configuring ADFS 2.0 to Communicate with SAML 2.0
  • KB0538763: Determining if the SAML certificate is correct
  • KB0538768: Determining of the properties from the source are copied over a target
  • KB0538769: Determining if SAML issues are occurring due to customer scripts no longer working after ...
  • KB0538770: Determining if the SAML issue is the result of a user being locked out
  • KB0538780: Determining if the SAML issue the result of the user having a duplicate record
  • KB0538781: Determining if a SAML issue is caused by leading or trailing spaces
  • KB0538782: Determining if different time stamps are impacting SAML
  • KB0538786: Determining if the user has an older version of SAML

Next week: get ready for the next Top Ten Solutions column!

[solutioningnow]

As helpful as it can get.

[JamesEcoStratus]

Thank You! Please keep them coming!

[heidi_schnakenb]

You are welcome and you can expect much more to come!

[dline]

I had an odd question today, another sys admin asked what was the highest version of LDAP Server was that would integrate with Service Now is. I know it works with 2010, and I'm not an LDAP sys admin, and don't even know what the latest version would be.

Help?

Doug

[heidi_schnakenb]

Hi, Doug - thanks for your question. I've forwarded to one of our LDAP SMEs here and expect to hear back soon. Thanks!

[heidi_schnakenb]

Hi, Doug,

I checked with one of the SMEs on this and he indicated that because LDAP is protocol-based, he'd expect it to work with any LDAP v3 compatible servers. I hope this helps!

Thanks,

Heidi

[seanpmcclean]

Another great resource for our implementors - I point our classes to this as a "for more information"...

[Community Alums]

Very helpful thanx

[heidi_schnakenb]

Glad you all found it helpful. There will be more blogs like this to come.

[yogesh15dd]

Hi Heidi,

We have just set up SSO integration for our development instance, after that SSO is working fine, but users getting logged in with only one users account : 'snowmidseruser'

we don't remember giving this user details during SSO set up.

urgent please help.

Regards

Yogish