Request for JWKS Endpoint and OIDC Discovery Support in Appwrite Authentication

Hey Appwrite Team,
Do you have plans to support JWKS and a well-known OIDC discovery endpoint?
This would let us verify Appwrite JWTs in other services using standard JWT/JWKS flows instead of calling Appwrite directly.

auth/v1/.well-known/jwks.json

Looking forward to any updates.

@role

Sorry for ping

@role

Hey, please don't ping moderators. Specially not after pinging the support role.

If this wasn't answered yet it either is not planned, or someone wasn't able to answer yet/have the answer.

I am not aware of any plans at all for this, check github, if not present open an issue and hope people up vote it

“Sorry for ping” pings another team right away hah

Checking the GitHub issues now. I’ll give the team some time to respond to my query; if I don’t hear back soon, I’ll go ahead and open a new issue.

Due to thr fact it's the first time I hear about this, very much doubt many will upvote your issue but it's always good to suggest it

curious do you have a use case for this?

The primary use case is verifying Appwrite-issued JWTs in external services without coupling them to the Appwrite backend.

https://docs.cdp.coinbase.com/embedded-wallets/custom-authentication

• We are integrating Coinbase Embedded Wallets (custom authentication), which expects a standard OIDC-compatible flow.
• Downstream services (edge functions, workers, third-party APIs) need to validate JWTs using public keys via JWKS, rather than calling back to Appwrite on every request.
• A .well-known/openid-configuration + jwks.json endpoint would allow:
  • Stateless JWT verification
  • Better performance and lower latency
  • Standard interoperability with OIDC/JWT tooling
  • Easier multi-service and zero-trust architectures

In short, this is about standards compliance and decoupling auth from service-to-service communication, especially when integrating with modern wallet, identity, and edge-based systems.

Why does this sound AI generated.

We all do that nowadays

Too lazy to write

Well in that case don't answer people's questions. I don't wanna see copy pasted AI answers here.

@Kenny I know I shouldn't but I had to I saw your reaction 🥸

🤦‍♂️😅too lazy to type into a sentence

Is this possible, or on the roadmap?

We’re considering migrating from Firebase to Appwrite. In Firebase, we rely on JWKS/OIDC to verify JWTs across services without backend calls.

then don't answer. Simple.

and as already said, it's not on the roadmap to my knowledge, check if there is an issue. If there isn't, chances are low.

But @Tessa hopefully can answer this better.

nothing ive clearly heard of from our team.

Like Mr. Afonso mentioned already, check if there is an existing issue, if not, create it as a discussion or feature request. We could prioritize things based on upvotes if it wasn't on the roadmap