I have an app using SSO and we have SSO being forced . So the default login page is "index.html" with redirects the user to /SSO/ using the tag "<meta http-equiv="refresh" content="0;URL=/SSO/" />". We want users to be routed to different home pages based on the URL path. So myapp.com routes to the normally to the home microflows I have set up. Each role has a role-based microflow as the home page. In these microflows I changed the URL properties to "test1", "test2", etc and set some logic to redirect the user to a different page if the application URL contains the string "test". Ideally when a user navigates to "myapp.com/p/test", SSO would redirect the user to the IDP and redirect back and the home microflow would detect the URL contains "test" and change the home page. However when SSO redirects back, it completely cuts off the /p/whatever. t's just coming back as "myapp.com". Is there a way, when SSO redirecting/authenticating, to retain the path used to get to the app (myapp.com/p/test1, myapp.com/p/test2, etc)?
asked
Brian Lorraine
1 answers
0
You 'll better not redirect default to SSO (with use of anonymous pagelinks). Create a page where you can login with SSO (with a button)
Use as default home page for anonymous users.
This is also better for the logout page, otherwise the user will be redirected direct after logout.