You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using Insomnia to test API-REST interfaces and, the truth is that I have multiple requests (too many) that I must use often.
For authorizations I use "OAuth 2" with GRANT_TYPE = "Client Credentials".
The problem I have is that sometimes they change the URLs to obtain the tokens, other times they change the "CLIENT_ID" and sometimes the "CLIENT SECRET", sometimes even all of them. This involves going to each of the requests and updating the values. It's very tedious.
My suggestion is that we could have an option called "LOCAL CREDENTIALS" (for example) that would obtain the values for obtaining the authorization token from a local repository.
Thus, we would have in "OAuth 2"
GRANT TYPE = LOCAL CREDENTIALS
REPOSITORY = c:/xxx/yyy/....
CONFIG_ID = MY-Configuration-name-001
This option would obtain the configuration values described at the beginning from the set "MY-Configuration-name-001" and with them it would make the request to obtain the token.
If any of the values to get the token change you could update the local repository and the information would be available for all requests
Obviously, in each session of the application, the first time you have to access the local repository , the username and password would be requested.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I am using Insomnia to test API-REST interfaces and, the truth is that I have multiple requests (too many) that I must use often.
For authorizations I use "OAuth 2" with GRANT_TYPE = "Client Credentials".
The problem I have is that sometimes they change the URLs to obtain the tokens, other times they change the "CLIENT_ID" and sometimes the "CLIENT SECRET", sometimes even all of them. This involves going to each of the requests and updating the values. It's very tedious.
My suggestion is that we could have an option called "LOCAL CREDENTIALS" (for example) that would obtain the values for obtaining the authorization token from a local repository.
Thus, we would have in "OAuth 2"
GRANT TYPE = LOCAL CREDENTIALS
REPOSITORY = c:/xxx/yyy/....
CONFIG_ID = MY-Configuration-name-001
This option would obtain the configuration values described at the beginning from the set "MY-Configuration-name-001" and with them it would make the request to obtain the token.
If any of the values to get the token change you could update the local repository and the information would be available for all requests
Obviously, in each session of the application, the first time you have to access the local repository , the username and password would be requested.
All reactions