Authentication and user management
Local account cannot sign in after invitation
For local authentication, the login field is the account's Username, not the email address used for the invitation. Verify that the user is entering their username, not their email.
See: Local authentication
LDAP authentication returns 401 or does not find users
Verify the LDAP search settings with ldapsearch using the same service account and search base you configured in TestOps, before changing the TestOps configuration. If ldapsearch does not return the expected entry, the issue is in the LDAP-side settings:
- LDAP URL
- bind DN and bind password
- user search base and search filter
- UID attribute used for sign-in
See: LDAP
Cannot sign in as administrator when external IdP is primary
When LDAP, OpenID, or SAML is the primary login method, the built-in administrator account is available at:
<your TestOps URL>/login/system
Use this when the external IdP is unavailable or the license needs to be reactivated.
See: Local authentication
Users get CSRF token error on sign-in
The browser console shows Request failed with status code 401. The expected CSRF token could not be found. This is typically caused by a stale session in Redis, which can happen when the clocks on the server, user machine, and VPN endpoint are in different time zones.
Fix: flush the Redis session store. This will sign out all active users, so do this during off-hours or notify users in advance.
redis-cli FLUSHALL
Alternatively, restart the Redis service. The effect is the same. Allure TestOps stores no persistent data in Redis.
