oidc
Here are 614 public repositories matching this topic...
Fixed keycloak/keycloak#9382
- Do not try to gzunzip based on input stream content as this may lead to unexpected behaviour in some cases were the data is not gzip encoded (e.g. random input as described in the but ticket). Use option flags instead for explicit control.
- Unify two parallel exiting implementations of the Base64 class (they already started diverging in
Description 🐜
With the removal of clientMaxAge and keepAlive in favor of refetchInterval, every time a tab is switched, the session gets revalidated, thus updating a session state in SessionProvider which then causes to rerender all components using useSession.
Is it possible to disable this "revalidation" upon window refocusing?
Thanks in advance.
Is this a bug in your own
-
Updated
Dec 30, 2021 - Go
-
Updated
Jan 4, 2022 - Python
-
Updated
Dec 23, 2021 - Python
-
Updated
Jan 4, 2022 - JavaScript
-
Updated
Dec 20, 2021 - JavaScript
-
Updated
Jan 5, 2022 - Python
-
Updated
Dec 24, 2021 - C
-
Updated
Dec 28, 2021 - C#
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:
- A server work on http that is setup as 'insecure origin'
- Start the login sequence
Expected behavior
Warning on library loading that check secure or
-
Updated
Jan 3, 2022 - Go
-
Updated
Jan 2, 2022 - TypeScript
Describe the issue:
The links not show hover states on hover on the getting started page.
How to reproduce:
- Navigate to getting started page
- hover over any link
Expected behavior:
Should indicate hover state for links
-
Updated
Jan 4, 2022 - JavaScript
-
Updated
Dec 30, 2021 - Java
-
Updated
Jan 2, 2022 - C
-
Updated
Dec 20, 2021 - TypeScript
-
Updated
Jan 4, 2022 - C#
-
Updated
Jan 4, 2022 - Go
-
Updated
Dec 31, 2021
-
Updated
Mar 4, 2021 - Go
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
-
Updated
Dec 13, 2021 - JavaScript
-
Updated
Nov 21, 2021 - Go
-
Updated
Jun 8, 2021 - C#
-
Updated
Jul 8, 2021
-
Updated
Sep 21, 2021 - JavaScript
Improve this page
Add a description, image, and links to the oidc topic page so that developers can more easily learn about it.
Add this topic to your repo
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