fix(deps): update module github.com/zitadel/oidc/v3 to v3.47.5

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/zitadel/oidc/v3	v3.45.5 → v3.47.5

---

Release Notes

zitadel/oidc (github.com/zitadel/oidc/v3)

v3.47.5

Compare Source

Bug Fixes

• op: allow dynamic loopback ports in post_logout_redirect_uri per RFC 8252 §7.3 (#​875) (fb9fbfe), closes /datatracker.ietf.org/doc/html/rfc8252#section-7 zitadel/zitadel#6615

v3.47.4

Compare Source

Bug Fixes

• URL-encode client credentials in Basic Auth per RFC 6749 §2.3.1 (#​873) (178e018), closes /datatracker.ietf.org/doc/html/rfc6749#section-2 #​857 #​858

v3.47.3

Compare Source

Bug Fixes

• propagate signature verification errors correctly (#​872) (49664bf)

v3.47.2

Compare Source

Bug Fixes

• tolerate string amr claims from external providers (#​855) (5f70eff)

v3.47.1

Compare Source

Bug Fixes

• oidc server error to http status mapping (#​865) (d118dd7)

v3.47.0

Compare Source

This release adds signing of opaque tokens. By secure default, all existing opaque access tokens emitted by OP implementations, will be invalid. Users will need to re-login. If you want a more gradual upgrade use the op.WithCrypto() option to pass a op.NewCompositeCrypto(). Use aop.NewAESCrypto() in the Decrypter slice with the existing master key.

This change does not affect client / RP / RS libraries.

What's Changed

• feat: use jose for bearer-token encryption by @​wim07101993 in b4cf422
• chore: package upgrades by @​wim07101993 in #​866

Full Changelog: zitadel/oidc@v3.46.0...v3.47.0

v3.46.0

Compare Source

Features

• Allow for reuse of cookie creation + decouple creation from http writer (#​848) (4fae59b), closes #​847

v3.45.6

Compare Source

Bug Fixes

• fixed a bunch of typos in both docs, tests and code (#​861) (cab66d5)

---

Configuration

📅 Schedule: (UTC)

• 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 11 additional dependencies were updated

Details:

Package	Change
golang.org/x/oauth2	v0.30.0 -> v0.33.0
golang.org/x/sync	v0.16.0 -> v0.18.0
go.opentelemetry.io/otel	v1.37.0 -> v1.38.0
go.opentelemetry.io/otel/metric	v1.37.0 -> v1.38.0
go.opentelemetry.io/otel/trace	v1.37.0 -> v1.38.0
golang.org/x/crypto	v0.39.0 -> v0.45.0
golang.org/x/net	v0.41.0 -> v0.47.0
golang.org/x/sys	v0.33.0 -> v0.38.0
golang.org/x/term	v0.32.0 -> v0.37.0
golang.org/x/text	v0.27.0 -> v0.31.0
golang.org/x/tools	v0.34.0 -> v0.38.0

[joggrbot]

📝 Documentation Analysis

All docs are up to date! 🎉

---

✅ Latest commit analyzed: a2a5eee | Powered by Joggr

[renovate]

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 13 additional dependencies were updated
• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.24.10 -> 1.25.0
golang.org/x/oauth2	v0.35.0 -> v0.36.0
golang.org/x/sync	v0.19.0 -> v0.20.0
github.com/go-jose/go-jose/v4	v4.1.3 -> v4.1.4
go.opentelemetry.io/otel	v1.40.0 -> v1.43.0
go.opentelemetry.io/otel/metric	v1.40.0 -> v1.43.0
go.opentelemetry.io/otel/trace	v1.40.0 -> v1.43.0
golang.org/x/crypto	v0.47.0 -> v0.49.0
golang.org/x/mod	v0.32.0 -> v0.34.0
golang.org/x/net	v0.49.0 -> v0.52.0
golang.org/x/sys	v0.40.0 -> v0.42.0
golang.org/x/term	v0.39.0 -> v0.41.0
golang.org/x/text	v0.34.0 -> v0.36.0
golang.org/x/tools	v0.41.0 -> v0.43.0

[cla-assistant]

All committers have signed the CLA.

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}