Middleware is calling getToken directly without providing any decode methods. By getToken() uses jwtDecrypt from jose package, and it will probably throws error when the JWT is not signed in the same way. It will throw error when we p
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:
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:
Expected behavior:
Should indicate hover state for links
After creating a custom login policy, the active identity providers are still listed from default. Same ist for MFA and 2FA, ...
From the screenshots below, you can see that the new policy is loaded after creation and reset. But only the policy itself and not the identity providers and factors:
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.
Add a description, image, and links to the oidc topic page so that developers can more easily learn about it.
To associate your repository with the oidc topic, visit your repo's landing page and select "manage topics."
Asking about this since the NSA recently published guidance advising the public and private sectors to transition to cryptographic algorithms that are no less than sha384 & ec384 (elliptic curves).
While Edwards' Curves are different, its worth noting that prior to this update sha256 & secp256k1 were both on the list of acceptable cryptographic algorithms. My deduction was that 128-bit securit