hundreds-telephone-89736
06/10/2024, 9:57 AM{
"error": {
"id": "browser_location_change_required",
"code": 422,
"status": "Unprocessable Entity",
"reason": "In order to complete this flow please redirect the browser to: <https://auth.our-domain.co.uk/auth/settings?flow=f601c736-fd5e-4d89-ac92-1ea8e4f694df>",
"message": "browser location change required"
},
"redirect_browser_to": "<https://auth.our-domain.co.uk/auth/settings?flow=f601c736-fd5e-4d89-ac92-1ea8e4f694df>"
}
I understand that we are supposed to parse the error and redirect the user according to the redirect_browser_to
field of the response.
However, the response is pointing to the Ory API URL instead of the custom UI URL, so that the browser fails to displays the page and shows 404.
If we manually modify it to https://enterprise.our-domain.co.uk/auth/settings?flow=f601c736-fd5e-4d89-ac92-1ea8e4f694df, it does work.
We reckon this is probably an Ory configuration mistake on our part. Would love to hear your insights on this.brainy-jewelry-16322
06/10/2024, 2:22 PMbrainy-jewelry-16322
06/10/2024, 2:23 PMhundreds-telephone-89736
06/10/2024, 2:39 PMcontinue_with
(but not the full link). So technically we can make it work by crafting the URL manually in the application.
However in the description it says it is intended for "recovery flows on mobile applications". So I'm not centain if it is appropriate to use in our scenario, which is a browser environment.
To sum up, we have two questions for the Ory engineers.
1. Is it by design that we go through the 422 error when completing a browser recovery flow?
2. If so, how can we modify the redirect_browser_to
URL in the 422 error response?