# SAML AD ADFS yaml settings troubleshooting and role mapping notes and insight part II (Solved) **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-security\ **Created:** [February 25, 2019, 3:12pm UTC](https://discuss.elastic.co/t/saml-ad-adfs-yaml-settings-troubleshooting-and-role-mapping-notes-and-insight-part-ii-solved/169860 "2019-02-25T15:12:54Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\ **Post date:** [February 25, 2019, 4:12pm UTC](https://discuss.elastic.co/t/saml-ad-adfs-yaml-settings-troubleshooting-and-role-mapping-notes-and-insight-part-ii-solved/169860/2 "2019-02-25T16:12:38Z")
> [@Ryan\_Downey](#): > > ES can still use SAML 1.1, officially ES only supports SAML 2.0 but we didn't test if this field was needed or not. This actually not true, see my relevant comment in [SAML AD ADFS yaml settings, troubleshooting and role mapping notes and insight (Solved) - #2 by ikakavas](https://discuss.elastic.co/t/saml-ad-adfs-yaml-settings-troubleshooting-and-role-mapping-notes-and-insight-solved/169859/2) > [@Ryan\_Downey](#): > > Kibana logs may not be of much use since the actual authentication is done by ES. Most errors are returned from Elasticsearch to Kibana as Exceptions so if one has only access to kibana logs, setting `logging.verbose: true` in kibana.yml will make sure that enough information will be printed there to start the troubleshooting. But in general, you are correct, ES logs are much more useful as the core of the SAML implementation is in Elasticsearch --- _[View the full topic](https://discuss.elastic.co/t/saml-ad-adfs-yaml-settings-troubleshooting-and-role-mapping-notes-and-insight-part-ii-solved/169860)._