-
Updated
Aug 24, 2021 - JavaScript
oauth2
Here are 4,602 public repositories matching this topic...
-
Updated
Aug 27, 2021 - Java
-
Updated
Apr 22, 2021 - Java
-
Updated
Aug 29, 2021 - Java
-
Updated
Aug 20, 2021 - C#
Description 🐜
When using Credentials provider, the authorize callback should receive the incoming message object as the second parameter. However, on certain Node versions the incoming message has undefined
as headers
.
This happens on Node versions 14.15.2, >=15.1 and >=16.0 and is related to this change: nodejs/node#35281 There is an issue on Node but it is clo
-
Updated
Aug 5, 2021 - Java
-
Updated
Aug 23, 2021 - C++
-
Updated
Aug 15, 2021 - PHP
-
Updated
Aug 13, 2021 - Java
-
Updated
Aug 29, 2021 - Ruby
-
Updated
Jul 24, 2021 - JavaScript
-
Updated
Jul 2, 2021 - Java
-
Updated
Aug 10, 2021 - Java
-
Updated
Aug 17, 2021 - Swift
-
Updated
Jan 26, 2021 - Go
-
Updated
Aug 19, 2021 - Python
In the multipleParallelTransactionTest
, if we do not add the while(true)
loop in the ParallelTransactions
class, we get the following error:
java.net.SocketException: Connection reset by peer (connect failed)
at java.base/java.net.PlainSocketImpl.socketConnect(Native Method)
at java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:399)
at java.base/jav
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
Aug 28, 2021 - Python
-
Updated
Aug 27, 2021 - Java
-
Updated
Aug 18, 2021 - Python
-
Updated
Aug 29, 2021 - Groovy
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 pull got closed. It is referenced in:
This issue was created by the ORY Closed Reference Notifier GitHub action.