-
Updated
Jan 19, 2021 - JavaScript
oauth2
Here are 4,126 public repositories matching this topic...
Describe the bug
Thank you for a great project and documentation. I ran into a bug (I think) while playing with the 5 minute tutorial.
When revoking an access token that is not found the hydra server returns a 404 response but this is not a defined response in the swagger specification. This leads to an error like `response status code does not match any response statuses defined for thi
-
Updated
Jan 20, 2021 - Java
-
Updated
Feb 16, 2021 - Java
-
Updated
Jan 26, 2021 - C#
-
Updated
Feb 12, 2021 - C++
-
Updated
Jan 18, 2021 - Java
-
Updated
Feb 11, 2021 - PHP
-
Updated
Jan 31, 2021 - Java
-
Updated
Feb 6, 2021 - Ruby
Describe the bug
Email Provider authentication does not create user account in account
table in database after successful authentication (only if new user)
Do not report bugs with your own project here, ask from help by raising a question instead - this helps us a lot with administration overhead.
Steps to reproduce
- Sign in using Email
- Verify email will be sent to specif
-
Updated
Jan 27, 2021 - JavaScript
-
Updated
Dec 13, 2020 - Java
-
Updated
Jan 19, 2021 - Swift
-
Updated
Jan 26, 2021 - Go
-
Updated
Feb 3, 2021 - Java
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
Feb 12, 2021 - Python
-
Updated
Feb 16, 2021 - Python
-
Updated
Feb 12, 2021 - Python
-
Updated
Jan 20, 2021 - Java
Instead, quite the container and print out an appropriate error message
-
Updated
Feb 16, 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."
Why did you add this feature?
Feature description
支持 “企业微信登录” 作为一个第三方登录的方案
目前的企业微信登录看了文档,应该是用企业微信登录这个企业自己的网站
而不是用企业微信登录我的网站,不是个公共的方案
区别是应该是下面这个文档
https://open.work.weixin.qq.com/api/doc/90001/90143/91123