What people keep running into with SSO
Complaints tagged SSO, each raised by more than one person. One-off posts are not included.
4 recurring problems · 11 people · 3 forums we read
Raised more than once
Most people first.
- 4How to manage users who don't have separate email addressesMany systems now require unique individual emails for every login, which blocks administrators from setting up part-time staff who share distribution lists. This forces teams to either invent workaround accounts or abandon platforms that refuse to support shared access.
- 3Active Directory and LDAP web login fails with no logsWeb UI logins configured with Active Directory, LDAP, or Entra often fail or immediately drop the user's session. Fixing the configuration is incredibly difficult because vendor support blames the user's environment, documentation is poor, and diagnostic logs are either empty or take up to two days to appear. This leaves administrators guessing and relying on temporary workarounds like clearing browser cookies.
- 2Why won't my seller account update my email address?Platforms often fail to process email changes due to technical errors or account mapping restrictions, frequently reverting the change or displaying failure messages. This prevents sellers from updating crucial account details like name changes, often forcing them to abandon the attempt or risk breaking their account history.
- 2Why do privileged Salesforce users have to create separate passkeys?Salesforce forces administrators and privileged users to set up platform-specific passkeys instead of letting them use their existing enterprise SSO and MFA providers like Microsoft Authenticator. This requirement prevents teams from maintaining a unified authentication workflow across all users.
Comes up alongside
Topics that keep appearing on the same problems — not topics with similar names.