cuddly-plastic-72839
08/07/2023, 11:16 AMproud-plumber-24205
08/07/2023, 12:54 PMcuddly-plastic-72839
08/07/2023, 1:00 PMreturn_to
query parameter wrong. How to specify, where to return to, after social login (e.g. via Google) has succeeded?
1. Create Registration Flow for Native Apps
2. Update Registration Flow with return_to
3. Open a browser with the provided URL for signing in via social login provider
4. After successful authentication with the social login provider call back to return_to
cuddly-plastic-72839
08/07/2023, 1:02 PMproud-plumber-24205
08/07/2023, 1:07 PMproud-plumber-24205
08/07/2023, 1:08 PMcuddly-plastic-72839
08/07/2023, 1:27 PMreturn_to
is also mentioned. I don't know how the normal callback URL would work?
Besides the native app, we also have a self service browser client, which needs to work along. If I configure the "normal" return urls to the native app, the browser UI will stop working.proud-plumber-24205
08/07/2023, 1:56 PMproud-plumber-24205
08/07/2023, 1:58 PMcuddly-plastic-72839
08/07/2023, 2:02 PMcuddly-plastic-72839
08/07/2023, 2:08 PMcuddly-plastic-72839
08/07/2023, 2:10 PMRelated to this: How to configure where to return to in case of an error?Should I open a bug report in Kratos for this?
return_to
doesn't work in the case an error happens, for example when already an account exists with the unique identifier.proud-plumber-24205
08/07/2023, 2:12 PMcuddly-plastic-72839
08/07/2023, 2:14 PMcuddly-plastic-72839
08/07/2023, 2:38 PMproud-plumber-24205
08/07/2023, 3:06 PM