Skip to content
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

[7.x] Handle RelayState in preparing a SAMLAuthN Request (#46534) #47092

Merged
merged 1 commit into from
Sep 25, 2019

Conversation

jkakavas
Copy link
Member

Backports the following commits to 7.x:

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.
@jkakavas jkakavas added backport :Security/Authorization Roles, Privileges, DLS/FLS, RBAC/ABAC labels Sep 25, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-security

@jkakavas jkakavas added :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) and removed :Security/Authorization Roles, Privileges, DLS/FLS, RBAC/ABAC labels Sep 25, 2019
@jkakavas jkakavas merged commit 23bceaa into elastic:7.x Sep 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants