Package-level declarations
Types
How an authentication client can get the information about the authorization server
Functions
Discovers the authorization server and obtains tokens with fully pluggable grant and refresh flows. Use for scenarios where neither the initial grant nor refresh use client credentials (e.g. JWT assertions).
Discovers the authorization server and obtains tokens using the standard client_credentials grant. Suitable for machine-to-machine scenarios with a client ID and secret.
Discovers the authorization server and obtains tokens using a custom initial grant flow but standard client_credentials-based refresh. Use when the initial grant is non-standard (e.g. JWT assertion) but refresh still uses client credentials.
OAuth JWT Bearer assertion grant (RFC 7523). Used for enterprise auth flows where the client authenticates with a JWT instead of client credentials.
OAuth Resource Owner Password Credentials grant with explicit client credentials.
OAuth Resource Owner Password Credentials grant. Authenticates with both client credentials and end-user username/password. Generally discouraged in favour of authorization code flow, but useful for legacy systems or trusted first-party clients.
Obtains and refreshes OAuth tokens using the standard client_credentials grant from the provider config. Suitable for machine-to-machine scenarios with a client ID and secret.
Obtains and refreshes OAuth tokens using the standard client_credentials grant. Suitable for machine-to-machine scenarios with a client ID and secret.
Obtains and refreshes OAuth tokens with fully pluggable grant and refresh flows. Use for scenarios where neither the initial grant nor refresh use client credentials (e.g. JWT assertions, ID-JAG).
Obtains and refreshes OAuth tokens with a custom initial grant flow but standard client_credentials-based refresh. Use when the initial grant is non-standard but the client has credentials for refreshing tokens.