-
Updated
Oct 17, 2020 - JavaScript
oauth2
Here are 3,875 public repositories matching this topic...
-
Updated
Oct 13, 2020 - Java
-
Updated
Jul 1, 2020 - Java
-
Updated
Oct 22, 2020 - Java
-
Updated
Oct 21, 2020 - C#
-
Updated
Oct 22, 2020 - C++
-
Updated
Oct 1, 2020 - PHP
-
Updated
Oct 13, 2020 - Java
-
Updated
Oct 12, 2020 - Java
-
Updated
Sep 3, 2020 - Ruby
-
Updated
Sep 16, 2020 - Java
-
Updated
Oct 11, 2020 - JavaScript
-
Updated
Sep 7, 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
Oct 13, 2020 - Java
-
Updated
Oct 21, 2020 - Python
-
Updated
Aug 3, 2020 - Python
-
Updated
Oct 22, 2020 - Python
-
Updated
Oct 13, 2020 - Java
-
Updated
Oct 22, 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."
Is your feature request related to a problem? Please describe.
AWS Fargate and ECS is a popular container cluster. Jaeger and datadog are not native to AWS, require additional setup, cost and operations. AWS X-Ray support distributed tracing for ECS and AWS lambda. A custom lambda can be developed for oauth2 token validation against Hydra. Currently tracing between lambda authorizer and hyd