We're starting to use Vercel for hosting a number of our Frontend products. When using Vercel's development flows, they create a deployment based on your branch and generate a unique URL for that branch. Since the URLS are unique for each deployment, I'm trying to understand how we can still use Hydra Clients and

redirect_uris

when we don't know the URL in advance, and since wildcards or similar or discouraged on the OAuth2.0 spec (although I'm not sure Hydra supports them either) I'm not sure how to get around this. Has anyone else encountered similar, and how did you overcome this?

Hey Adam 👋 We are facing a similar issue, and will probably try to hook ourselves into the creation of a new environment. It will call some logic that'll interact with Hydra admin API patch Oauth2 client to add the new URLs to the

redirect_uris

of the given client. We haven't implemented it yet, but that's our current idea.

We ended up changing how our frontend services use auth, unrelated to this problem, but it had the added benefit that it solved this for us