Hi, looking into Hydra, and I see that consent, lo...
# talk-hydra
s
Hi, looking into Hydra, and I see that consent, login and logout urls have to be provided in configuration. Working on an application with whitelabeling, is there a way to support multiple hostnames? This is actually also the case for
urls.self.issuer
1
m
The proper way of doing this would be to have one authZ server/domain and one login server/domain. The other websites would then simply call that one server instead of esch on their own domain, which is what OAuth is for. If you want true multi-tenancy (individual oauth2 clients per domain, …) you need multiple deployments.
Another option is to have a redirect in your login app to the login app of the domain. You control it, you can program whatever you want.
You can also wait for the Ory Hydra APIs to be available in Ory Cloud, which is multi-tenant out of the box (earlyQ2)
s
Cool, that would be very interesting. Is there a github issue or something else where I can follow the progress?
m
You can subscribe to our newsletter and watch the roadmap (update should be coming momentarily). We will be very vocal about the Ory Hydra APIs making it to Ory Cloud 😉.
s
Great! Thank you Vincent
👍 1
m
Or you can just sign up https://console.ory.sh/ and then you are also on the mailing list
Also check out the community projects and articles, maybe there is something related to your usecase: https://www.ory.sh/docs/ecosystem/community
👍 1
I will stop spamming you now 😆