oidc
Here are 637 public repositories matching this topic...
Describe the bug
Our favicon is missing when opening the welcome page on chrome / macos (see additional details)
Version
<=latest
Expected behavior
Favicon is shown
Actual behavior
Favicon is missing on the welcome page. It shows up when opening other pages like login / admin ui, though.
How to Reproduce?
e.g.
kc.sh start-dev -> navigate to localhost:8080 -> see
In vercel/next.js#34316 (comment) I concluded that getInitialProps really does not play well with our auth model. There are simply much better solutions for this now.
We should discourage the usage of it entirely.
https://next-auth.js.org/tutorials/securing-pages-and-api-routes should be updated to also mention [Middleware support](https://next-auth.
-
Updated
Feb 12, 2022 - Go
-
Updated
Feb 15, 2022 - Python
-
Updated
Feb 13, 2022 - Python
-
Updated
Feb 7, 2022 - JavaScript
-
Updated
Feb 7, 2022 - JavaScript
-
Updated
Feb 14, 2022 - Python
-
Updated
Feb 10, 2022 - Go
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
Feb 4, 2022 - C
-
Updated
Feb 7, 2022 - C#
-
Updated
Feb 11, 2022 - TypeScript
-
Updated
Feb 14, 2022 - JavaScript
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
Feb 14, 2022 - Java
-
Updated
Feb 15, 2022 - Ruby
-
Updated
Feb 13, 2022 - C
-
Updated
Feb 14, 2022 - C#
-
Updated
Feb 15, 2022 - TypeScript
-
Updated
Feb 10, 2022 - Go
-
Updated
Dec 31, 2021
-
Updated
Jan 31, 2022 - 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
Feb 6, 2022 - C#
-
Updated
Feb 5, 2022
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