# Jumpcloud setup saml integration with Kibana for Authentication

**URL:** <https://discuss.elastic.co/t/jumpcloud-setup-saml-integration-with-kibana-for-authentication/362693>\
**Category:** Kibana\
**Created:** [July 8, 2024, 10:04am UTC](https://discuss.elastic.co/t/jumpcloud-setup-saml-integration-with-kibana-for-authentication/362693 "2024-07-08T10:04:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Manoilayans](https://avatars.discourse-cdn.com/v4/letter/m/50afbb/32.png) [@Manoilayans](https://discuss.elastic.co/u/Manoilayans)\
**Post date:** [July 8, 2024, 10:04am UTC](https://discuss.elastic.co/t/jumpcloud-setup-saml-integration-with-kibana-for-authentication/362693/1 "2024-07-08T10:04:47Z")

</div>

Hi All,

We are planning to implement Jumpcloud integration with Kibana for Authentication.

**Configuration we added in kibana.yml:**

```auto
xpack.security.authc.providers:
  saml.saml1:
    order: 0
    realm: saml1
    description: JumpCloud SSO
    hint: Login using Jumpcloud Single Sign-On.
    icon: 'https://raw.githubusercontent.com/jumpcloud.jpg'
  basic.basic1:
    order: 1
    description: ELK Account
    hint: Login with username and password.
    icon: 'https://yt3.googleusercontent.com/ytc/AOPolaRjSDhIgwZlQz'

```

**Configuration we added in Elasticsearch.yml:**

```auto
xpack.security.authc.token.enabled: true
xpack.security.authc.realms:
  file:
    file1:
      order: 0
      enabled: true
  native:
    native1:
      order: 1
      enabled: true
      authentication.enabled: true
  saml:
    saml1:
      order: 2
      enabled: true
      idp.metadata.path: 'https://sso.jumpcloud.com/saml2/metadata/546456456'
      idp.entity_id: 'https://sso.jumpcloud.com/JumpCloud'
      sp.entity_id: 'https://xxx-xx-xx-xx.xx.xx/'
      sp.acs: 'https://xxx-xx-xx-xx.xx.xx/api/security/saml/callback'
      sp.logout: 'https://xxx-xx-xx-xx.xx.xx/logout'
      idp.use_single_logout: true
      nameid_format: 'urn:oasis:names:tc:SAML:2.0:nameid-format:persistent'
      attributes.principal: 'nameid:persistent'
      attribute_patterns.principal: '^([^@]+)@.*$'
      authorization_realms: native1

```

**Getting exception as per below while starting Kibana:**

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/c/dc9dacc62166c994d6bf18257ea91dd102b9e31c.png)

Pls let us know in case of any other details needed. Actually we implemented the same in Development Environment it was working fine. But, in Production only it is causing the problem.

Pls help us !!

---

<div class="post-metadata">

**Author:** ![Dzmitry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dzmitry/32/65026_2.png) [@Dzmitry](https://discuss.elastic.co/u/Dzmitry)\
**Post date:** [July 8, 2024, 4:12pm UTC](https://discuss.elastic.co/t/jumpcloud-setup-saml-integration-with-kibana-for-authentication/362693/2 "2024-07-08T16:12:21Z")

</div>

Hi @Manoilayans ,

Please use in-built editor to format your configuration as it is hard to understand the plain text.

Error states to enable `xpack.security.http.ssl.enabled`. I would start with adding it and see if it works.

Regards, Dima

---

<div class="post-metadata">

**Author:** ![Manoilayans](https://avatars.discourse-cdn.com/v4/letter/m/50afbb/32.png) [@Manoilayans](https://discuss.elastic.co/u/Manoilayans)\
**Post date:** [July 8, 2024, 5:07pm UTC](https://discuss.elastic.co/t/jumpcloud-setup-saml-integration-with-kibana-for-authentication/362693/3 "2024-07-08T17:07:03Z")

</div>

Thanks for your suggestion, I have updated the config using "Preformatted text" and now you can able to view the configuration properly.

---

<div class="post-metadata">

**Author:** ![Dzmitry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dzmitry/32/65026_2.png) [@Dzmitry](https://discuss.elastic.co/u/Dzmitry)\
**Post date:** [July 8, 2024, 6:12pm UTC](https://discuss.elastic.co/t/jumpcloud-setup-saml-integration-with-kibana-for-authentication/362693/4 "2024-07-08T18:12:11Z")

</div>

> [@Dzmitry](#):
>
> Error states to enable `xpack.security.http.ssl.enabled`

Can you try adding it with `true` ?

Regards, Dima