Expo AuthSession

GitHub

npm

A universal library that provides an API to handle browser-based authentication.

Android
iOS
Web

AuthSession enables web browser-based authentication (for example, browser-based OAuth flows) in your app by utilizing WebBrowser and Crypto. For implementation details, refer to this reference, and for usage, see the Authentication guide.

Installation

expo-crypto is a peer dependency and must be installed alongside expo-auth-session.

Terminal
npx expo install expo-auth-session expo-crypto

If you are installing this in an existing React Native app, start by installing expo in your project. Then, follow the additional instructions as mentioned by the library's README under "Installation in bare React Native projects" section.

Are you using this library in a bare React Native app?

Use the uri-scheme CLI to easily add, remove, list, and open your URIs.

To make your native app handle mycoolredirect:// simply run:

Terminal
npx uri-scheme add mycoolredirect

You should now be able to see a list of all your project's schemes by running:

Terminal
npx uri-scheme list

You can test it to ensure it works like this:

Terminal
# Rebuild the native apps, be sure to use an emulator
yarn android
yarn ios

# Open a URI scheme
npx uri-scheme open mycoolredirect://some/redirect

Usage in standalone apps

app.json
{
  "expo": {
    "scheme": "mycoolredirect"
  }
}

to be able to deep link back into your app, you will need to set a scheme in your project app.config.js, or app.json, and then build your standalone app (it can't be updated with an update). If you do not include a scheme, the authentication flow will complete, but it will be unable to pass the information back into your application and the user will have to manually exit the authentication modal (resulting in a canceled event).

Guides

The guides have moved: Authentication Guide.

How web browser based authentication flows work

The typical flow for browser-based authentication in mobile apps is as follows:

  • Initiation: the user presses a sign in button
  • Open web browser: the app opens up a web browser to the authentication provider sign in page. The url that is opened for the sign in page usually includes information to identify the app, and a URL to redirect to on success. Note: the web browser should share cookies with your system web browser so that users do not need to sign in again if they are already authenticated on the system browser -- Expo's WebBrowser API takes care of this.
  • Authentication provider redirects: upon successful authentication, the authentication provider should redirect back to the application by redirecting to URL provided by the app in the query parameters on the sign in page (read more about how linking works in mobile apps), provided that the URL is in the allowlist of allowed redirect URLs. Allowlisting redirect URLs is important to prevent malicious actors from pretending to be your application. The redirect includes data in the URL (such as user id and token), either in the location hash, query parameters, or both.
  • App handles redirect: the redirect is handled by the app and data is parsed from the redirect URL.

Security considerations

  • Never put any secret keys inside your application code, there is no secure way to do this! Instead, you should store your secret key(s) on a server and expose an endpoint that makes API calls for your client and passes the data back.

API

import * as AuthSession from 'expo-auth-session';

Hooks

useAuthRequest(config, discovery)

ParameterTypeDescription
configAuthRequestConfig

A valid AuthRequestConfig that specifies what provider to use.

discoverynull | DiscoveryDocument

A loaded DiscoveryDocument with endpoints used for authenticating. Only authorizationEndpoint is required for requesting an authorization code.


Load an authorization request for a code. When the prompt method completes then the response will be fulfilled.

In order to close the popup window on web, you need to invoke WebBrowser.maybeCompleteAuthSession(). See the Identity example for more info.

If an Implicit grant flow was used, you can pass the response.params to TokenResponse.fromQueryParams() to get a TokenResponse instance which you can use to easily refresh the token.

Returns a loaded request, a response, and a prompt method in a single array in the following order:

  • request - An instance of AuthRequest that can be used to prompt the user for authorization. This will be null until the auth request has finished loading.
  • response - This is null until promptAsync has been invoked. Once fulfilled it will return information about the authorization.
  • promptAsync - When invoked, a web browser will open up and prompt the user for authentication. Accepts an AuthRequestPromptOptions object with options about how the prompt will execute.

Example

const [request, response, promptAsync] = useAuthRequest({ ... }, { ... });

useAutoDiscovery(issuerOrDiscovery)

ParameterTypeDescription
issuerOrDiscoveryIssuerOrDiscovery

URL using the https scheme with no query or fragment component that the OP asserts as its Issuer Identifier.


Given an OpenID Connect issuer URL, this will fetch and return the DiscoveryDocument (a collection of URLs) from the resource provider.

Returns:

DiscoveryDocument | null

Returns null until the DiscoveryDocument has been fetched from the provided issuer URL.

Example

const discovery = useAutoDiscovery('https://example.com/auth');

Classes

AccessTokenRequest

Type: Class extends TokenRequest<AccessTokenRequestConfig> implements AccessTokenRequestConfig

Access token request. Exchange an authorization code for a user access token.

Section 4.1.3

AccessTokenRequest Properties

AccessTokenRequest Methods

performAsync(discovery)

ParameterType
discoveryPick<DiscoveryDocument, 'tokenEndpoint'>

AuthError

Type: Class extends ResponseError

Represents an authorization response error: Section 5.2. Often times providers will fail to return the proper error message for a given error code. This error method will add the missing description for more context on what went wrong.

AuthError Properties

code

Type: string

description

Optional • Type: string

Used to assist the client developer in understanding the error that occurred.

info

Optional • Type: any

params

Type: Record<string, string>

Raw results of the error.

state

Optional • Type: string

Required only if state is used in the initial request

uri

Optional • Type: string

A URI identifying a human-readable web page with information about the error, used to provide the client developer with additional information about the error.

AuthRequest

Type: Class implements Omit<AuthRequestConfig, 'state'>

Used to manage an authorization request according to the OAuth spec: Section 4.1.1. You can use this class directly for more info around the authorization.

Common use-cases:

  • Parse a URL returned from the authorization server with parseReturnUrlAsync().
  • Get the built authorization URL with makeAuthUrlAsync().
  • Get a loaded JSON representation of the auth request with crypto state loaded with getAuthRequestConfigAsync().

Example

// Create a request.
const request = new AuthRequest({ ... });

// Prompt for an auth code
const result = await request.promptAsync(discovery);

// Get the URL to invoke
const url = await request.makeAuthUrlAsync(discovery);

// Get the URL to invoke
const parsed = await request.parseReturnUrlAsync("<URL From Server>");

AuthRequest Properties

codeVerifier

Optional • Type: string

state

Type: string

Used for protection against Cross-Site Request Forgery.

url

Type: null | string • Default: null

AuthRequest Methods

getAuthRequestConfigAsync()

Load and return a valid auth request based on the input config.

makeAuthUrlAsync(discovery)

ParameterType
discoveryAuthDiscoveryDocument

Create the URL for authorization.

Returns:

Promise<string>

parseReturnUrl(url)

ParameterType
urlstring

promptAsync(discovery, promptOptions)

ParameterType
discoveryAuthDiscoveryDocument
promptOptions
(optional)
AuthRequestPromptOptions

Prompt a user to authorize for a code.

RefreshTokenRequest

Type: Class extends TokenRequest<RefreshTokenRequestConfig> implements RefreshTokenRequestConfig

Refresh request.

Section 6

RefreshTokenRequest Properties

RefreshTokenRequest Methods

performAsync(discovery)

ParameterType
discoveryPick<DiscoveryDocument, 'tokenEndpoint'>

RevokeTokenRequest

Type: Class extends Request<RevokeTokenRequestConfig, boolean> implements RevokeTokenRequestConfig

Revocation request for a given token.

Section 2.1

RevokeTokenRequest Methods

TokenError

Type: Class extends ResponseError

Section 4.1.2.1

TokenError Properties

code

Type: string

description

Optional • Type: string

Used to assist the client developer in understanding the error that occurred.

info

Optional • Type: any

params

Type: Record<string, string>

Raw results of the error.

uri

Optional • Type: string

A URI identifying a human-readable web page with information about the error, used to provide the client developer with additional information about the error.

TokenResponse

Type: Class implements TokenResponseConfig

Token Response.

Section 5.1

TokenResponse Methods

fromQueryParams(params)

ParameterType
paramsRecord<string, any>

Creates a TokenResponse from query parameters returned from an AuthRequest.

isTokenFresh(token, secondsMargin)

ParameterType
tokenPick<TokenResponse, 'expiresIn' | 'issuedAt'>
secondsMargin
(optional)
number

Determines whether a token refresh request must be made to refresh the tokens

Returns:

boolean

refreshAsync(config, discovery)

ParameterType
configOmit<TokenRequestConfig, 'grantType' | 'refreshToken'>
discoveryPick<DiscoveryDocument, 'tokenEndpoint'>

shouldRefresh()

Returns:

boolean

Methods

AuthSession.dismiss()

Cancels an active AuthSession if there is one.

Returns:

void

AuthSession.exchangeCodeAsync(config, discovery)

ParameterTypeDescription
configAccessTokenRequestConfig

Configuration used to exchange the code for a token.

discoveryPick<DiscoveryDocument, 'tokenEndpoint'>

The tokenEndpoint for a provider.


Exchange an authorization code for an access token that can be used to get data from the provider.

Returns a discovery document with a valid tokenEndpoint URL.

AuthSession.fetchDiscoveryAsync(issuer)

ParameterTypeDescription
issuerstring

An Issuer URL to fetch from.


Fetch a DiscoveryDocument from a well-known resource provider that supports auto discovery.

Returns a discovery document that can be used for authentication.

AuthSession.fetchUserInfoAsync(config, discovery)

ParameterTypeDescription
configPick<TokenResponse, 'accessToken'>

The accessToken for a user, returned from a code exchange or auth request.

discoveryPick<DiscoveryDocument, 'userInfoEndpoint'>

The userInfoEndpoint for a provider.


Fetch generic user info from the provider's OpenID Connect userInfoEndpoint (if supported).

Returns:

Promise<Record<string, any>>

See: UserInfo.

AuthSession.generateHexStringAsync(size)

ParameterType
sizenumber

Digest a random string with hex encoding, useful for creating nonces.

Returns:

Promise<string>

AuthSession.getDefaultReturnUrl(urlPath, options)

ParameterType
urlPath
(optional)
string
options
(optional)
Omit<CreateURLOptions, 'queryParams'>

Returns:

string

Deprecated Use makeRedirectUri() instead.

AuthSession.getRedirectUrl(path)

ParameterType
path
(optional)
string

Get the URL that your authentication provider needs to redirect to. For example: https://auth.expo.io/@your-username/your-app-slug. You can pass an additional path component to be appended to the default redirect URL.

Note This method will throw an exception if you're using the bare workflow on native.

Returns:

string

Example

const url = AuthSession.getRedirectUrl('redirect');

// Managed: https://auth.expo.io/@your-username/your-app-slug/redirect
// Web: https://localhost:19006/redirect

AuthSession.loadAsync(config, issuerOrDiscovery)

ParameterTypeDescription
configAuthRequestConfig

A valid AuthRequestConfig that specifies what provider to use.

issuerOrDiscoveryIssuerOrDiscovery

A loaded DiscoveryDocument or issuer URL. (Only authorizationEndpoint is required for requesting an authorization code).


Build an AuthRequest and load it before returning.

Returns an instance of AuthRequest that can be used to prompt the user for authorization.

AuthSession.makeRedirectUri(options)

ParameterTypeDescription
options
(optional)
AuthSessionRedirectUriOptions

Additional options for configuring the path.

Default:{}

Create a redirect url for the current platform and environment. You need to manually define the redirect that will be used in a bare workflow React Native app, or an Expo standalone app, this is because it cannot be inferred automatically.

  • Web: Generates a path based on the current window.location. For production web apps, you should hard code the URL as well.
  • Managed workflow: Uses the scheme property of your app config.
  • Bare workflow: Will fallback to using the native option for bare workflow React Native apps.
Returns:

string

The redirectUri to use in an authentication request.

Example

const redirectUri = makeRedirectUri({
  scheme: 'my-scheme',
  path: 'redirect'
});
// Development Build: my-scheme://redirect
// Expo Go: exp://127.0.0.1:8081/--/redirect
// Web dev: https://localhost:19006/redirect
// Web prod: https://yourwebsite.com/redirect

const redirectUri2 = makeRedirectUri({
  scheme: 'scheme2',
  preferLocalhost: true,
  isTripleSlashed: true,
});
// Development Build: scheme2:///
// Expo Go: exp://localhost:8081
// Web dev: https://localhost:19006
// Web prod: https://yourwebsite.com

AuthSession.refreshAsync(config, discovery)

ParameterTypeDescription
configRefreshTokenRequestConfig

Configuration used to refresh the given access token.

discoveryPick<DiscoveryDocument, 'tokenEndpoint'>

The tokenEndpoint for a provider.


Refresh an access token.

  • If the provider didn't return a refresh_token then the access token may not be refreshed.
  • If the provider didn't return a expires_in then it's assumed that the token does not expire.
  • Determine if a token needs to be refreshed via TokenResponse.isTokenFresh() or shouldRefresh() on an instance of TokenResponse.

Returns a discovery document with a valid tokenEndpoint URL.

See: Section 6.

AuthSession.resolveDiscoveryAsync(issuerOrDiscovery)

ParameterType
issuerOrDiscoveryIssuerOrDiscovery

Utility method for resolving the discovery document from an issuer or object.

AuthSession.revokeAsync(config, discovery)

ParameterTypeDescription
configRevokeTokenRequestConfig

Configuration used to revoke a refresh or access token.

discoveryPick<DiscoveryDocument, 'revocationEndpoint'>

The revocationEndpoint for a provider.


Revoke a token with a provider. This makes the token unusable, effectively requiring the user to login again.

Returns:

Promise<boolean>

Returns a discovery document with a valid revocationEndpoint URL. Many providers do not support this feature.

Interfaces

AccessTokenRequestConfig

Extends: TokenRequestConfig

Config used to exchange an authorization code for an access token.

AccessTokenRequestConfig Properties

NameTypeDescription
codestring

The authorization code received from the authorization server.

redirectUristring

If the redirectUri parameter was included in the AuthRequest, then it must be supplied here as well.

Section 3.1.2


AuthRequestConfig

Represents an OAuth authorization request as JSON.

AuthRequestConfig Properties

NameTypeDescription
clientIdstring

A unique string representing the registration information provided by the client. The client identifier is not a secret; it is exposed to the resource owner and shouldn't be used alone for client authentication.

The client identifier is unique to the authorization server.

Section 2.2

clientSecret
(optional)
string

Client secret supplied by an auth provider. There is no secure way to store this on the client.

Section 2.3.1

codeChallenge
(optional)
string

Derived from the code verifier by using the CodeChallengeMethod.

Section 4.2

codeChallengeMethod
(optional)
CodeChallengeMethod

Method used to generate the code challenge. You should never use Plain as it's not good enough for secure verification.

Default:CodeChallengeMethod.S256
extraParams
(optional)
Record<string, string>

Extra query params that'll be added to the query string.

prompt
(optional)
Prompt

Informs the server if the user should be prompted to login or consent again. This can be used to present a dialog for switching accounts after the user has already been logged in.

Section 3.1.2.1

redirectUristring

After completing an interaction with a resource owner the server will redirect to this URI. Learn more about linking in Expo.

Section 3.1.2

responseType
(optional)
string

Specifies what is returned from the authorization server.

Section 3.1.1

Default:ResponseType.Code
scopes
(optional)
string[]

List of strings to request access to.

Section 3.3

state
(optional)
string

Used for protection against Cross-Site Request Forgery.

usePKCE
(optional)
boolean

Should use Proof Key for Code Exchange.

Default:true

DiscoveryDocument

DiscoveryDocument Properties

NameTypeDescription
authorizationEndpoint
(optional)
string

Used to interact with the resource owner and obtain an authorization grant.

Section 3.1

discoveryDocument
(optional)
ProviderMetadata

All metadata about the provider.

endSessionEndpoint
(optional)
string

URL at the OP to which an RP can perform a redirect to request that the End-User be logged out at the OP.

OPMetadata

registrationEndpoint
(optional)
string

URL of the OP's Dynamic Client Registration Endpoint.

revocationEndpoint
(optional)
string

Used to revoke a token (generally for signing out). The spec requires a revocation endpoint, but some providers (like Spotify) do not support one.

Section 2.1

tokenEndpoint
(optional)
string

Used by the client to obtain an access token by presenting its authorization grant or refresh token. The token endpoint is used with every authorization grant except for the implicit grant type (since an access token is issued directly).

Section 3.2

userInfoEndpoint
(optional)
string

URL of the OP's UserInfo Endpoint used to return info about the authenticated user.

UserInfo


Deprecated See Facebook authentication.

FacebookAuthRequestConfig

Extends: ProviderAuthRequestConfig

FacebookAuthRequestConfig Properties

NameTypeDescription
androidClientId
(optional)
string

Android native client ID for use in development builds and bare workflow.

iosClientId
(optional)
string

iOS native client ID for use in development builds and bare workflow.

webClientId
(optional)
string

Expo web client ID for use in the browser.


Deprecated See Google authentication.

GoogleAuthRequestConfig

Extends: ProviderAuthRequestConfig

GoogleAuthRequestConfig Properties

NameTypeDescription
androidClientId
(optional)
string

Android native client ID for use in standalone, and bare workflow.

iosClientId
(optional)
string

iOS native client ID for use in standalone, bare workflow, and custom clients.

language
(optional)
string

Language code ISO 3166-1 alpha-2 region code, such as 'it' or 'pt-PT'.

loginHint
(optional)
string

If the user's email address is known ahead of time, it can be supplied to be the default option. If the user has approved access for this app in the past then auth may return without any further interaction.

selectAccount
(optional)
boolean

When true, the service will allow the user to switch between accounts (if possible).

Default:false.
shouldAutoExchangeCode
(optional)
boolean

Should the hook automatically exchange the response code for an authentication token.

Defaults to true on installed apps (Android, iOS) when ResponseType.Code is used (default).

webClientId
(optional)
string

Expo web client ID for use in the browser.


RefreshTokenRequestConfig

Extends: TokenRequestConfig

Config used to request a token refresh, or code exchange.

RefreshTokenRequestConfig Properties

NameTypeDescription
refreshToken
(optional)
string

The refresh token issued to the client.


RevokeTokenRequestConfig

Extends: Partial<TokenRequestConfig>

Config used to revoke a token.

RevokeTokenRequestConfig Properties

NameTypeDescription
tokenstring

The token that the client wants to get revoked.

Section 3.1

tokenTypeHint
(optional)
TokenTypeHint

A hint about the type of the token submitted for revocation.

Section 3.2


ServerTokenResponseConfig

Object returned from the server after a token response.

ServerTokenResponseConfig Properties

NameTypeDescription
access_tokenstring-
expires_in
(optional)
number-
id_token
(optional)
string-
issued_at
(optional)
number-
refresh_token
(optional)
string-
scope
(optional)
string-
token_type
(optional)
TokenType-

TokenRequestConfig

Config used to request a token refresh, revocation, or code exchange.

TokenRequestConfig Properties

NameTypeDescription
clientIdstring

A unique string representing the registration information provided by the client. The client identifier is not a secret; it is exposed to the resource owner and shouldn't be used alone for client authentication.

The client identifier is unique to the authorization server.

Section 2.2

clientSecret
(optional)
string

Client secret supplied by an auth provider. There is no secure way to store this on the client.

Section 2.3.1

extraParams
(optional)
Record<string, string>

Extra query params that'll be added to the query string.

scopes
(optional)
string[]

List of strings to request access to.

Section 3.3


TokenResponseConfig

TokenResponseConfig Properties

NameTypeDescription
accessTokenstring

The access token issued by the authorization server.

Section 4.2.2

expiresIn
(optional)
number

The lifetime in seconds of the access token.

For example, the value 3600 denotes that the access token will expire in one hour from the time the response was generated.

If omitted, the authorization server should provide the expiration time via other means or document the default value.

Section 4.2.2

idToken
(optional)
string

ID Token value associated with the authenticated session.

TokenResponse

issuedAt
(optional)
number

Time in seconds when the token was received by the client.

refreshToken
(optional)
string

The refresh token, which can be used to obtain new access tokens using the same authorization grant.

Section 5.1

scope
(optional)
string

The scope of the access token. Only required if it's different to the scope that was requested by the client.

Section 3.3

state
(optional)
string

Required if the "state" parameter was present in the client authorization request. The exact value received from the client.

Section 4.2.2

tokenType
(optional)
TokenType

The type of the token issued. Value is case insensitive.

Section 7.1


Types

AuthRequestPromptOptions

Options passed to the promptAsync() method of AuthRequests. This can be used to configure how the web browser should look and behave.

Type: Omit<WebBrowserOpenOptions, 'windowFeatures'> extended by:


NameTypeDescription
url
(optional)
string

URL to open when prompting the user. This usually should be defined internally and left undefined in most cases.

windowFeatures
(optional)
WebBrowserWindowFeatures
Only for:
Web

Features to use with window.open().

AuthSessionOptions

NameTypeDescription
authUrlstring

The URL that points to the sign in page that you would like to open the user to.

projectNameForProxy
(optional)
string

Project name to use for the auth.expo.io proxy.

returnUrl
(optional)
string

The URL to return to the application. In managed apps, it's optional and defaults to output of Linking.createURL('expo-auth-session', params) call with scheme and queryParams params. However, in the bare app, it's required - AuthSession needs to know where to wait for the response. Hence, this method will throw an exception, if you don't provide returnUrl.

showInRecents
(optional)
boolean
Only for:
Android

A boolean determining whether browsed website should be shown as separate entry in Android recents/multitasking view.

Default:false

AuthSessionRedirectUriOptions

Options passed to makeRedirectUri.

NameTypeDescription
isTripleSlashed
(optional)
boolean

Should the URI be triple slashed scheme:///path or double slashed scheme://path. Defaults to false.

native
(optional)
string

Manual scheme to use in Bare and Standalone native app contexts. Takes precedence over all other properties. You must define the URI scheme that will be used in a custom built native application or standalone Expo application. The value should conform to your native app's URI schemes. You can see conformance with npx uri-scheme list.

path
(optional)
string

Optional path to append to a URI. This will not be added to native.

preferLocalhost
(optional)
boolean

Attempt to convert the Expo server IP address to localhost. This is useful for testing when your IP changes often, this will only work for iOS simulator.

Default:false
queryParams
(optional)
Record<string, string | undefined>

Optional native scheme URI protocol <scheme>:// that must be built into your native app.

scheme
(optional)
string

URI protocol <scheme>:// that must be built into your native app.

AuthSessionResult

Object returned after an auth request has completed.

  • If the user cancelled the authentication session by closing the browser, the result is { type: 'cancel' }.
  • If the authentication is dismissed manually with AuthSession.dismiss(), the result is { type: 'dismiss' }.
  • If the authentication flow is successful, the result is { type: 'success', params: Object, event: Object }.
  • If the authentication flow is returns an error, the result is { type: 'error', params: Object, error: string, event: Object }.

Type: object shaped as below:


NameTypeDescription
type'cancel' | 'dismiss' | 'opened' | 'locked'

How the auth completed.


NameTypeDescription
authenticationTokenResponse | null

Returned when the auth finishes with an access_token property.

error
(optional)
AuthError | null

Possible error if the auth failed with type error.

errorCodestring | null

Deprecated Legacy error code query param, use error instead.

paramsRecord<string, string>

Query params from the url as an object.

type'error' | 'success'

How the auth completed.

urlstring

Auth URL that was opened

Issuer

URL using the https scheme with no query or fragment component that the OP asserts as its Issuer Identifier.

Type: string

IssuerOrDiscovery

Literal Type: multiple types

Acceptable values are: Issuer | DiscoveryDocument

ProviderMetadata

OpenID Providers have metadata describing their configuration. ProviderMetadata

Type: Record<string, string | boolean | string[]> ProviderMetadataEndpoints extended by:


NameTypeDescription
backchannel_logout_session_supported
(optional)
boolean-
backchannel_logout_supported
(optional)
boolean-
check_session_iframe
(optional)
string-
claim_types_supported
(optional)
string[]

a list of the Claim Types that the OpenID Provider supports.

claims_locales_supported
(optional)
string[]

Languages and scripts supported for values in Claims being returned.

claims_parameter_supported
(optional)
boolean

Boolean value specifying whether the OP supports use of the claims parameter, with true indicating support.

Default:false
claims_supported
(optional)
string[]

a list of the Claim Names of the Claims that the OpenID Provider may be able to supply values for. Note that for privacy or other reasons, this might not be an exhaustive list.

code_challenge_methods_supported
(optional)
CodeChallengeMethod[]-
display_values_supported
(optional)
string[]

a list of the display parameter values that the OpenID Provider supports.

frontchannel_logout_session_supported
(optional)
boolean-
frontchannel_logout_supported
(optional)
boolean-
grant_types_supported
(optional)
string[]

JSON array containing a list of the OAuth 2.0 Grant Type values that this OP supports. Dynamic OpenID Providers MUST support the authorization_code and implicit Grant Type values and MAY support other Grant Types. If omitted, the default value is ["authorization_code", "implicit"].

id_token_signing_alg_values_supported
(optional)
string[]

JSON array containing a list of the JWS signing algorithms (alg values) supported by the OP for the ID Token to encode the Claims in a JWT. The algorithm RS256 MUST be included.

jwks_uri
(optional)
string

URL of the OP's JSON Web Key Set JWK document.

op_policy_uri
(optional)
string

URL that the OpenID Provider provides to the person registering the Client to read about the OP's requirements on how the Relying Party can use the data provided by the OP. The registration process SHOULD display this URL to the person registering the Client if it is given.

op_tos_uri
(optional)
string

URL that the OpenID Provider provides to the person registering the Client to read about OpenID Provider's terms of service. The registration process should display this URL to the person registering the Client if it is given.

request_parameter_supported
(optional)
boolean

Boolean value specifying whether the OP supports use of the request parameter, with true indicating support.

Default:false
request_uri_parameter_supported
(optional)
boolean

Whether the OP supports use of the request_uri parameter, with true indicating support.

Default:true
require_request_uri_registration
(optional)
boolean

Whether the OP requires any request_uri values used to be pre-registered using the request_uris registration parameter. Pre-registration is required when the value is true.

Default:false
response_modes_supported
(optional)
string[]

JSON array containing a list of the OAuth 2.0 response_mode values that this OP supports, as specified in OAuth 2.0 Multiple Response Type Encoding Practices. If omitted, the default for Dynamic OpenID Providers is ["query", "fragment"].

response_types_supported
(optional)
string[]

JSON array containing a list of the OAuth 2.0 response_type values that this OP supports. Dynamic OpenID Providers must support the code, id_token, and the token id_token Response Type values

scopes_supported
(optional)
string[]

JSON array containing a list of the OAuth 2.0 RFC6749 scope values that this server supports.

service_documentation
(optional)
string

URL of a page containing human-readable information that developers might want or need to know when using the OpenID Provider. In particular, if the OpenID Provider does not support Dynamic Client Registration, then information on how to register Clients needs to be provided in this documentation.

subject_types_supported
(optional)
string[]

JSON array containing a list of the Subject Identifier types that this OP supports. Valid types include pairwise and public.

token_endpoint_auth_methods_supported
(optional)
('client_secret_post' | 'client_secret_basic' | 'client_secret_jwt' | 'private_key_jwt' | string)[]

A list of Client authentication methods supported by this Token Endpoint. If omitted, the default is ['client_secret_basic']

ui_locales_supported
(optional)
string[]

Languages and scripts supported for the user interface, represented as a JSON array of BCP47 language tag values.

TokenType

Literal Type: string

Access token type.

Acceptable values are: 'bearer' | 'mac'

Enums

CodeChallengeMethod

CodeChallengeMethod Values

Plain

CodeChallengeMethod.Plain = "plain"

This should not be used. When used, the code verifier will be sent to the server as-is.

S256

CodeChallengeMethod.S256 = "S256"

The default and recommended method for transforming the code verifier.

  • Convert the code verifier to ASCII.
  • Create a digest of the string using crypto method SHA256.
  • Convert the digest to Base64 and URL encode it.

GrantType

Grant type values used in dynamic client registration and auth requests.

GrantType Values

AuthorizationCode

GrantType.AuthorizationCode = "authorization_code"

Used for exchanging an authorization code for one or more tokens.

Section 4.1.3

ClientCredentials

GrantType.ClientCredentials = "client_credentials"

Used for client credentials flow.

Section 4.4.2

Implicit

GrantType.Implicit = "implicit"

Used when obtaining an access token.

Section 4.2

RefreshToken

GrantType.RefreshToken = "refresh_token"

Used when exchanging a refresh token for a new token.

Section 6

Prompt

Informs the server if the user should be prompted to login or consent again. This can be used to present a dialog for switching accounts after the user has already been logged in. You should use this in favor of clearing cookies (which is mostly not possible on iOS).

Prompt Values

Consent

Prompt.Consent = "consent"

Server should prompt the user for consent before returning information to the client. If it cannot obtain consent, it must return an error, typically consent_required.

Login

Prompt.Login = "login"

The server should prompt the user to reauthenticate. If it cannot reauthenticate the End-User, it must return an error, typically login_required.

None

Prompt.None = "none"

Server must not display any auth or consent UI. Can be used to check for existing auth or consent. An error is returned if a user isn't already authenticated or the client doesn't have pre-configured consent for the requested claims, or does not fulfill other conditions for processing the request. The error code will typically be login_required, interaction_required, or another code defined in Section 3.1.2.6.

SelectAccount

Prompt.SelectAccount = "select_account"

Server should prompt the user to select an account. Can be used to switch accounts. If it can't obtain an account selection choice made by the user, it must return an error, typically account_selection_required.

ResponseType

The client informs the authorization server of the desired grant type by using the response type.

ResponseType Values

Code

ResponseType.Code = "code"

For requesting an authorization code as described by Section 4.1.1.

IdToken

ResponseType.IdToken = "id_token"

A custom registered type for getting an id_token from Google OAuth.

Token

ResponseType.Token = "token"

For requesting an access token (implicit grant) as described by Section 4.2.1.

TokenTypeHint

A hint about the type of the token submitted for revocation. If not included then the server should attempt to deduce the token type.

TokenTypeHint Values

AccessToken

TokenTypeHint.AccessToken = "access_token"

Access token.

Section 1.4

RefreshToken

TokenTypeHint.RefreshToken = "refresh_token"

Refresh token.

Section 1.5

Providers

AuthSession has built-in support for some popular providers to make usage as easy as possible. These allow you to skip repetitive things like defining endpoints and abstract common features like language.

Google

Deprecated: This provider is deprecated and will be removed in a future SDK version. See Google authentication instead.
import * as Google from 'expo-auth-session/providers/google';
  • See the guide for more info on usage: Google Authentication.

  • Provides an extra loginHint parameter. If the user's email address is known ahead of time, it can be supplied to be the default option.

  • Enforces minimum scopes to the following APIs for optimal usage with services like Firebase and Auth0.

    ['openid', 'https://www.googleapis.com/auth/userinfo.profile', 'https://www.googleapis.com/auth/userinfo.email']
    
  • By default, the authorization code will be automatically exchanged for an access token. This can be overridden with shouldAutoExchangeCode.

  • Defaults to using the bundle ID and package name for the native URI redirect instead of the reverse client ID.

  • Disables PKCE for implicit and id-token based auth responses.

  • On web, the popup is presented with the dimensions that are optimized for the Google login UI ({ width: 515, height: 680 }).

useAuthRequest()

A hook used for opinionated Google authentication that works across platforms.

Arguments

  • config (GoogleAuthRequestConfig) - A GoogleAuthRequestConfig object with client IDs for each platform that should be supported.
  • redirectUriOptions (AuthSessionRedirectUriOptions) - Optional properties used to construct the redirect URI (passed to makeRedirectUri()).

Returns

  • request (GoogleAuthRequest | null) - An instance of GoogleAuthRequest that can be used to prompt the user for authorization. This will be null until the auth request has finished loading.
  • response (AuthSessionResult | null) - This is null until promptAsync has been invoked. Once fulfilled it will return information about the authorization.
  • promptAsync (function) - When invoked, a web browser will open up and prompt the user for authentication. Accepts an AuthRequestPromptOptions object with options about how the prompt will execute.

discovery

A DiscoveryDocument object containing the discovery URLs used for Google auth.

Facebook

Deprecated: This provider is deprecated and will be removed in a future SDK version. See Facebook authentication instead.
import * as Facebook from 'expo-auth-session/providers/facebook';
  • Uses implicit auth (ResponseType.Token) by default.
  • See the guide for more info on usage: Facebook Authentication.
  • Enforces minimum scopes to ['public_profile', 'email'] for optimal usage with services like Firebase and Auth0.
  • Uses display=popup for better UI results.
  • Disables PKCE for implicit auth response.
  • On web, the popup is presented with the dimensions { width: 700, height: 600 }

useAuthRequest()

A hook used for opinionated Facebook authentication that works across platforms.

Arguments

  • config (FacebookAuthRequestConfig) - A FacebookAuthRequestConfig object with client IDs for each platform that should be supported.
  • redirectUriOptions (AuthSessionRedirectUriOptions) - Optional properties used to construct the redirect URI (passed to makeRedirectUri()).

Returns

  • request (FacebookAuthRequest | null) - An instance of FacebookAuthRequest that can be used to prompt the user for authorization. This will be null until the auth request has finished loading.
  • response (AuthSessionResult | null) - This is null until promptAsync has been invoked. Once fulfilled it will return information about the authorization.
  • promptAsync (function) - When invoked, a web browser will open up and prompt the user for authentication. Accepts an AuthRequestPromptOptions object with options about how the prompt will execute.

discovery

A DiscoveryDocument object containing the discovery URLs used for Facebook auth.

Advanced usage

Filtering out AuthSession events in Linking handlers

There are many reasons why you might want to handle inbound links into your app, such as push notifications or just regular deep linking (you can read more about this in the Linking guide); authentication redirects are only one type of deep link, and AuthSession handles these particular links for you. In your own Linking.addEventListener handlers, you can filter out deep links that are handled by AuthSession by checking if the URL includes the +expo-auth-session string -- if it does, you can ignore it. This works because AuthSession adds +expo-auth-session to the default returnUrl; however, if you provide your own returnUrl, you may want to consider adding a similar identifier to enable you to filter out AuthSession events from other handlers.

With React Navigation

If you are using deep linking with React Navigation, filtering through Linking.addEventListener will not be sufficient because deep linking is handled differently. Instead, to filter these events, add a custom getStateFromPath function to your linking configuration, and then filter by URL in the same way as described above.