> For the complete documentation index, see [llms.txt](/docs/llms.txt)

# Authentication Types | FusionAuth Docs

Learn about the supported types of authentication.

# Authentication Types

FusionAuth supports authentication in many different ways. These are the methods that are available.

*   `APPLE` - The user was authenticated using Apple. Available since 1.17.0
*   `APPLICATION_TOKEN` - The user was authenticated using an Application Authentication Token.
*   `EpicGames` - The user was authenticated using Epic Games. Available since 1.28.0
*   `FACEBOOK` - The user was authenticated using Facebook. Available since 1.1.0
*   `FEDERATED_JWT` - The user was authenticated using a JWT from an external source.
*   `GENERIC_CONNECTOR` - The user was authenticated using a generic connector. Available since 1.18.0
*   `GOOGLE` - The user was authenticated using Google. Available since 1.1.0
*   `HYPR` - The user was authenticated using HYPR. Available since 1.12.0
*   `JWT_SSO` - A valid JWT associated with one application was exchanged for another JWT associated with a different application.
*   `LDAP_CONNECTOR` - The user was authenticated using an LDAP connector. Available since 1.18.0
*   `LINKEDIN` - The user was authenticated using LinkedIn. Available since 1.23.0
*   `Nintendo` - The user was authenticated using Nintendo. Available since 1.36.0
*   `ONE_TIME_PASSWORD` - The user was authenticated using a one-time password. Available since 1.5.0
*   `OPENID_CONNECT` - The user was authenticated using OIDC. Available since 1.1.0
*   `PASSWORD` - The user was authenticated using a loginId and password combination.
*   `PASSWORDLESS` - The user was authenticated using a passwordless login link. Available since 1.5.0
*   `PING` - The user was authenticated using a `PUT` request on the Login API. This is used to record a login event without prompting for credentials, such as when the FusionAuth SSO session is used.
*   `REFRESH_TOKEN` - The user requested a new JWT using a refresh token.
*   `REGISTRATION` - The user was created using the Registration API. Available since 1.16.0
*   `SAMLv2` - The user was authenticated using SAMLv2. Available since 1.6.0
*   `SAMLv2IdpInitiated` - The user was authenticated using SAMLv2 IdP Initiated login. Available since 1.28.0
*   `SonyPSN` - The user was authenticated using Sony. Available since 1.28.0
*   `Steam` - The user was authenticated using Steam. Available since 1.28.0
*   `TWITTER` - The user was authenticated using Twitter. Available since 1.1.0
*   `Twitch` - The user was authenticated using Twitch. Available since 1.28.0
*   `USER_CREATE` - The user was created using the User API. Available since 1.16.0
*   `WebAuthn` - The user was authenticated using a passkey. Available since 1.41.0
*   `Xbox` - The user was authenticated using Xbox. Available since 1.28.0

These authentication type values are available in [webhook payloads](/docs/extend/events-and-webhooks/events/user/login/user-login-success), [OAuth tokens](/docs/lifecycle/authenticate-users/oauth/tokens) and for use with a [login validation lambda](/docs/extend/code/lambdas/login-validation).