Your approach is assuming I built my own login component. I want to use the login UI generated by FusionAuth, when the user clicks on the login button that is a component inside the fusionauth react-sdk. I want to completely remove this initial workflow, so when the user launches the application the root route with redirect the user to /oauth2/authorize endpoint.

I need help, I am just trying to load the FusionAuth login screen without showing the landing page with the login button first. I am not sure how to automate the event that redirects and loads the FusionAuth login page in my react application.

@vinicius-campitelli The issue is with the our backend setting the final cookies, app.at, app.idt, app.at_exp in one domain after authentication, then having the application redirect back to localhost and retain the cookies. In other words I am trying to authenticate as a user and develop on localhost, however after authentication the cookies are no longer accessible when I redirect back to localhost.

I am developing a SPA with react. I am having an issue while developing locally, i.e. on my localhost, the app is talking to FusionAuth and a service that is performing PKCE which are running remotely. I am having issues with the cookies being set. The cookies that are returned from the backend have a domain which is not localhost so they are dropped after the authentication and redirect.

How do I develop locally with this set-up, redirect back to localhost after authentication and retain the cookies?