oidc

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

Describe the bug

Reported in: https://issues.redhat.com/browse/KEYCLOAK-19520

PolicyEnforcerConfig.PathCacheConfig is missing @JsonProperty annotation that results in the following error when it is set for example, in Spring security yaml config

The way basic-tests is written currently, each adapter method test run depend on previous tests to succeed. This way easier to write initially, but as a result, it is much harder to debug the original cause of an issue while debugging/working on an adapter.

We should refactor basic-tests so tests don't rely on each other to succeed.

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

The lack of open API schema support for the concierge aggregated APIs results in the following scary log messages in the API server logs:

E1229 15:34:45.928937       1 controller.go:116] loading OpenAPI spec for "v1alpha1.login.concierge.pinniped.dev" failed with: OpenAPI spec does not exist
I1229 15:34:45.928949       1 controller.go:129] OpenAPI AggregationController: action for item v1