Why did you add this feature?

Feature description

支持 “企业微信登录” 作为一个第三方登录的方案

目前的企业微信登录看了文档，应该是用企业微信登录这个企业自己的网站

而不是用企业微信登录我的网站，不是个公共的方案

区别是应该是下面这个文档
https://open.work.weixin.qq.com/api/doc/90001/90143/91123

API documentation for nodejs client for hydra returns a 404

The link mentioned in the documentation: https://github.com/ory/hydra/blob/master/sdk/js/swagger/README.md

Summary of proposed feature
I would like to use the Dataswift.io solution directly in next-auth

Purpose of proposed feature
It simplifies the auth/registration process to simple few steps.

Detail about proposed feature
I would like to see Dataswift auth in the same way as auth0

Potential problems

Describe any alternatives you've considered
Create a separate m

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

Instead, quite the container and print out an appropriate error message