mqf20 3edc81ed9a feat: allow setting op.Crypto during provider setup (#778) ...

Add a `op.WithCrypto` `op.Option` that allows developers to specify
their custom `op.Crypto` implementations during setup. If the
`op.Option` is used, it will override `op.Config.CryptoKey`.

Closes https://github.com/zitadel/oidc/issues/736.

### Definition of Ready

- [x] I am happy with the code
- [x] Short description of the feature/issue is added in the pr
description
- [x] PR is linked to the corresponding user story
- [ ] Acceptance criteria are met
- [ ] All open todos and follow ups are defined in a new ticket and
justified
- [ ] Deviations from the acceptance criteria and design are agreed with
the PO and documented.
- [x] No debug or dead code
- [ ] My code has no repetitions
- [ ] Critical parts are tested automatically
- [ ] Where possible E2E tests are implemented
- [x] Documentation/examples are up-to-date
- [ ] All non-functional requirements are met
- [ ] Functionality of the acceptance criteria is checked manually on
the dev system.

---------

Signed-off-by: mqf20 <mingqingfoo@gmail.com>
Co-authored-by: Tim Möhlmann <tim+github@zitadel.com>

2025-08-05 12:00:11 +00:00

..

client

feat(rp): optional authorized party check (#752)

2025-07-31 08:36:27 +00:00

crypto

feat(crypto): hash algorithm for EdDSA (#638)

2024-08-21 07:32:13 +00:00

http

feat: Request aware cookie handling (#753)

2025-07-16 11:33:03 +00:00

oidc

feat(rp): optional authorized party check (#752)

2025-07-31 08:36:27 +00:00

op

feat: allow setting op.Crypto during provider setup (#778)

2025-08-05 12:00:11 +00:00

strings

refactor: mark pkg/strings as deprecated in favor of stdlib (#680)

2024-11-15 18:47:32 +02:00