# Openid connect for kibana login

**URL:** <https://discuss.elastic.co/t/openid-connect-for-kibana-login/211792>\
**Category:** Kibana\
**Tags:** elastic-stack-security\
**Created:** [December 13, 2019, 12:40pm UTC](https://discuss.elastic.co/t/openid-connect-for-kibana-login/211792 "2019-12-13T12:40:32Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![amiya-santra](https://avatars.discourse-cdn.com/v4/letter/a/bc8723/32.png) [@amiya-santra](https://discuss.elastic.co/u/amiya-santra)\
**Post date:** [December 13, 2019, 12:40pm UTC](https://discuss.elastic.co/t/openid-connect-for-kibana-login/211792/1 "2019-12-13T12:40:32Z")

</div>

Hi, I am using an x-pack trail license, using openid connect to use our customized oauth2.0 but, it is giving error :  
Successfully exchanged code for ID Token: [null] and Access Token  
[2019-12-13T15:26:42,047][DEBUG][o.e.x.s.a.o.OpenIdConnectRealm] [localhost] Failed to consume the OpenIdConnectToken  
org.elasticsearch.ElasticsearchSecurityException: Token Response did not contain an ID Token or parsing of the JWT failed.

Is there any to configure open id with oauth2.0  
Thanks

---

<div class="post-metadata">

**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:** [December 13, 2019, 12:57pm UTC](https://discuss.elastic.co/t/openid-connect-for-kibana-login/211792/2 "2019-12-13T12:57:56Z")

</div>

> [@amiya-santra](#):
>
> Is there any to configure open id with oauth2.0

No. oAuth2 is an authorization standard. OpenID Connect is an authentication standard, built on top of oAuth2. Our OpenID Connect realm can't work with custom oAuth2 providers that do not implement OpenID Connect.

---

<div class="post-metadata">

**Author:** ![amiya-santra](https://avatars.discourse-cdn.com/v4/letter/a/bc8723/32.png) [@amiya-santra](https://discuss.elastic.co/u/amiya-santra)\
**Post date:** [December 13, 2019, 1:38pm UTC](https://discuss.elastic.co/t/openid-connect-for-kibana-login/211792/3 "2019-12-13T13:38:08Z")

</div>

Thanks for replying . so if i have open source open id connecter like Keycloak or my own open id connector then it will work?

---

<div class="post-metadata">

**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:** [December 13, 2019, 1:51pm UTC](https://discuss.elastic.co/t/openid-connect-for-kibana-login/211792/4 "2019-12-13T13:51:35Z")

</div>

Yes, our implementation follows the standard as defined in [https://openid.net/specs/openid-connect-core-1\_0.html](https://openid.net/specs/openid-connect-core-1_0.html), and if the OpenID Connect Provider also does, then it should work just fine.  
Our documentation is available at [https://www.elastic.co/guide/en/elasticsearch/reference/7.5/oidc-guide.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.5/oidc-guide.html)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 10, 2020, 1:51pm UTC](https://discuss.elastic.co/t/openid-connect-for-kibana-login/211792/5 "2020-01-10T13:51:41Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.