-
Notifications
You must be signed in to change notification settings - Fork 420
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use deep linking #359
Comments
Hello, If you take a look at TrackRequest in request_tracker_cookie.go it stores the original request URL in the tracked request.
After the auth flow completes the middleware (middleware.go) loads the trackedRequest in CreateSessionFromAssertion and redirects to the original URL.
This means that the relayState does not contain the URL but rather a key that allows the SP to lookup the initial request URL. If you want to redirect somewhere else you could modify the code to either store a different url or redirect to something else after the auth flow completes. |
HI All!
According to SAML documentation usually
RelayState
is used to allow IdPs to redirect to an specific URL after the whole SAML roundtrip has been completed. However, withcrewjam/saml
implementation I have not been able to get this right as seems thatRelayState
is usually a random generated value (This following the example in the Readme.md)Can please someone point me on how to achieve deep linking using this library? I suspect, instead of using the Middleware I'll need to implement the whole authentication flow using methods like
MakeRedirectAuthenticationRequest
Is this correct?If so, what should I do after the first redirection?
Thank you
The text was updated successfully, but these errors were encountered: