Authentication Events

Flip is using the standard OAuth protocol for authentication. Some authentication events relate to the OAuth protocol and are relevant for system administrators wanting to troubleshoot authentication issues.

To monitor any problems with the user authentication flow all authentication events can be found in the Admin Console under Access & Security > Authentication Events.

The corresponding user, the time, the event type, a possible error code, as well as the IP address and the client can be displayed.
The displayed columns can be shown or hidden via the column menu at the top right.

Event Types

Depending on your authentication setup, these are the event types:

LOGIN_USERNAME_PASSWORDA user has logged in using the login form.
BACKGROUND_AUTHENTICATIONA user was re-authenticated via a background process in our app. This automatic process ensures that users remain logged in.
LOGIN_SSOA user was logged in through another Identity Provider.
LOGIN_POST_REGISTRATIONA user was logged in after successfully completing the self-registration process.
LOGIN_API_CLIENTAn API client has logged in. Depending on the API used, this could be either an "OAuth2 Resource Owner Password Flow" or an "OAuth2 Client Credentials Flow".
LOGIN_UNSPECIFIEDA user or an API was authenticated using unspecified methods.
SESSION_PROPAGATIONThe user's authentication session was propagated to another OIDC Client. This happens as a result of users clicking on menu items for external applications or integration.
CODE_TO_TOKENA user/api client has exchanged an authentication code for a refresh/access token pair. This is part of the "OAuth2 Authorization Code Flow" and usually happens after a login or a background authentication.
REFRESH_TOKENA user/api client has refreshed an access token using their refresh token. This automatic process ensures that users remain logged in.
CUSTOM_REQUIRED_ACTIONThe user/api client was required to do certain actions prior to accessing the app. This is either verifying their email, changing their password or accepting the terms and conditions.
REGISTERA user has registered.
LOGOUTA user has logged out.
SEND_PASSWORD_RESETA password reset email has been sent.
UPDATE_PASSWORDThe password for an account has changed.
UPDATE_PROFILEThe profile for an account has changed.
UPDATE_EMAILThe email for an account has changed.
SEND_VERIFY_EMAILAn email verification email has been sent.
VERIFY_EMAILThe email address for an account has been verified.
IDENTITY_PROVIDER_POST_LOGINA user has logged in via an identity provider.
IDENTITY_PROVIDER_FIRST_LOGINA user has logged in for the first time via an identity provider.
FEDERATED_IDENTITY_LINKA user has been linked to an external IDP.

 

Error Codes

There is a corresponding error event for each event type, which can be recognized by the _ERROR suffix. If an error occurs, the error code provides further information about the reason.
These are the most common error types:

client_not_foundThe client has not been found
cookie_not_foundThe cookie has not been found
email_send_failedSending the email failed
expired_codeThe code has expired
Failed to verify login actionFailed to verify login action
invalid_codeThe code is invalid
invalid_emailThe email is invalid
invalid_redirect_uriThe redirect url is invalid
invalid_requestThe request is invalid
invalid_saml_responseThe SAML response is invalid
invalid_tokenThe token is invalid
invalid_user_credentialsThe user credentials are invalid
not_allowedThe action is not allowed
password_confirm_errorThe password has not been confirmed
password_missingThe password has not been entered
password_rejectedThe password has been rejected
rejected_by_userThe action was rejected by the user
session_expiredThe session is expired
user_disabledThe user is disabled
user_not_foundThe user has not been found
user_temporarily_disabledThe user is temporarily disabled
username_missingThe username has not been entered

 

Was this article helpful?

1 out of 2 found this helpful

Have more questions? Submit a request