-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Handle RelayState in preparing a SAMLAuthN Request #46534
Conversation
This change allows for the caller of the `saml/prepare` API to pass a `relay_state` parameter that will then be part of the redirect URL in the response as the `RelayState` query parameter. The SAML IdP is required to reflect back the value of that relay state when sending a SAML Response. The caller of the APIs can then, when receiving the SAML Response, read and consume the value as it see fit.
Pinging @elastic/es-security |
At first glance this looks fine, but let's wait and see how Kibana wants to deal with the length limit on |
I agree to wait for Kibana but I think the possibility for the caller of the API to set the relaystate we send with the authentication request is useful to have ( Since we do already handle the possibility of a relay state parameter internally ) even if kibana doesn't use this now for passing the target url |
@elasticmachine update branch |
@@ -67,5 +83,8 @@ public void writeTo(StreamOutput out) throws IOException { | |||
super.writeTo(out); | |||
out.writeOptionalString(realmName); | |||
out.writeOptionalString(assertionConsumerServiceURL); | |||
if (out.getVersion().onOrAfter(Version.V_7_5_0)){ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if (out.getVersion().onOrAfter(Version.V_7_5_0)){ | |
if (out.getVersion().onOrAfter(Version.V_7_5_0)) { |
1b7a519
to
7390dcb
Compare
This change allows for the caller of the `saml/prepare` API to pass a `relay_state` parameter that will then be part of the redirect URL in the response as the `RelayState` query parameter. The SAML IdP is required to reflect back the value of that relay state when sending a SAML Response. The caller of the APIs can then, when receiving the SAML Response, read and consume the value as it see fit.
This change allows for the caller of the `saml/prepare` API to pass a `relay_state` parameter that will then be part of the redirect URL in the response as the `RelayState` query parameter. The SAML IdP is required to reflect back the value of that relay state when sending a SAML Response. The caller of the APIs can then, when receiving the SAML Response, read and consume the value as it see fit.
Re-enable BWC tests now that elastic#46534 has been backported to 7.x
Re-enable BWC tests now that elastic#46534 has been backported to 7.x
Re-enable BWC tests now that #46534 has been backported to 7.x
Re-enable BWC tests now that #46534 has been backported to 7.x
Support for RelayState was introduced in elastic#46534 but the docs were not updated at the time.
Support for RelayState was introduced in #46534 but the docs were not updated at the time.
Support for RelayState was introduced in elastic#46534 but the docs were not updated at the time.
This change allows for the caller of the
saml/prepare
API to passa
relay_state
parameter that will then be part of the redirectURL in the response as the
RelayState
query parameter.The SAML IdP is required to reflect back the value of that relay
state when sending a SAML Response. The caller of the APIs can
then, when receiving the SAML Response, read and consume the value
as it see fit.
Resolves: #46232