Configure browser redirects per custom domain
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 96
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Preflight checklist
- I could not find a solution in the existing issues, docs, nor discussions.
- I agree to follow this project's Code of Conduct.
- I have read and am following this repository's Contribution Guidelines.
- I have joined the Ory Community Slack.
- I am signed up to the Ory Security Patch Newsletter.
Ory Network Project
dazzling-chandrasekhar-msru5m4b1c
Describe your problem
On the Account Experience > Browser redirects page, you can configure the redirect settings for your Ory project.
There are no issues if you use the default project URL or only have a single custom domain.
But if you have multiple custom domains, then configuring the redirects may be problematic.
Path values are limited since, if the redirect value is a path instead of a full URL, the path is relative to the project URL and not the Custom UI base URL. Since you can't host pages under the project URL (even with a custom domain), you'll likely need to set the redirect value using a full URL. But if you have multiple custom domains, then the full URL may not work with all of the custom domains.
Describe your ideal solution
Similar to the Account Experience > UI URLs page where you set the Custom UI Base URL and flow UI values separately for each custom domain, you should be able to set the redirects separately for each custom domain. Or at least be able to set a custom base URL for each custom domain, and then path redirect values should be relative to the base URL.
Workarounds or alternatives
Right now I am setting a return_to value in my code when there isn't already one specified, which can be dynamic based on where the code is running
Version
Ory Network
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Account Experience > Browser redirects and UI URLs pages described in the issue, and compare how settings are represented for multiple custom domains. Review the existing return_to workaround and determine the intended per-domain redirect behavior. Done should mean redirect settings can be configured consistently for each custom domain.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100