Skip to content

Adjust troubleshooting guide for SAML #437

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

Merged
merged 3 commits into from
Jul 24, 2019

Conversation

jkakavas
Copy link
Member

Since 7.3, it's possible to explicitly configure the SAML realm to
be used in Kibana's configuration. This in turn, eliminates the need
of properly setting xpack.security.public.* settings in Kibana
and largely simplifies relevant documentation.

This change adjusts our troubleshooting guide to reflect this change

Relates: elastic/elasticsearch#44705

Since 7.3, it's possible to explicitly configure the SAML realm to
be used in Kibana's configuration. This in turn, eliminates the need
of properly setting xpack.security.public.* settings in Kibana
and largely simplifies relevant documentation.

This change adjusts our troubleshooting guide to reflect this change
Copy link
Contributor

@lcawl lcawl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM and builds successfully

@jkakavas jkakavas merged commit e2e217d into elastic:master Jul 24, 2019
jkakavas added a commit that referenced this pull request Jul 24, 2019
Since 7.3, it's possible to explicitly configure the SAML realm to
be used in Kibana's configuration. This in turn, eliminates the need
of properly setting xpack.security.public.* settings in Kibana
and largely simplifies relevant documentation.

This change adjusts our troubleshooting guide to reflect this change
jkakavas added a commit that referenced this pull request Jul 24, 2019
Since 7.3, it's possible to explicitly configure the SAML realm to
be used in Kibana's configuration. This in turn, eliminates the need
of properly setting xpack.security.public.* settings in Kibana
and largely simplifies relevant documentation.

This change adjusts our troubleshooting guide to reflect this change
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants