[GH-ISSUE #3490] [feature]: OAuth 2.0: able to switch between id_token and access_token when scope is openid #1180

New issue

Open

opened 2026-03-16 19:01:01 +03:00 by kerem · 2 comments

kerem commented

2026-03-16 19:01:01 +03:00

Owner

Originally created by @tonnico on GitHub (Nov 3, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3490

Is there an existing issue for this?

I have searched the existing issues

Summary

With scope openid you will receive something like this:

{
    "token_type": "Bearer",
    "scope": "openid",
    "access_token": "<access-token>",
    "refresh_token": "<refresh-token",
    "id_token": "<id-token>"
}

At least I would wish to be able to choose between access_token or id_token.

Why should this be worked on?

Some APIs will need the id_token instead of the access_token. Until now you need to inspect the network calls (F12) and copy the token response to use the id_token.

Originally created by @tonnico on GitHub (Nov 3, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3490 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Summary With scope `openid` you will receive something like this: ```json { "token_type": "Bearer", "scope": "openid", "access_token": "<access-token>", "refresh_token": "<refresh-token", "id_token": "<id-token>" } ``` At least I would wish to be able to choose between `access_token` or `id_token`. ### Why should this be worked on? Some APIs will need the `id_token` instead of the `access_token`. Until now you need to inspect the network calls (F12) and copy the token response to use the `id_token`.