# Twitch authenticate using OIDC id\_token missing

**URL:** <https://discuss.dev.twitch.com/t/twitch-authenticate-using-oidc-id-token-missing/10691>\
**Category:** API\
**Created:** [June 13, 2017, 12:57am UTC](https://discuss.dev.twitch.com/t/twitch-authenticate-using-oidc-id-token-missing/10691 "2017-06-13T00:57:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![wlami](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/wlami/32/2891_2.png) [@wlami](https://discuss.dev.twitch.com/u/wlami)\
**Post date:** [June 13, 2017, 12:57am UTC](https://discuss.dev.twitch.com/t/twitch-authenticate-using-oidc-id-token-missing/10691/1 "2017-06-13T00:57:17Z")

</div>

Hi there,

I am trying to configure Twitch as an Open ID Connect Identity Provider in my Keycloak server. As far as I understand the API authentication documentation this should be possible. I am implementing the Authorization Code Flow and am currently stuck at step 4) “We respond with a JSON-encoded…” The documentation says “OIDC responses include an additional OAuth 2.0 token, an ID token,” which would be compliant to the linked OpenID Connect spec. However my authentication server keycloak explodes while processing the response from the token endpoint because the response looks like this: `{"access_token":"a","refresh_token":"a","scope":["openid"]}` So there is no `id_token` but an `refresh_token` instead. The content is not JWT:

tl/dr: The token endpoint returns a field named “refresh\_token” instead of “id\_token”. Am I calling it wrong?

Regards,  
Wlami

---

<div class="post-metadata">

**Author:** ![system](https://d2opxh93rbxzdn.cloudfront.net/original/2X/0/05909729875cce3b53e59d5561c4d23bb14948fc.png) [@system](https://discuss.dev.twitch.com/u/system)\
**Post date:** [July 13, 2017, 1:10am UTC](https://discuss.dev.twitch.com/t/twitch-authenticate-using-oidc-id-token-missing/10691/2 "2017-07-13T01:10:12Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Barkspawn](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/barkspawn/32/3391_2.png) [@Barkspawn](https://discuss.dev.twitch.com/u/Barkspawn)\
**Post date:** [September 27, 2017, 9:44pm UTC](https://discuss.dev.twitch.com/t/twitch-authenticate-using-oidc-id-token-missing/10691/3 "2017-09-27T21:44:21Z")

</div>

Can you double check the URL you’re posting against?  
OIDC flows require a post to a new enpoint:  
[https://api.twitch.tv/kraken/oauth2/token](https://api.twitch.tv/kraken/oauth2/token)

If you post the code to the OAuth API, [https://api.twitch.tv/kraken/oauth2/authorize](https://api.twitch.tv/kraken/oauth2/authorize), you’ll get a standard OAuth refresh token and access token