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] Suggest DEBUG level logging instead for SAML (#74661) #75878

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 11 additions & 8 deletions x-pack/docs/en/security/troubleshooting.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -682,29 +682,32 @@ the `basic` `authProvider` in {kib}. The process is documented in the

*Logging:*

Very detailed trace logging can be enabled specifically for the SAML realm by
setting the following transient setting:
If the previous resolutions do not solve your issue, enable additional
logging for the SAML realm to troubleshoot further. You can enable debug
logging by configuring the following transient setting:

[source, shell]
-----------------------------------------------
[source, console]
----
PUT /_cluster/settings
{
"transient": {
"logger.org.elasticsearch.xpack.security.authc.saml": "trace"
"logger.org.elasticsearch.xpack.security.authc.saml": "debug"
}
}
-----------------------------------------------

----

Alternatively, you can add the following lines to the end of the
`log4j2.properties` configuration file in the `ES_PATH_CONF`:

[source,properties]
----------------
logger.saml.name = org.elasticsearch.xpack.security.authc.saml
logger.saml.level = TRACE
logger.saml.level = DEBUG
----------------

Refer to <<configuring-logging-levels,configuring logging levels>> for more
information.

[[trb-security-internalserver]]
=== Internal Server Error in Kibana

Expand Down