Axioms

Authorization

Authorize your end-users to access protected APIs, resources or functionalities
Authorization Flows
Specifically tailored for web apps, native apps, IoT devices, REST APIs, and microservices.
Consent
Fully customisable consent screen that describes scopes that the user is authorizing to the application.
Grants
After an authorization flow, OAuth client will receive tokens which are used to access protected resources.
Claims
Claims including the scope and optionally authorization details are embedded in issued tokens.
Authorization Grants
A range of OpenID Connect and OAuth 2.0 authorization grants are supported
Implicit Flow
Can be used by Single-page applications. After authorisation, access Token and ID Token are returned directly to the application as fragment component of the Redirection URI.
Authorization Code Flow
Can be used by server-side web applications. After authorization, application will get the authorization code from the URL and use it to request an access token from token endpoint.
Proof Key for Code Exchange (PKCE)
Can be used by mobile and single-page applications. Application includes a code challenge in authorisation request. Rest of the flow is similar to authorization code flow but now token endpoint will match authorization code with code challenge.
Device Authorization
Can be used by CLI application or IoT devices (smart TV, printers, gaming consoles, etc.) due to constrained browser access. In this flow client uses a pre-registered URL to get authorization from user via a user agent on a separate device or context.
Hybrid Flow
Combination of implicit flow and authorization code flow i.e. some tokens are returned from the authorization endpoint as fragment in redirect URI and others are exchanged from the token endpoint.
Client Credentials
Can be used by server side applications or backend services to obtain an access token outside of the context of a user.
Username Password
Can be used by first-party private clients only to exchange a user's credentials (username and password) for tokens.
Refresh Token
Can be used by private clients including mobile apps, server-side applications to exchange a refresh token for an access token when the access token has expired.
Passwordless
Custom grant type only supported by Axioms platform to exchange passwordless one-time code or magic link with tokens.
Authenticate your end-users using a range of strong authentication methods including username-password, passwordless, multi-factor, etc.