ZenonE.88109 (Customer) asked a question.
Hi,
I am trying to leverage the redirect URI wildcard functionality. I see that it's possible to put the "*" in a subdomain, like "https://*.foo.com/bar/baz", but I'd like to put it in the path, like "https://baz.foo.com/bar/*".
The reason: I am working on a multi-tenant system and the operative value in my redirect path is an instance id of a tenant.
However, if I put the wildcard in the path, it does not appear to be recognized, and I receive a 400 Bad Request error that states: "Your request resulted in an error. The 'redirect_uri' parameter but be a Login redirect URI in the client app settings:'.
(I attempted to post this as a question, but it wouldn't let me, so I'm opening a case. Sorry if this not the right process for such a simple question).
Hi @ZenonE.88109 (Customer),
Thank you for posting on the Okta community page!
I have done some research on my end, and based on my findings it seems that what you are trying to achieve might not be possible because the redirect URIs need to be absolute.
Additionally, the redirect URI wildcards have been designed for subdomains, as I manage to find in the bellow documentation:
I hope the above information is helpful!
If you can handle wildcards in a subdomain, why can't you handle wildcards in the path. I could also really use this feature
Please upvote this request here
Upvoted, thanks Rafael.
Hi everyone. This is a minor change, but can reduce lot of work. If you want this too, Please upvote this request here we already have ~50 upvotes