Why did you add this feature?

Feature description

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

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

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

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

Is your feature request related to a problem? Please describe.

May we make the Jaeger configuration maxTagValueLength be configureable for ory/x/tracing tracer.go ?
The default length 256 isn't enough for we observe the query.

Describe the solution you'd like

Configuration in yaml like

tracing:
  service_name: or

Summary of proposed feature
AppWrite.io is an open-source Firebase-like project that provides authentication features via REST.

Purpose of proposed feature
Have Next-Auth work with it.

Detail about proposed feature
They have a User API https://appwrite.io/docs/server/users and an Account API https://appwrite.io/docs/client/account. I think the latter seems like the one that s

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