| LandingPages |
|
| OktaAuthenticators |
|
| OktaAuthenticators.OktaAuthenticationClient |
|
| OktaAuthenticators.OktaNativeSSOClient |
From https://developer.okta.com/docs/guides/configure-native-sso/main
Native SSO allows you to protect native OpenID Connect applications, such as
desktop apps and mobile apps, and achieve Single Sign-On (SSO) and Single
Logout (SLO) between these applications.
|
| OktaAuthenticators.OktaNativeSSOToken |
From https://developer.okta.com/docs/guides/configure-native-sso/main
Native SSO allows you to protect native OpenID Connect applications, such as
desktop apps and mobile apps, and achieve Single Sign-On (SSO) and Single
Logout (SLO) between these applications.
|
| OpenIDAuthenticators |
|
| OpenIDAuthenticators.AuthorizationCodeCallbackResource |
|
| OpenIDAuthenticators.AuthorizationCodeWithPKCEClient |
The PKCE-enhanced Authorization Code Flow introduces a secret created by the
calling application that can be verified by the authorization server; this
secret is called the Code Verifier.
|
| OpenIDAuthenticators.AuthorizationCodeWithPKCEClient.AuthorizationCodeGrant<T extends Token> |
The authorization code is obtained by using an authorization server as an
intermediary between the client and resource owner.
|
| OpenIDAuthenticators.DeviceAuthorizationGrant<T extends Token> |
The Device Authorization Grant is an extension that enables devices with no
browser or limited input capability to use OAuth.
|
| OpenIDAuthenticators.DeviceAuthorizationGrantClient |
From https://datatracker.ietf.org/doc/html/rfc8628
The OAuth 2.0 device authorization grant is designed for Internet-connected
devices that either lack a browser to perform a user-agent-based
authorization or are input constrained to the extent that requiring the user
to input text in order to authenticate during the authorization flow is
impractical.
|
| OpenIDAuthenticators.OAuthToken |
Token(s) received from an OAuth 2.0 Token Endpoint
|