Disable Account Experience UI pages when Custom UI is set up

[BrandonNoad]

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

https://account-flows-test.bonfirehub.com

Describe your problem

If you have a custom UI and custom domain set up and have the "Enable the Account Experience welcome page" option disabled, the default Account Experience UI pages are still accessible if the user navigates to them directly with a valid flow id.

For example, go to https://account-test.bonfirehub.com/login. Copy the flow id from the url. Then visit https://account-flows-test.bonfirehub.com/ui/login?flow={FLOW_ID_YOU_COPIED}

The default Account Experience login page is still accessible by the user.

Describe your ideal solution

These Account Experience pages should not be accessible by the user

Workarounds or alternatives

🤷

Version

Ory Network

Additional Context

No response

[aeneasr]

So you basically want to disable the full managed account experience, not just the welcome page, correct?

[BrandonNoad]

Correct. Or maybe a toggle for each page so you fallback to the Account Experience for pages you haven't customized yet.

[github-actions]

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

• open a PR referencing and resolving the issue;
• leave a comment on it and discuss ideas on how you could contribute towards resolving it;
• leave a comment and describe in detail why this issue is critical for your use case;
• open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️