search

Kong / insomnia

The open-source, cross-platform API client for GraphQL, REST, WebSockets, SSE and gRPC. With Cloud, Local and Git storage.
https://insomnia.rest
Apache License 2.0
34.77k stars 1.97k forks source link

OAuth 2 - Extra parameters #2700

Open lasrol opened 4 years ago

lasrol commented 4 years ago

When using the OAuth 2.0 flow we are required to add additional parameters. In our case it is acr_values, but i think it would be good to add any extra parameters any might require.

Currently we now use the Bearer auth instead, but it is a bit inconvenient to manually request a token and copy paste it into diffrent environments.

It might be better to allow clients to create any custom params they might require. A simple key/vaule list?

ericp3reira commented 4 years ago

Hi people! May I work on this one?

lasrol commented 4 years ago

Since there has not been any reply, i would say go for it 👍 I assume they will just be happy to get a PR for this.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

jclusso commented 3 years ago

I realized you can just add the extra parameters to the Authorization URL. Figured it might help someone else out since I didn't immediately come up with this solution.

rtconner commented 2 years ago

Thanks @jclusso This is still an issue but its nice to have a workaround.

I'm hitting this issue with response_type on ebay API: https://developer.ebay.com/api-docs/static/oauth-consent-request.html

ZainAli104 commented 1 year ago

Thanks @jclusso This is still an issue but its nice to have a workaround.

I'm hitting this issue with response_type on ebay API: https://developer.ebay.com/api-docs/static/oauth-consent-request.html

Can you tell me what is exact issue and explain that issue, so I will fix this

MSuih commented 1 year ago

Sorry if it's against your policy to reply to three-year old issues.

My use case: https://dev.procountor.com/m2m-authentication/#client%20credentials%20grant%20flow_1

So the api requires that I pass api_key parameter when authenticating. If it is missing, the server replies with HTTP 400. Right now this is not possible to do in Insomnia. The workaround of using url parameters doesn't work because the API ignores those due to security concerns.