Hi, any chance this PR will be merged into a Keycloak release soon?
Allowing the (optional) use of wildcard redirect urls on a controlled subdomain would vastly reduce administrative overhead for dynamic environment creation.
thanks,
David

Closing. It's clear that this is not going to happen (at least not with this PR), and it's so stale at this point, might as well re-write it.

@josh-cain Could you link the new PR here if you create one, so I can watch it?

@sharedprophet - my apologies, I can see where that comment was not clear. I have no intentions of re-writing this myself at this point. Per @stianst 's comment, they're not going to take anything with mocks, so a re-write will entail one of:

1. refactoring to decouple the data domain from a utility function as simple as wildcard validation, as you must have a correctly populated RealmModel to test the exposed verifyRedirectUri function.
2. manipulating the accessibility of the private matchesRedirects (commonly done with something like PowerMock, which I suppose would once again be taboo).
3. writing massive integration tests involving an application server to test its ability to properly parse a url string since mocks cannot be used.

Pretty sure #1 or #2 above would get rejected, and I don't have the time/patience for #3. Sorry to abandon it, hopefully the community can band together for this one soon!