# SAML for kibana Single Sign-on using Okta

**URL:** <https://forum.search-guard.com/t/saml-for-kibana-single-sign-on-using-okta/1238>\
**Category:** Search Guard\
**Created:** [December 5, 2018, 1:33pm UTC](https://forum.search-guard.com/t/saml-for-kibana-single-sign-on-using-okta/1238 "2018-12-05T13:33:02Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Venkata\_Naresh\_Divi](https://avatars.discourse-cdn.com/v4/letter/v/c5a1d2/32.png) [@Venkata\_Naresh\_Divi](https://forum.search-guard.com/u/Venkata_Naresh_Divi)\
**Post date:** [December 5, 2018, 1:33pm UTC](https://forum.search-guard.com/t/saml-for-kibana-single-sign-on-using-okta/1238/1 "2018-12-05T13:33:02Z")

</div>

When asking questions, please provide the following information:

- Search Guard and Elasticsearch version

6.4.3

- Installed and used enterprise modules, if any

- JVM version and operating system version

JAVA 10.0.2, Ubuntu 18.04

- Search Guard configuration files

authc:

basic\_internal\_auth\_domain:

enabled: true

order: 0

http\_authenticator:

type: basic

challenge: false

authentication\_backend:

type: intern

saml\_auth\_domain\_okta:

http\_enabled: true

transport\_enabled: true

order: 1

http\_authenticator:

type: ‘saml’

challenge: true

config:

idp:

metadata\_file: /home/ubuntu/ELK\_6\_4\_Stack/elasticsearch-6.4.3/config/okta.xml

entity\_id: [http://www.okta.com/](http://www.okta.com/)\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

sp:

entity\_id: kibana-saml-demo

kibana\_url: [https://kibana](https://kibana).\*\*\*\*.info:5601/

roles\_key: Role

exchange\_key: ‘eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9’

authentication\_backend:

type: noop

- Elasticsearch log messages on debug level

- Other installed Elasticsearch or Kibana plugins, if any

I have configured Single Sign on using Okta for Kibana using search gaurd community edition. After all the set up, Elastic search is running but with Kibana Im getting customerror?type=samlConfigError#?\_g=() with SAML configuration error Something went wrong while retrieving the SAML configuration, please check your settings. Please help me with this

---

<div class="post-metadata">

**Author:** ![jkressin](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/jkressin/32/9_2.png) [@jkressin](https://forum.search-guard.com/u/jkressin)\
**Post date:** [December 5, 2018, 2:11pm UTC](https://forum.search-guard.com/t/saml-for-kibana-single-sign-on-using-okta/1238/2 "2018-12-05T14:11:16Z")

</div>

SAML is an Enterprise feature, not a Community feature. If you have disabled the Enterprise features in elasticsearch.yml, then this error is expected.

> **···**
>
> On Wednesday, December 5, 2018 at 2:33:02 PM UTC+1, Venkata Naresh Divi wrote:
> 
> > When asking questions, please provide the following information:
> 
> > - Search Guard and Elasticsearch version
> 
> > 6.4.3
> 
> > - Installed and used enterprise modules, if any
> 
> > - JVM version and operating system version
> 
> > JAVA 10.0.2, Ubuntu 18.04
> 
> > 
> 
> > - Search Guard configuration files
> 
> > authc:
> 
> > basic\_internal\_auth\_domain:
> 
> > enabled: true
> 
> > order: 0
> 
> > http\_authenticator:
> 
> > type: basic
> 
> > challenge: false
> 
> > authentication\_backend:
> 
> > type: intern
> 
> > saml\_auth\_domain\_okta:
> 
> > http\_enabled: true
> 
> > transport\_enabled: true
> 
> > order: 1
> 
> > http\_authenticator:
> 
> > type: ‘saml’
> 
> > challenge: true
> 
> > config:
> 
> > idp:
> 
> > metadata\_file: /home/ubuntu/ELK\_6\_4\_Stack/elasticsearch-6.4.3/config/okta.xml
> 
> > entity\_id: [http://www.okta.com/\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*](http://www.okta.com/ *************** )
> 
> > sp:
> 
> > entity\_id: kibana-saml-demo
> 
> > kibana\_url: [https://kibana.](https://kibana.)\*\*\*\*.info:5601/
> 
> > roles\_key: Role
> 
> > exchange\_key: ‘eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9’
> 
> > authentication\_backend:
> 
> > type: noop
> 
> > 
> 
> > - Elasticsearch log messages on debug level
> 
> > - Other installed Elasticsearch or Kibana plugins, if any
> 
> > 
> 
> > I have configured Single Sign on using Okta for Kibana using search gaurd community edition. After all the set up, Elastic search is running but with Kibana Im getting customerror?type=samlConfigError#?\_g=() with SAML configuration error Something went wrong while retrieving the SAML configuration, please check your settings. Please help me with this
> 
> > 
> 
> >

---

<div class="post-metadata">

**Author:** ![Venkata\_Naresh\_Divi](https://avatars.discourse-cdn.com/v4/letter/v/c5a1d2/32.png) [@Venkata\_Naresh\_Divi](https://forum.search-guard.com/u/Venkata_Naresh_Divi)\
**Post date:** [December 5, 2018, 2:15pm UTC](https://forum.search-guard.com/t/saml-for-kibana-single-sign-on-using-okta/1238/3 "2018-12-05T14:15:21Z")

</div>

I have enabled the enterprise feature in elasticsearch.yml. Find below is my elasticsearch.yml configuration

**searchguard.enterprise\_modules\_enabled: true** searchguard.ssl.transport.pemcert\_filepath: CN=emailnow.info.crtfull.pem  
searchguard.ssl.transport.pemkey\_filepath: CN=emailnow.info.key.pem  
searchguard.ssl.transport.pemkey\_password: $$$$$$$$$$$$$$$$$$  
searchguard.ssl.transport.pemtrustedcas\_filepath: chain-ca.pem  
searchguard.ssl.transport.enforce\_hostname\_verification: false

searchguard.ssl.http.enabled: true  
searchguard.compliance.history.internal\_config\_enabled: true  
searchguard.compliance.history.external\_config\_enabled: true  
searchguard.compliance.history.read.metadata\_only: true

searchguard.ssl.http.pemcert\_filepath: CN=emailnow.info.crtfull.pem  
searchguard.ssl.http.pemkey\_filepath: CN=emailnow.info.key.pem  
searchguard.ssl.http.pemkey\_password: $$$$$$$$$$$$$$$$$$$$$$  
searchguard.ssl.http.pemtrustedcas\_filepath: chain-ca.pem  
searchguard.allow\_unsafe\_democertificates: true  
searchguard.authcz.admin\_dn:

- CN=sgadmin

searchguard.audit.type: internal\_elasticsearch  
searchguard.enable\_snapshot\_restore\_privilege: true  
searchguard.check\_snapshot\_restore\_write\_privileges: true  
searchguard.restapi.roles\_enabled: [“sg\_all\_access”]  
cluster.routing.allocation.disk.threshold\_enabled: false  
cluster.name: searchguard\_demo  
network.host: 0.0.0.0  
discovery.zen.minimum\_master\_nodes: 1  
node.max\_local\_storage\_nodes: 3  
xpack.monitoring.enabled: true  
xpack.graph.enabled: false  
xpack.ml.enabled: false  
xpack.security.enabled: false  
xpack.watcher.enabled: false

``

> **···**
>
> On Wednesday, 5 December 2018 19:41:16 UTC+5:30, Jochen Kressin wrote:
> 
> > SAML is an Enterprise feature, not a Community feature. If you have disabled the Enterprise features in elasticsearch.yml, then this error is expected.
> > 
> > On Wednesday, December 5, 2018 at 2:33:02 PM UTC+1, Venkata Naresh Divi wrote:
> > 
> > > When asking questions, please provide the following information:
> 
> > > - Search Guard and Elasticsearch version
> 
> > > 6.4.3
> 
> > > - Installed and used enterprise modules, if any
> 
> > > - JVM version and operating system version
> 
> > > JAVA 10.0.2, Ubuntu 18.04
> 
> > >
> 
> > > - Search Guard configuration files
> 
> > > authc:
> 
> > > basic\_internal\_auth\_domain:
> 
> > > enabled: true
> 
> > > order: 0
> 
> > > http\_authenticator:
> 
> > > type: basic
> 
> > > challenge: false
> 
> > > authentication\_backend:
> 
> > > type: intern
> 
> > > saml\_auth\_domain\_okta:
> 
> > > http\_enabled: true
> 
> > > transport\_enabled: true
> 
> > > order: 1
> 
> > > http\_authenticator:
> 
> > > type: ‘saml’
> 
> > > challenge: true
> 
> > > config:
> 
> > > idp:
> 
> > > metadata\_file: /home/ubuntu/ELK\_6\_4\_Stack/elasticsearch-6.4.3/config/okta.xml
> 
> > > entity\_id: [http://www.okta.com/\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*](http://www.okta.com/ *************** )
> 
> > > sp:
> 
> > > entity\_id: kibana-saml-demo
> 
> > > kibana\_url: [https://kibana.](https://kibana.)\*\*\*\*.info:5601/
> 
> > > roles\_key: Role
> 
> > > exchange\_key: ‘eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9’
> 
> > > authentication\_backend:
> 
> > > type: noop
> 
> > >
> 
> > > - Elasticsearch log messages on debug level
> 
> > > - Other installed Elasticsearch or Kibana plugins, if any
> 
> > >
> 
> > > I have configured Single Sign on using Okta for Kibana using search gaurd community edition. After all the set up, Elastic search is running but with Kibana Im getting customerror?type=samlConfigError#?\_g=() with SAML configuration error Something went wrong while retrieving the SAML configuration, please check your settings. Please help me with this
> 
> > >
> 
> > >

---

<div class="post-metadata">

**Author:** ![jkressin](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/jkressin/32/9_2.png) [@jkressin](https://forum.search-guard.com/u/jkressin)\
**Post date:** [December 5, 2018, 3:48pm UTC](https://forum.search-guard.com/t/saml-for-kibana-single-sign-on-using-okta/1238/4 "2018-12-05T15:48:03Z")

</div>

Can you please post your Elasticsearch logfile on debug level when this error occurs? It should show the root cause of the error.

Setting log level to debug:

> **[Search Guard logging](https://docs.search-guard.com/latest/troubleshooting-setting-log-level)**
>
> Hot to set the Search Guard log level in a running Elasticsearch cluster for debugging.

> **···**
>
> On Wednesday, December 5, 2018 at 3:14:26 PM UTC+1, Venkata Naresh Divi wrote:
> 
> > I have enabled the enterprise feature in elasticsearch.yml. Find below is my elasticsearch.yml configuration
> 
> > **searchguard.enterprise\_modules\_enabled: true** searchguard.ssl.transport.pemcert\_filepath: CN=emailnow.info.crtfull.pem  
> > searchguard.ssl.transport.pemkey\_filepath: CN=emailnow.info.key.pem  
> > searchguard.ssl.transport.pemkey\_password: $$$$$$$$$$$$$$$$$$  
> > searchguard.ssl.transport.pemtrustedcas\_filepath: chain-ca.pem  
> > searchguard.ssl.transport.enforce\_hostname\_verification: false
> > 
> > searchguard.ssl.http.enabled: true  
> > searchguard.compliance.history.internal\_config\_enabled: true  
> > searchguard.compliance.history.external\_config\_enabled: true  
> > searchguard.compliance.history.read.metadata\_only: true
> > 
> > searchguard.ssl.http.pemcert\_filepath: CN=emailnow.info.crtfull.pem  
> > searchguard.ssl.http.pemkey\_filepath: CN=emailnow.info.key.pem  
> > searchguard.ssl.http.pemkey\_password: $$$$$$$$$$$$$$$$$$$$$$  
> > searchguard.ssl.http.pemtrustedcas\_filepath: chain-ca.pem  
> > searchguard.allow\_unsafe\_democertificates: true  
> > searchguard.authcz.admin\_dn:
> > 
> > - CN=sgadmin
> > 
> > searchguard.audit.type: internal\_elasticsearch  
> > searchguard.enable\_snapshot\_restore\_privilege: true  
> > searchguard.check\_snapshot\_restore\_write\_privileges: true  
> > searchguard.restapi.roles\_enabled: [“sg\_all\_access”]  
> > cluster.routing.allocation.disk.threshold\_enabled: false  
> > cluster.name: searchguard\_demo  
> > network.host: 0.0.0.0  
> > discovery.zen.minimum\_master\_nodes: 1  
> > node.max\_local\_storage\_nodes: 3  
> > xpack.monitoring.enabled: true  
> > xpack.graph.enabled: false  
> > xpack.ml.enabled: false  
> > xpack.security.enabled: false  
> > xpack.watcher.enabled: false
> 
> > ``
> 
> > 
> 
> > On Wednesday, 5 December 2018 19:41:16 UTC+5:30, Jochen Kressin wrote:
> > 
> > > SAML is an Enterprise feature, not a Community feature. If you have disabled the Enterprise features in elasticsearch.yml, then this error is expected.
> > > 
> > > On Wednesday, December 5, 2018 at 2:33:02 PM UTC+1, Venkata Naresh Divi wrote:
> > > 
> > > > When asking questions, please provide the following information:
> 
> > > > - Search Guard and Elasticsearch version
> 
> > > > 6.4.3
> 
> > > > - Installed and used enterprise modules, if any
> 
> > > > - JVM version and operating system version
> 
> > > > JAVA 10.0.2, Ubuntu 18.04
> 
> > > >
> 
> > > > - Search Guard configuration files
> 
> > > > authc:
> 
> > > > basic\_internal\_auth\_domain:
> 
> > > > enabled: true
> 
> > > > order: 0
> 
> > > > http\_authenticator:
> 
> > > > type: basic
> 
> > > > challenge: false
> 
> > > > authentication\_backend:
> 
> > > > type: intern
> 
> > > > saml\_auth\_domain\_okta:
> 
> > > > http\_enabled: true
> 
> > > > transport\_enabled: true
> 
> > > > order: 1
> 
> > > > http\_authenticator:
> 
> > > > type: ‘saml’
> 
> > > > challenge: true
> 
> > > > config:
> 
> > > > idp:
> 
> > > > metadata\_file: /home/ubuntu/ELK\_6\_4\_Stack/elasticsearch-6.4.3/config/okta.xml
> 
> > > > entity\_id: [http://www.okta.com/\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*](http://www.okta.com/ *************** )
> 
> > > > sp:
> 
> > > > entity\_id: kibana-saml-demo
> 
> > > > kibana\_url: [https://kibana.](https://kibana.)\*\*\*\*.info:5601/
> 
> > > > roles\_key: Role
> 
> > > > exchange\_key: ‘eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9’
> 
> > > > authentication\_backend:
> 
> > > > type: noop
> 
> > > >
> 
> > > > - Elasticsearch log messages on debug level
> 
> > > > - Other installed Elasticsearch or Kibana plugins, if any
> 
> > > >
> 
> > > > I have configured Single Sign on using Okta for Kibana using search gaurd community edition. After all the set up, Elastic search is running but with Kibana Im getting customerror?type=samlConfigError#?\_g=() with SAML configuration error Something went wrong while retrieving the SAML configuration, please check your settings. Please help me with this
> 
> > > >
> 
> > > >

---

<div class="post-metadata">

**Author:** ![Venkata\_Naresh\_Divi](https://avatars.discourse-cdn.com/v4/letter/v/c5a1d2/32.png) [@Venkata\_Naresh\_Divi](https://forum.search-guard.com/u/Venkata_Naresh_Divi)\
**Post date:** [December 10, 2018, 1:14pm UTC](https://forum.search-guard.com/t/saml-for-kibana-single-sign-on-using-okta/1238/5 "2018-12-10T13:14:35Z")

</div>

Getting the below error when request happens

{“type”:“response”,“@timestamp”:“2018-12-10T13:05:54Z”,“tags”:,“pid”:22031,“method”:“get”,“statusCode”:200,“req”:{“url”:“/ui/favicons/favicon-32x32.png”,“method”:“get”,“headers”:{“host”:“[kibana.emailnow.info:5601](http://kibana.emailnow.info:5601)”,“connection”:“keep-alive”,“pragma”:“no-cache”,“cache-control”:“no-cache”,“user-agent”:“Mozilla/5.0 (X11; Linux x86\_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36”,“dnt”:“1”,“accept”:“image/webp,image/apng,image/_,_/\*;q=0.8”,“referer”:“[https://kibana.emailnow.info:5601/customerror?type=samlConfigError",“accept-encoding”:"gzip](https://kibana.emailnow.info:5601/customerror?type=samlConfigError%22,%22accept-encoding%22:%22gzip), deflate, br”,“accept-language”:“en-GB,en-US;q=0.9,en;q=0.8”},“remoteAddress”:“202.153.46.98”,“userAgent”:“202.153.46.98”,“referer”:“[https://kibana.emailnow.info:5601/customerror?type=samlConfigError"},“res”:{“statusCode”:200,“responseTime”:7,“contentLength”:9},“message”:"GET](https://kibana.emailnow.info:5601/customerror?type=samlConfigError%22%7D,%22res%22:%7B%22statusCode%22:200,%22responseTime%22:7,%22contentLength%22:9%7D,%22message%22:%22GET) /ui/favicons/favicon-32x32.png 200 7ms - 9.0B”}

``

> **···**
>
> On Wednesday, 5 December 2018 21:18:03 UTC+5:30, Jochen Kressin wrote:
> 
> > Can you please post your Elasticsearch logfile on debug level when this error occurs? It should show the root cause of the error.
> 
> > Setting log level to debug:
> 
> > 
> 
> > [https://docs.search-guard.com/latest/troubleshooting-setting-log-level](https://docs.search-guard.com/latest/troubleshooting-setting-log-level)
> > 
> > On Wednesday, December 5, 2018 at 3:14:26 PM UTC+1, Venkata Naresh Divi wrote:
> > 
> > > I have enabled the enterprise feature in elasticsearch.yml. Find below is my elasticsearch.yml configuration
> 
> > > **searchguard.enterprise\_modules\_enabled: true** searchguard.ssl.transport.pemcert\_filepath: CN=emailnow.info.crtfull.pem  
> > > searchguard.ssl.transport.pemkey\_filepath: CN=emailnow.info.key.pem  
> > > searchguard.ssl.transport.pemkey\_password: $$$$$$$$$$$$$$$$$$  
> > > searchguard.ssl.transport.pemtrustedcas\_filepath: chain-ca.pem  
> > > searchguard.ssl.transport.enforce\_hostname\_verification: false
> > > 
> > > searchguard.ssl.http.enabled: true  
> > > searchguard.compliance.history.internal\_config\_enabled: true  
> > > searchguard.compliance.history.external\_config\_enabled: true  
> > > searchguard.compliance.history.read.metadata\_only: true
> > > 
> > > searchguard.ssl.http.pemcert\_filepath: CN=emailnow.info.crtfull.pem  
> > > searchguard.ssl.http.pemkey\_filepath: CN=emailnow.info.key.pem  
> > > searchguard.ssl.http.pemkey\_password: $$$$$$$$$$$$$$$$$$$$$$  
> > > searchguard.ssl.http.pemtrustedcas\_filepath: chain-ca.pem  
> > > searchguard.allow\_unsafe\_democertificates: true  
> > > searchguard.authcz.admin\_dn:
> > > 
> > > - CN=sgadmin
> > > 
> > > searchguard.audit.type: internal\_elasticsearch  
> > > searchguard.enable\_snapshot\_restore\_privilege: true  
> > > searchguard.check\_snapshot\_restore\_write\_privileges: true  
> > > searchguard.restapi.roles\_enabled: [“sg\_all\_access”]  
> > > cluster.routing.allocation.disk.threshold\_enabled: false  
> > > cluster.name: searchguard\_demo  
> > > network.host: 0.0.0.0  
> > > discovery.zen.minimum\_master\_nodes: 1  
> > > node.max\_local\_storage\_nodes: 3  
> > > xpack.monitoring.enabled: true  
> > > xpack.graph.enabled: false  
> > > xpack.ml.enabled: false  
> > > xpack.security.enabled: false  
> > > xpack.watcher.enabled: false
> 
> > > ``
> 
> > >
> 
> > > On Wednesday, 5 December 2018 19:41:16 UTC+5:30, Jochen Kressin wrote:
> > > 
> > > > SAML is an Enterprise feature, not a Community feature. If you have disabled the Enterprise features in elasticsearch.yml, then this error is expected.
> > > > 
> > > > On Wednesday, December 5, 2018 at 2:33:02 PM UTC+1, Venkata Naresh Divi wrote:
> > > > 
> > > > > When asking questions, please provide the following information:
> 
> > > > > - Search Guard and Elasticsearch version
> 
> > > > > 6.4.3
> 
> > > > > - Installed and used enterprise modules, if any
> 
> > > > > - JVM version and operating system version
> 
> > > > > JAVA 10.0.2, Ubuntu 18.04
> 
> > > > >
> 
> > > > > - Search Guard configuration files
> 
> > > > > authc:
> 
> > > > > basic\_internal\_auth\_domain:
> 
> > > > > enabled: true
> 
> > > > > order: 0
> 
> > > > > http\_authenticator:
> 
> > > > > type: basic
> 
> > > > > challenge: false
> 
> > > > > authentication\_backend:
> 
> > > > > type: intern
> 
> > > > > saml\_auth\_domain\_okta:
> 
> > > > > http\_enabled: true
> 
> > > > > transport\_enabled: true
> 
> > > > > order: 1
> 
> > > > > http\_authenticator:
> 
> > > > > type: ‘saml’
> 
> > > > > challenge: true
> 
> > > > > config:
> 
> > > > > idp:
> 
> > > > > metadata\_file: /home/ubuntu/ELK\_6\_4\_Stack/elasticsearch-6.4.3/config/okta.xml
> 
> > > > > entity\_id: [http://www.okta.com/\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*](http://www.okta.com/ *************** )
> 
> > > > > sp:
> 
> > > > > entity\_id: kibana-saml-demo
> 
> > > > > kibana\_url: [https://kibana.](https://kibana.)\*\*\*\*.info:5601/
> 
> > > > > roles\_key: Role
> 
> > > > > exchange\_key: ‘eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9’
> 
> > > > > authentication\_backend:
> 
> > > > > type: noop
> 
> > > > >
> 
> > > > > - Elasticsearch log messages on debug level
> 
> > > > > - Other installed Elasticsearch or Kibana plugins, if any
> 
> > > > >
> 
> > > > > I have configured Single Sign on using Okta for Kibana using search gaurd community edition. After all the set up, Elastic search is running but with Kibana Im getting customerror?type=samlConfigError#?\_g=() with SAML configuration error Something went wrong while retrieving the SAML configuration, please check your settings. Please help me with this
> 
> > > > >
> 
> > > > >

---

<div class="post-metadata">

**Author:** ![searchguard\_google\_group](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/searchguard_google_group/32/462_2.png) [@searchguard\_google\_group](https://forum.search-guard.com/u/searchguard_google_group)\
**Post date:** [December 11, 2018, 5:46pm UTC](https://forum.search-guard.com/t/saml-for-kibana-single-sign-on-using-okta/1238/6 "2018-12-11T17:46:28Z")

</div>

seems like a duplicate of [Redirecting to Google Groups](https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/search-guard/Ox4tBvpUR74/gAfEpgAnBgAJ)

> **···**
>
> On Monday, 10 December 2018 14:14:35 UTC+1, Venkata Naresh Divi wrote:
> 
> > Getting the below error when request happens
> 
> > 
> 
> > {“type”:“response”,“@timestamp”:“2018-12-10T13:05:54Z”,“tags”:,“pid”:22031,“method”:“get”,“statusCode”:200,“req”:{“url”:“/ui/favicons/favicon-32x32.png”,“method”:“get”,“headers”:{“host”:“[kibana.emailnow.info:5601](http://kibana.emailnow.info:5601)”,“connection”:“keep-alive”,“pragma”:“no-cache”,“cache-control”:“no-cache”,“user-agent”:“Mozilla/5.0 (X11; Linux x86\_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36”,“dnt”:“1”,“accept”:“image/webp,image/apng,image/_,_/\*;q=0.8”,“referer”:“[https://kibana.emailnow.info:5601/customerror?type=samlConfigError](https://kibana.emailnow.info:5601/customerror?type=samlConfigError)”,“accept-encoding”:“gzip, deflate, br”,“accept-language”:“en-GB,en-US;q=0.9,en;q=0.8”},“remoteAddress”:“202.153.46.98”,“userAgent”:“202.153.46.98”,“referer”:“[https://kibana.emailnow.info:5601/customerror?type=samlConfigError](https://kibana.emailnow.info:5601/customerror?type=samlConfigError)”},“res”:{“statusCode”:200,“responseTime”:7,“contentLength”:9},“message”:“GET /ui/favicons/favicon-32x32.png 200 7ms - 9.0B”}
> 
> > ``
> 
> > 
> 
> > On Wednesday, 5 December 2018 21:18:03 UTC+5:30, Jochen Kressin wrote:
> > 
> > > Can you please post your Elasticsearch logfile on debug level when this error occurs? It should show the root cause of the error.
> 
> > > Setting log level to debug:
> 
> > >
> 
> > > [https://docs.search-guard.com/latest/troubleshooting-setting-log-level](https://docs.search-guard.com/latest/troubleshooting-setting-log-level)
> > > 
> > > On Wednesday, December 5, 2018 at 3:14:26 PM UTC+1, Venkata Naresh Divi wrote:
> > > 
> > > > I have enabled the enterprise feature in elasticsearch.yml. Find below is my elasticsearch.yml configuration
> 
> > > > **searchguard.enterprise\_modules\_enabled: true** searchguard.ssl.transport.pemcert\_filepath: CN=emailnow.info.crtfull.pem  
> > > > searchguard.ssl.transport.pemkey\_filepath: CN=emailnow.info.key.pem  
> > > > searchguard.ssl.transport.pemkey\_password: $$$$$$$$$$$$$$$$$$  
> > > > searchguard.ssl.transport.pemtrustedcas\_filepath: chain-ca.pem  
> > > > searchguard.ssl.transport.enforce\_hostname\_verification: false
> > > > 
> > > > searchguard.ssl.http.enabled: true  
> > > > searchguard.compliance.history.internal\_config\_enabled: true  
> > > > searchguard.compliance.history.external\_config\_enabled: true  
> > > > searchguard.compliance.history.read.metadata\_only: true
> > > > 
> > > > searchguard.ssl.http.pemcert\_filepath: CN=emailnow.info.crtfull.pem  
> > > > searchguard.ssl.http.pemkey\_filepath: CN=emailnow.info.key.pem  
> > > > searchguard.ssl.http.pemkey\_password: $$$$$$$$$$$$$$$$$$$$$$  
> > > > searchguard.ssl.http.pemtrustedcas\_filepath: chain-ca.pem  
> > > > searchguard.allow\_unsafe\_democertificates: true  
> > > > searchguard.authcz.admin\_dn:
> > > > 
> > > > - CN=sgadmin
> > > > 
> > > > searchguard.audit.type: internal\_elasticsearch  
> > > > searchguard.enable\_snapshot\_restore\_privilege: true  
> > > > searchguard.check\_snapshot\_restore\_write\_privileges: true  
> > > > searchguard.restapi.roles\_enabled: [“sg\_all\_access”]  
> > > > cluster.routing.allocation.disk.threshold\_enabled: false  
> > > > cluster.name: searchguard\_demo  
> > > > network.host: 0.0.0.0  
> > > > discovery.zen.minimum\_master\_nodes: 1  
> > > > node.max\_local\_storage\_nodes: 3  
> > > > xpack.monitoring.enabled: true  
> > > > xpack.graph.enabled: false  
> > > > xpack.ml.enabled: false  
> > > > xpack.security.enabled: false  
> > > > xpack.watcher.enabled: false
> 
> > > > ``
> 
> > > >
> 
> > > > On Wednesday, 5 December 2018 19:41:16 UTC+5:30, Jochen Kressin wrote:
> > > > 
> > > > > SAML is an Enterprise feature, not a Community feature. If you have disabled the Enterprise features in elasticsearch.yml, then this error is expected.
> > > > > 
> > > > > On Wednesday, December 5, 2018 at 2:33:02 PM UTC+1, Venkata Naresh Divi wrote:
> > > > > 
> > > > > > When asking questions, please provide the following information:
> 
> > > > > > - Search Guard and Elasticsearch version
> 
> > > > > > 6.4.3
> 
> > > > > > - Installed and used enterprise modules, if any
> 
> > > > > > - JVM version and operating system version
> 
> > > > > > JAVA 10.0.2, Ubuntu 18.04
> 
> > > > > >
> 
> > > > > > - Search Guard configuration files
> 
> > > > > > authc:
> 
> > > > > > basic\_internal\_auth\_domain:
> 
> > > > > > enabled: true
> 
> > > > > > order: 0
> 
> > > > > > http\_authenticator:
> 
> > > > > > type: basic
> 
> > > > > > challenge: false
> 
> > > > > > authentication\_backend:
> 
> > > > > > type: intern
> 
> > > > > > saml\_auth\_domain\_okta:
> 
> > > > > > http\_enabled: true
> 
> > > > > > transport\_enabled: true
> 
> > > > > > order: 1
> 
> > > > > > http\_authenticator:
> 
> > > > > > type: ‘saml’
> 
> > > > > > challenge: true
> 
> > > > > > config:
> 
> > > > > > idp:
> 
> > > > > > metadata\_file: /home/ubuntu/ELK\_6\_4\_Stack/elasticsearch-6.4.3/config/okta.xml
> 
> > > > > > entity\_id: [http://www.okta.com/\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*](http://www.okta.com/ *************** )
> 
> > > > > > sp:
> 
> > > > > > entity\_id: kibana-saml-demo
> 
> > > > > > kibana\_url: [https://kibana.](https://kibana.)\*\*\*\*.info:5601/
> 
> > > > > > roles\_key: Role
> 
> > > > > > exchange\_key: ‘eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9’
> 
> > > > > > authentication\_backend:
> 
> > > > > > type: noop
> 
> > > > > >
> 
> > > > > > - Elasticsearch log messages on debug level
> 
> > > > > > - Other installed Elasticsearch or Kibana plugins, if any
> 
> > > > > >
> 
> > > > > > I have configured Single Sign on using Okta for Kibana using search gaurd community edition. After all the set up, Elastic search is running but with Kibana Im getting customerror?type=samlConfigError#?\_g=() with SAML configuration error Something went wrong while retrieving the SAML configuration, please check your settings. Please help me with this
> 
> > > > > >
> 
> > > > > >