package
2.12.2
Repository: https://github.com/zitadel/oidc.git
Documentation: pkg.go.dev

# Functions

No description provided by the author
DeviceClient creates a device client with Basic authentication.
No description provided by the author
NativeClient will create a client of type native, which will always use PKCE and allow the use of refresh tokens user-defined redirectURIs may include: - http://localhost without port specification (e.g.
NewMultiStorage implements the op.Storage interface by wrapping multiple storage structs and selecting them by the calling issuer.
No description provided by the author
No description provided by the author
No description provided by the author
RedirectGlobsClient wraps the client in a op.HasRedirectGlobs only if DevMode is enabled.
RefreshTokenRequestFromBusiness will simply wrap the storage RefreshToken to implement the op.RefreshTokenRequest interface.
RegisterClients enables you to register clients for the example implementation there are some clients (web and native) to try out different cases add more if necessary RegisterClients should be called before the Storage is used so that there are no race conditions.
WebClient will create a client of type web, which will always use Basic Auth and allow the use of refresh tokens user-defined redirectURIs may include: - http://localhost with port specification (e.g.

# Constants

CustomClaim is an example for how to return custom claims with this library.
CustomScope is an example for how to use custom scopes in this library(in this scenario, when requested, it will return a custom claim).
CustomScopeImpersonatePrefix is an example scope prefix for passing user id to impersonate using token exchage.

# Structs

No description provided by the author
Client represents the storage model of an OAuth/OIDC client this could also be your database model.
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
storage implements the op.Storage interface typically you would implement this as a layer on top of your database for simplicity this example keeps everything in-memory.
No description provided by the author
No description provided by the author

# Interfaces

No description provided by the author