What people keep running into with authentication
Complaints tagged authentication, each raised by more than one person. One-off posts are not included.
30 recurring problems · 381 people · 21 forums we read
Raised more than once
Most people first.
- 4Why does platform single sign on keep breaking?Platform single sign-on intermittently breaks after a few weeks or months, forcing devices to completely drop out of directory membership. This sudden failure blocks access and requires users to either wait weeks, manually wipe the machine, or completely rejoin the system from scratch.
- 3QNAP NAS shared folder opens but is empty for Apple usersApple users trying to access a QNAP NAS find that the shared folder takes time to load and ultimately appears empty. While the mapped drive itself is visible, clicking it fails to auto-populate or display the necessary company data files inside. Trying to restore access forces people to blindly guess between confusing configuration options without understanding the differences.
- 3Can't verify account without a mobile phoneVerification systems rely on text messages that cannot be received on a landline or go to phone numbers you no longer have. When backup options like landline callbacks fail, people are entirely blocked from finishing new account setups or get locked out of their existing shops. They then cannot contact customer support to explain the situation because help sites require an active login just to get assistance.
- 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.
- 2Can multiple Windows users open a KeePass database?KeePass does not natively support setting up multiple Windows user logins or Active Directory domain accounts as valid authentication for a single database. This prevents shared systems from allowing different users to open the file using their individual credentials.
- 2Why is step-up authentication forced and buggy?Step-up authentication is currently enforced without an option to turn it off, leaving administrators stuck with inconsistent browser behavior that support writes off as known issues. These unpredictable prompts prevent users from completing basic workflows, such as returning to their original report tab after verification.
- 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.
- 2Why does Salesforce require another login after Okta 2FA?Salesforce does not recognize Okta's 2FA as sufficient, forcing users to jump through multiple verification processes just to gain access. This creates an awful "MFA all the time" workflow that puts up a barrier to actually accessing the system. Ultimately, these extra security hoops make it even harder to get sales teams to use the tool.
- 2Logged out immediately after logging inAuthentication systems repeatedly clear the active session within seconds of signing in, failing to persist user credentials across initial redirects. This forces people into an endless login loop, blocking them from accessing the application entirely.
- 2Can't log into AWS console with root emailThe system redirects you to a Builder ID sign-up page without warning, prompting you to create a new password. This prevents you from logging into your AWS console with your original root email. Fixing the issue is frustrating, as support chats can remain unresponsive for 30 minutes or more.
Comes up alongside
Topics that keep appearing on the same problems — not topics with similar names.