# Support OpenId Connect Authorization Type **URL:** \ **Category:** Help Hub\ **Tags:** authorization, authentication\ **Created:** [November 19, 2018, 10:49pm UTC](https://community.postman.com/t/support-openid-connect-authorization-type/3328 "2018-11-19T22:49:12Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![JSeifert](https://avatars.discourse-cdn.com/v4/letter/j/9de0a6/32.png) [@JSeifert](https://community.postman.com/u/JSeifert)\ **Post date:** [November 19, 2018, 10:49pm UTC](https://community.postman.com/t/support-openid-connect-authorization-type/3328/1 "2018-11-19T22:49:12Z")
Just wanted to start the conversation around OpenId Connect (OPIDC) and using the Authorization types. Our company has an API that sits on top of an authority that supports Open Id Connect that is a layer on top of OAuth2. When using the OAuth2 authorization type everything looks to be working except the response from the token endpoint is looking for access\_token and does not support id\_token. In our case we would like to be able to chose when setting up the OAuth2 settings if postman should use the id\_token or the access\_token. ---
**Author:** ![martea](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/martea/32/1676_2.png) [@martea](https://community.postman.com/u/martea)\ **Post date:** [April 24, 2019, 2:25pm UTC](https://community.postman.com/t/support-openid-connect-authorization-type/3328/2 "2019-04-24T14:25:34Z")
This would really help if there was a support for JWT access and reference token, to test certain flows. ---
**Author:** ![system](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/system/32/29796_2.png) [@system](https://community.postman.com/u/system)\ **Post date:** [December 9, 2024, 2:33pm UTC](https://community.postman.com/t/support-openid-connect-authorization-type/3328/3 "2024-12-09T14:33:41Z")
Closed on December 9, 2024, 2:33pm UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.