Is the managed UI recommended for production use? ...
# ory-network
r
Is the managed UI recommended for production use? Any things to be aware of besides limited customization (colour, logo etc.)?
p
Hi @rhythmic-musician-58953 yes it is production ready. We are adding customization to the Ory Account Experience in the coming weeks so you can style it to your brand.
👍 1
r
Is “ui/welcome” route supposed to be accessible to everyone? Is there a way to disable it, since it should be for devs only?
p
It is currently not possible to completely disable it, however when integrating with Ory through the Account Experience you can set redirect urls to your own application and so it won't show the
ui/welcome page
r
Thanks @proud-plumber-24205 🙇
After the user verifies an email there's a form rendered to submit the email again. If you submit it again it says it's already verified. Is there any reason to render this email form even after successful verification?
Also, OTP account recovery flow renders two submit buttons
f
thanks for pointing these out, we're aware and fixing them!
r
Hi, @fast-lunch-54279, is there an update on this issue in Ory Elements?
After the user verifies an email there's a form rendered to submit the email again. If you submit it again it says it's already verified.
f
@proud-plumber-24205 can you give an update here please?
p
Hi @rhythmic-musician-58953 The first problem you mentioned should be resolved (account recovery renders two submit buttons). The second problem isn't a problem with the account experience. The account experience is rendering the form again since Ory is taking you back to the /verification route by default. You can set where the user should end up after a successful verification by adding a post-verification redirect URL e.g. your application url. This can be found inside the console -> Browser Redirects -> Post-Verification Redirect
r
Thanks for the response. Yes, I'm aware of the post-verification redirect, but that's not an option for us since we'll be using many different applications with the same self-service app. The redirects need to be set dynamically for each, with params such as
after_verification_return_to
, and, in some cases, we've not found a way to set that (e.g. this case). We've built a workaround in the custom self-service UI by rendering a new
Card
on successful verification, rather than using the
UserAuthCard
component.
Let me know if I'm missing some concepts here that would allow to solve this differently 🙂
p
For all the Ory Flows you should be able to set the
return_to
query parameter which redirects the user back to the page you want them to be on when initializing the flow. If I remember correctly you need to add the URL to the redirect "allow" list