Hello, team! :wave: I'm a newbie to Ory's ecosyst...
# talk-hydra
b
Hello, team! 👋 I'm a newbie to Ory's ecosystem. I'm investigating Ory Hydra as the Authentication provider to our SaaS solution. Ory team has provided a good documentation. Thank you for that 🙏 I have 2 question about Hydra that I don't see them in the doc yet: 1. Does it support Multi-Tenant architecture? 2. How do we scale it? For example, if we have a huge of requests from "clients" to authenticate or validate access token?
b
Just my 2 cents 1. If by
multi-tenant
you mean,
multi-organization
, I think you can assign one OAuth client as one tenant... 2. If you are going to self-host it, k8s is a good option (and services like GKE, Amazon EKS auto-scales it for you) and there are helm charts already available officially.
b
Hi @bulky-architect-22083 1. By
multi-tenant
I mean all of organizations will use the same System instances 2. Great! Thanks!
f
@blue-engineer-76235 the 1st is an interesting question. How would you identify which end-point is invoked for which part of the organisation!
b
Hi @fancy-smartphone-2075 They are end-points that Client apps and resource servers use to authenticate (PKCE), verify access token, get userinfo, etc
b
I dont understand what you mean by
All organizations will use the same system instances
Hmmm perhaps you can use the
audience
field in the OAuth Client that you create and specify the list of endpoints that a particular organization is allowed to access. Then on the API side, when you receive the access_token, you introspect the token and get the list of endpoints from the audience field and check if the Client is allowed to access the endpoint.
👍 1