brash-hydrogen-25966
05/15/2025, 2:53 PM<https://auth.identity.abc.com>
and https://*.<http://abc.com|abc.com>
.
Our custom UI is hosted at <https://identity.abc.com>
(e.g., <https://identity.abc.com/login>
, <https://identity.abc.com/recovery>
, etc.), and we've set the necessary custom UI paths in our Ory project configuration. We have also ensured that "Enable the account experience welcome page" is turned OFF.
We're observing that direct navigation to paths on our Ory custom domain like <https://auth.identity.abc.com/login>
, <https://auth.identity.abc.com/recovery>
, etc., results in a 404 error:
{
"error": {
"code": "404",
"details": {
"ruleId": "6176b3cb"
},
"message": "Invalid path",
"reason": "No resource found using the specified path.",
"status": "Not Found"
}
}
Interestingly, users with a valid session can access <https://auth.identity.abc.com/settings>
and see the default Ory account experience settings page. Our goal is to have all user-facing identity pages served exclusively from our custom UI domain (<https://identity.abc.com>
).
Could you please advise on how can we completely disable access to the Ory-hosted /settings
page at <https://auth.identity.abc.com/settings>
, ensuring users are always directed to our custom UI for account management? Have we potentially missed a configuration setting to achieve this behavior?
Thanks for your help!bland-eye-99092
05/15/2025, 2:58 PMbrash-hydrogen-25966
05/15/2025, 2:59 PM<https://identity.abc.com/settings>
, following the same patternbland-eye-99092
05/15/2025, 2:59 PMbrash-hydrogen-25966
05/15/2025, 3:01 PMbland-eye-99092
05/15/2025, 3:21 PMbrash-hydrogen-25966
05/15/2025, 3:34 PM