4znur (4znur) asked a question.
I have a Blazor web application that I use Okta for. Let's say our app is accessible through a custom domain https://abc.com. It is deployed in a server which has the address https://xyz.somecloudserver.com. So , in Okta settings, in sign-in redirect uri we have added both
https://abc.com/authorization-code/callback
https://xyz.somecloudserver.com/authorization-code/callback
When I access the app through custom domain (https://abc.com) and click on login button, it takes me to the Okta login page. In the address bar I see that in query string the redirect_uri is set to https://xyz.somecloudserver.com/authorization-code/callback and not https://abc.com/authorization-code/callback. This means that once the user is authenticated they're taken to https://xyz.somecloudserver.com and not https://abc.com
When I am accessing the app through https://abc.com/ why is the redirect_uri being set to https://xyz.somecloudserver.com/authorization-code/callback?
Hello @4znur (4znur) Thank you for reacting out to our Community!
Please see below documentations for Blazor app and how to setup authentication and redirect for it to direct your users to the desired page:
https://developer.okta.com/code/dotnet/blazor/#get-started-with-blazor-okta
https://github.com/okta/samples-blazor
Please see also this video on the implementation for additional details:
https://www.youtube.com/watch?v=MvKK0UlgxGI
Additionally if you need further assistance we recommend to leverage the Okta Developer forums for this type of questions and take advantage of their expertise.
https://devforum.okta.com/
Community members help others by clicking Like or Select as Best on responses. Try it today.
What you missed: new product releases and other announcements