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

Doing a faulty POST Request on Token endpoint /realms/{realm-name}/protocol/openid-connect/token
here without form data and missing Content-Type leads to NullPointerException and HTTP 500 API response {"error":"unknown_error"}

For sure this is an usage error, but in other error case keycloak gives back clear error indication:

• Form data given, but Content-Type is mi

Environment

System:
OS: Linux 5.10 Ubuntu 20.04.4 LTS (Focal Fossa)
CPU: (12) x64 Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz
Memory: 9.57 GB / 15.58 GB
Container: Yes
Shell: 5.0.17 - /bin/bash
Binaries:
Node: 16.15.1 - ~/.nvm/versions/node/v16.15.1/bin/node
Yarn: 1.22.15 - ~/.nvm/versions/node/v16.15.1/bin/yarn
npm: 8.11.0 - ~/.nvm/versions/node/v1

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.

Internationalization French

Guide: https://github.com/zitadel/zitadel/blob/v2-alpha/CONTRIBUTING.md#contribute-internationalization

• Console texts
• Login Interface
• [Email Notifications](https://github.com/zitadel/z

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.