3

As you would know, most password policy for apps and services require to set a password including a special character.

When setting a password for SSO/LDAP, password has to be compatible with all apps that use LDAP acccounts.

During last years I have found problems due this special characters, sometimes symbols have to be escaped at scripts.

For example @ symbol at username can produce problems because some interfaces or cli apps expect a domain/urls after @.

From your experience which symbols are recommended in order to use as plain text and avoid escaping?

Giacomo1968
  • 58,727

2 Answers2

1

I would recommend avoiding & $ and @

However you can use # ! ~ ( ) _ from the number row

and the following from the three rows below : ; < > { } [ ]

0

This will depend entirely on the applications your SSO system needs to work with.

Our experience is not the same as yours. Your needs are unique to you due to the set of applications you wish to use SSO to authenticate being unique to you.

The correct way to solve this problem FOR YOU is to look at the password requirements for the applications you are linking in this scheme and find the characters that are allowed by all of them, and then set the rules on your systems to only accept those characters.

music2myear
  • 49,799