- Code Flow with PKCE Using a configuration from an http source and silent renew
- Code Flow PKCE with Refresh tokens
- Code Flow PKCE Auto login
- Code Flow with PKCE basic with silent renew
- Azure B2C Code Flow PKCE with silent renew
- Azure AD Code Flow PKCE with silent renew
- Implicit Flow with silent renew (Not recommended)
- Implicit Flow google (Not recommended)
- Code flow with a lazy loaded module
Sometimes it is required to load the configuration from an http address. You can load the config from your source, map it into the required format and use the withConfig(...)
function.
The properties used in this example are just for demo purposes, you can used any definitions.
The Code flow with PKCE uses refresh tokens to refresh the session and a the end of the session, the user can logout and revoke the tokens. The demo is setup to use each refresh token only once.
The example logins the user in directly without a login click using the Code Flow with PKCE and an Auth Guard.
The is the basic example of the Code Flow with PKCE.
The example uses the Code Flow PKCE with Silent renew with Azure B2C as the STS.
Azure AD sample using OpenID Connect Code Flow with PKCE and a iframe silent renew
The example uses the Implicit Flow with silent renew. This flow is no longer recommended, but some servers support this flow only, and not the Code flow with PKCE.
The example uses the Implicit Flow with silent renew with google. This flow is no longer recommended, but some servers support this flow only, and not the Code flow with PKCE.
The example uses the Code flow with silent renew but you authenticate in a lazy loaded module