oauth2

Why did you add this feature?

Feature description

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

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

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

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

The upstream pull got closed. It is referenced in:

• driver/registry_base.go#L246

This issue was created by the ORY Closed Reference Notifier GitHub action.

Description 🐜

Follow-up for #2236 , as I was browsing the code changes I noticed that the redirect in useSession doesn't use the basePath settings that are set from NEXTAUTH_URL. We use a slightly different url paths in our project (/api/v1/auth/...) so we rely on everything being parsed from from `NEXTAUTH_URL

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

The repo containing the Dockerfile and the entrypoint is here.