How-to guide
Find out why someone cannot sign in to an app
See who signed in to an application recently, find out why a sign-in failed, and run the built-in tests.
This guide finds out what happened when people signed in to an application: who signed in, who was refused and why. Use it when someone reports that they cannot get into an application.
Look at recent sign-ins
On your home page, under Administration, select Open admin, then select Applications.
Each application’s card already shows when someone last signed in, for example last sign-in 5m ago, or no sign-ins yet.
Open the application and its Access & diagnostics tab.
Scroll to Recent activity, under Diagnostics & activity for an OpenID Connect app or Test SSO & recent activity for a SAML app.
The table lists the latest 20 events, newest first:
| Column | Shows |
|---|---|
| When | Date and time of the event |
| Type | sign_in or logout |
| User | Who signed in. For a delegated sign-in it adds “as” the owner “by” the delegate |
| Result | ok, denied, error, or test for a run of a test button |
| Source IP | Where the request came from |
| Detail | What went wrong, and often a line starting with Fix: |
Sovrain keeps application activity for 90 days.
Find out why a sign-in failed
- Find the row with denied or error for the person and time.
- Read Detail and follow the Fix: line. Common cases:
- the redirect URI the application sent is not listed under Redirect URIs, or differs in a single character;
- the application asked for a scope that is not ticked under Scopes & options;
- the application sent no PKCE while Require PKCE is on;
- the application is disabled.
- Make the change and ask the person to try again.
For a SAML application, a request Sovrain refuses outright, for example an unsigned request while signed requests are required, shows as error with a detail starting with “SAML sign-in rejected:”. See Connect a SAML app for the signed-request setting.
Check that a person may sign in
People refused for lack of access are not in a group under Group access. Open the person from Users and compare their Group memberships with the application’s Group access. See Give a group access to an app.
Run the built-in tests
None of the tests signs anyone in or out.
- OpenID Connect: Test sign-in signs a sample ID token and checks it against the published keys. Run it after rotating keys. Test sign-out checks that the back-channel logout address answers.
- SAML: Run test SSO signs and checks a sample assertion with the active key. Test logout checks the Single Logout setup.
The result appears above the table as Test passed in a number of milliseconds, or Test failed with the reason.
Related
- Review API access for scripts that use the Admin API.
- Rotate signing keys.
- Limits for retention.