fix(deps): update module github.com/zitadel/oidc to v3.23.2 #2416
+19
−21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![trap-renovate[bot]](https://avatars.githubusercontent.com/in/355677?s=60&v=4){kind=small}
trap-renovate
bot
added
renovate/gomod
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
trap-renovate
bot
force-pushed
the
renovate/github.com-zitadel-oidc-3.x
branch
from
0bfd422 to
6c74b48
Compare
trap-renovate
bot
force-pushed
the
renovate/github.com-zitadel-oidc-3.x
branch
from
6c74b48 to
4deac11
Compare
trap-renovate
bot
force-pushed
the
renovate/github.com-zitadel-oidc-3.x
branch
from
4deac11 to
485f827
Compare
trap-renovate
bot
force-pushed
the
renovate/github.com-zitadel-oidc-3.x
branch
from
485f827 to
590cb14
Compare
motoki317
approved these changes
May 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.13.5->v3.23.2Release Notes
zitadel/oidc (github.com/zitadel/oidc)
v3.23.2Compare Source
Bug Fixes
RefreshTokenRequestwhen performing a token refresh (#599) (5a84d8c)v3.23.1Compare Source
Bug Fixes
v3.23.0Compare Source
Features
v3.22.1Compare Source
Bug Fixes
v3.22.0Compare Source
Features
v3.21.0Compare Source
Features
v3.20.1Compare Source
Bug Fixes
v3.20.0Compare Source
Features
v3.19.0Compare Source
Features
v3.18.0Compare Source
Features
v3.17.0Compare Source
Features
v3.16.0Compare Source
Features
v3.15.0Compare Source
Features
v3.14.0Compare Source
Features
v3.13.0Compare Source
Features
v3.12.0Compare Source
Features
v3.11.2Compare Source
Bug Fixes
v3.11.1Compare Source
Bug Fixes
v3.11.0Compare Source
Features
v3.10.3Compare Source
Bug Fixes
v3.10.2Compare Source
Bug Fixes
v3.10.1Compare Source
Bug Fixes
v3.10.0Compare Source
Features
v3.9.1Compare Source
Bug Fixes
v3.9.0Compare Source
Features
v3.8.1Compare Source
Bug Fixes
v3.8.0Compare Source
Features
v3.7.0Compare Source
Features
v3.6.0Compare Source
Features
v3.5.1Compare Source
Bug Fixes
v3.5.0Compare Source
Features
v3.4.0Compare Source
Features
v3.3.1Compare Source
Bug Fixes
v3.3.0Compare Source
Features
v3.2.1Compare Source
Bug Fixes
v3.2.0Compare Source
Features
v3.1.1Compare Source
Bug Fixes
v3.1.0Compare Source
Features
v3.0.3Compare Source
Bug Fixes
v3.0.2Compare Source
What's Changed
Full Changelog: zitadel/oidc@v3.0.1...v3.0.2
v3.0.1Compare Source
Bug Fixes
v3.0.0Compare Source
Bug Fixes
chore
replace gorilla/mux with go-chi/chi (#332) (57fb9f7), closes #301
Merge pull request #456 from zitadel/next-main (976b406), closes #456
Features
BREAKING CHANGES
This change allows the return of the id_token in an explicit manner,
as part of the oidc.Tokens struct.
The return type is now consistent with the CodeExchange function.
When an id_token is returned, it is verified.
In case no id_token was received,
RefreshTokens will not return an error.
As per specifictation:
https://openid.net/specs/openid-connect-core-1\_0.html#RefreshTokenResponse
Upon successful validation of the Refresh Token,
the response body is the Token Response of Section 3.1.3.3
except that it might not contain an id_token.
a type parameter.
this binds the correct contstructor to each verifier usecase.
fix: handle the zero cases for oidc.Time
add unit tests to oidc verifier
fix: correct returned field for JWTTokenRequest
JWTTokenRequest.GetIssuedAt() was returning the ExpiresAt field.
This change corrects that by returning IssuedAt instead.
op.CreateRouter()is now achi.Routerv2.12.0Compare Source
Features
v2.11.0Compare Source
Features
v2.10.0Compare Source
Features
v2.9.0Compare Source
Features
v2.8.3Compare Source
Bug Fixes
v2.8.2Compare Source
Bug Fixes
v2.8.1Compare Source
Bug Fixes
v2.8.0Compare Source
Features
v2.7.0Compare Source
Features
v2.6.4Compare Source
Bug Fixes
v2.6.3Compare Source
Bug Fixes
v2.6.2Compare Source
Bug Fixes
v2.6.1Compare Source
Bug Fixes
v2.6.0Compare Source
Features
v2.5.0Compare Source
Features
v2.4.0Compare Source
Features
v2.3.0Compare Source
Features
v2.2.6Compare Source
Bug Fixes
v2.2.5Compare Source
Bug Fixes
v2.2.4Compare Source
Bug Fixes
v2.2.3Compare Source
Bug Fixes
v2.2.2Compare Source
Bug Fixes
v2.2.1Compare Source
Bug Fixes
v2.2.0Compare Source
Features
v2.1.2Compare Source
Bug Fixes
v2.1.1Compare Source
Bug Fixes
v2.1.0Compare Source
Features
v2.0.0Compare Source
Bug Fixes
chore
Code Refactoring
Features
BREAKING CHANGES
The following methods of OPStorage now take a pointer to a struct type,
instead of an interface:
The following functions are now generic, so that type-safe extension
of Claims is now possible:
op.VerifyIDTokenHint
op.VerifyAccessToken
rp.VerifyTokens
rp.VerifyIDToken
Changed UserInfoAddress to pointer in UserInfo and
IntrospectionResponse.
This was needed to make omitempty work correctly.
Copy or merge maps in IntrospectionResponse and SetUserInfo
op: add example for VerifyAccessToken
fix: rp: wrong assignment in WithIssuedAtMaxAge
WithIssuedAtMaxAge assigned its value to v.maxAge, which was wrong.
This change fixes that by assiging the duration to v.maxAgeIAT.
rp: add VerifyTokens example
oidc: add standard references to:
./pkg/...The call chain of above functions did not use the context anywhere.
This change removes the context from those fucntion arguments.
Configurationinterface:Issuer() stringhas been changed toIssuerFromRequest(r *http.Request) stringInsecure() boolhas been addedIssuerhas been removed from Config structNewOpenIDProvidernow takes an additional parameterissuerand returns a pointer to the public/default implementation and not an OpenIDProvider interface:NewOpenIDProvider(ctx context.Context, config *Config, storage Storage, opOpts ...Option) (OpenIDProvider, error)changed toNewOpenIDProvider(ctx context.Context, issuer string, config *Config, storage Storage, opOpts ...Option) (*Provider, error)Option func(o *Provider) errorAuthCallbackURL(o OpenIDProvider) func(string) stringhas been changed toAuthCallbackURL(o OpenIDProvider) func(context.Context, string) stringIDTokenHintVerifier() IDTokenHintVerifier(Authorizer, OpenIDProvider, SessionEnder interfaces),AccessTokenVerifier() AccessTokenVerifier(Introspector, OpenIDProvider, Revoker, UserinfoProvider interfaces) andJWTProfileVerifier() JWTProfileVerifier(IntrospectorJWTProfile, JWTAuthorizationGrantExchanger, OpenIDProvider, RevokerJWTProfile interfaces) now take a context.Context parameterIDTokenHintVerifier(context.Context) IDTokenHintVerifier,AccessTokenVerifier(context.Context) AccessTokenVerifierandJWTProfileVerifier(context.Context) JWTProfileVerifierOidcDevMode(CAOS_OIDC_DEV) environment variable check has been removed, useWithAllowInsecure()OptionSignerinterface and funcNewSignerhave been removedReadySigner(s Signer) ProbesFnhas been removedCreateDiscoveryConfig(c Configuration, s Signer) *oidc.DiscoveryConfigurationhas been changed toCreateDiscoveryConfig(r *http.Request, config Configuration, storage DiscoverStorage) *oidc.DiscoveryConfigurationStorageinterface:GetSigningKey(context.Context, chan<- jose.SigningKey)has been changed toSigningKey(context.Context) (SigningKey, error)KeySet(context.Context) ([]Key, error)has been addedGetKeySet(context.Context) (*jose.JSONWebKeySet, error)has been changed toKeySet(context.Context) ([]Key, error)SigAlgorithms(s Signer) []stringhas been changed toSigAlgorithms(ctx context.Context, storage DiscoverStorage) []stringGetKeySet(context.Context) (*jose.JSONWebKeySet, error)has been changed toKeySet(context.Context) ([]Key, error)CreateIDToken: the Signer parameter has been removedmove example
fix examples
fix mocks
update readme
fix examples and update usage
update go module version to v2
build branch
fix(module): rename caos to zitadel
fix: add state in access token response (implicit flow)
fix: encode auth response correctly (when using query in redirect uri)
fix query param handling
feat: add all optional claims of the introspection response
fix: use default redirect uri when not passed
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.