-
Updated
Nov 8, 2020 - JavaScript
oauth2
Here are 3,955 public repositories matching this topic...
-
Updated
Nov 6, 2020 - Java
-
Updated
Jul 1, 2020 - Java
-
Updated
Nov 30, 2020 - Java
-
Updated
Nov 26, 2020 - C#
-
Updated
Nov 24, 2020 - C++
-
Updated
Nov 30, 2020 - PHP
-
Updated
Nov 14, 2020 - Java
-
Updated
Nov 30, 2020 - Java
-
Updated
Nov 26, 2020 - Ruby
-
Updated
Nov 29, 2020 - Java
-
Updated
Nov 28, 2020 - JavaScript
-
Updated
Nov 14, 2020 - Swift
-
Updated
Sep 12, 2020 - Go
If not for some particular exceptions, the status code returned from our WebAPI on error is always 500, regardless of the kind of error.
If an object already exists, for example, it should be returned as 409
. If the object does not pass the schema validation, it should be a 415
.
Go through the whole WebAPI and verify that the status codes are being returned correctly.
Hint: Error
cl
-
Updated
Nov 30, 2020 - Java
-
Updated
Nov 24, 2020 - Python
-
Updated
Nov 24, 2020 - Python
-
Updated
Nov 22, 2020 - Python
-
Updated
Nov 19, 2020 - Java
-
Updated
Nov 30, 2020 - Groovy
-
Updated
Oct 19, 2020 - Go
Improve this page
Add a description, image, and links to the oauth2 topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the oauth2 topic, visit your repo's landing page and select "manage topics."
Describe the bug
After Hydra startup log warns about configuration key deprecation. There is no records in documentation reference (https://www.ory.sh/hydra/docs/reference/configuration/) about oidc.subject_identifiers.supported_types.
Reproducing the bug
Steps to reproduce the behavior:
Start Hydra Hydra v1.9.0-alpha.2 with oidc.subject_identifiers.enabled set to public
_Se