Back button in Hosted UI does not go to the main application but always `/ui/welcome`

[aeneasr]

Discussed in https://github.com/ory/cloud/discussions/100

^{Originally posted by adrianrudnik June 12, 2022} I have set all available fields for the post-settings redirections, but I'm still unable to get back to my app if I hit the "back"-button at the bottom of the default settings UI. It always redirects back to /ui/welcome. Is there anything special I need to set, or is this a bug?

[aeneasr]

Thank you for the report, we have to fix that!

[Benehiko]

We recently removed the footer which contained the "back" button. I think some pages should still include some way for the user to navigate back to the main app.

e.g. example.com -> settings page (redirects to Ory Network) -> user is now stuck on Ory Network page with the only option to use the browser back button.

We currently only have the back button implemented on error pages. Here is an example: https://playground.projects.oryapis.com/ui/error?id=stub:500

I believe this should help with navigating the user back to the original page from where the user was redirected from. https://github.com/ory/kratos-selfservice-ui-node/blob/master/src/routes/error.ts#L33

We should still add some way to navigate the user back from the Login, Registration, Verification, Recovery, Settings page.

[github-actions[bot]]

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 🙏✌️