-
Updated
Mar 29, 2022 - JavaScript
oauth2
Here are 5,239 public repositories matching this topic...
-
Updated
Jan 3, 2022 - Java
Provider type
Custom provider
Environment
next-auth 4.3.3
(I don't think any other version information is relevant, I looked at the source)
Reproduction URL
N/A
Describe the issue
I looked at the source and the declaration seems t
-
Updated
Apr 28, 2022 - Java
-
Updated
Mar 8, 2022 - Java
-
Updated
Apr 24, 2022 - C#
-
Updated
Apr 23, 2022 - Java
-
Updated
Mar 10, 2022 - C++
-
Updated
Apr 19, 2022 - PHP
-
Updated
Apr 13, 2022 - Java
-
Updated
Apr 28, 2022 - Ruby
-
Updated
Mar 9, 2022 - JavaScript
-
Updated
Jul 2, 2021 - Java
-
Updated
Apr 18, 2022 - Java
-
Updated
Mar 4, 2022 - JavaScript
-
Updated
Apr 25, 2022 - PHP
-
Updated
Apr 22, 2022 - Java
-
Updated
Jan 26, 2021 - Go
-
Updated
Apr 23, 2022 - Python
-
Updated
Apr 21, 2022 - Swift
-
Updated
Apr 24, 2022 - Python
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
Preflight checklist
- I could not find a solution in the existing issues, docs, nor discussions.
- I agree to follow this project's Code of Conduct.
- I have read and am following this repository's Contribution Guidelines.
- This issue affec
-
Updated
Apr 27, 2022 - C#
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."
The upstream issues got closed. It is referenced in:
This issue was created by the ORY Closed Reference Notifier GitHub action.