Update SAML Troubleshooting documentation to include /api/security/v1/me API

[hemantmalik]

Description: Update the https://www.elastic.co/guide/en/elasticsearch/reference/current/trb-security-saml.html to include /api/security/v1/me

Use-case: Helps with troubleshooting Auth issues with SAML setup

[elasticmachine]

Pinging @elastic/kibana-security (Team:Security)

[azasypkin]

Description: Update the https://www.elastic.co/guide/en/elasticsearch/reference/current/trb-security-saml.html to include /api/security/v1/me

@hemantmalik thanks for filing this, but what exactly you'd like us to mention in the docs regarding Kibana's /api/security/v1/me (it's /internal/security/me now by the way)?

[hemantmalik]

Hi @azasypkin leveraging this API in troubleshooting a SAML issue proved critical to get to the root of the authorization issue in integrating with the SAML provider.

[mbrunnert]

Hi @azasypkin , I second this as well. When user authentication is setup with SAML and you are troubleshooting a user with no access to Kibana, the Elasticsearch GET /_security/_authenticate is not available. In this scenario Kibana /api/security/v1/me is the only way to tell what SAML groups and Elasticsearch roles a user does and does not have.

[azasypkin]

Closing this one in favor of a more generic Kibana authentication troubleshooting guide issue where this ask is recorded as well.