oidc

The upstream issues got closed. It is referenced in:

• client/manager_test_helpers.go#L235

This issue was created by the ORY Closed Reference Notifier GitHub action.

Describe the bug

We are configuring a IdentityProvider in Keycloak with PKCE enabled and PKCE method "SH256". In the token request Keycloak sends the parameter "code_challenge_method" although it's non-standard. The Identity-Provider we configure cancels the request because the request body contains a non-standard parameter. For security reasons all requests with non-standard parameters ar

Provider type

Custom provider

Environment

next-auth 4.3.3
(I don't think any other version information is relevant, I looked at the source)

Reproduction URL

N/A

Describe the issue

I looked at the source and the declaration seems t

After we shuffled around the branches, codecov isn't working as expected.
I'm sure this is something silly, but I personally am not that into the code coverage game and don't feel like spending time on it. It would be nice if someone knowledgeable can give me a hand.

Description

The user should be able to add autocompletion through a cli call (e.g. zitadel completion bash)

Acceptance criteria

• it is possible to add the autocompletion of ZITADEL to .bashrc
• if a user writes zitadel in his terminal and presses tab the user gets proposals of what to do

Describe the bug
If the environment (in my case the stage environment) is not setup as a a secure origin the library break up cause of the crypto library is not in window object

To Reproduce
Steps to reproduce the behavior:

1. A server work on http that is setup as 'insecure origin'
2. Start the login sequence

Expected behavior
Warning on library loading that check secure or

Describe the issue:
The links not show hover states on hover on the getting started page.

How to reproduce:

1. Navigate to getting started page
2. hover over any link

Expected behavior:
Should indicate hover state for links

Our docs use cert-manager on GKE. It would be good to migrate them to use GKE workload identity so that the cluster does not need direct access to the GCP SA creds.