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'm using Insomnia to test API-REST interfaces and the truth is that I have multiple requests (too many) that I have to use frequently.
For authorizations I use "OAuth 2" with GRANT_TYPE = "Client Credentials".
The problem I have is that sometimes the administrators change the URLs to get 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 to create a functionality called "LOCAL CREDENTIALS" (for example) that gets the configuration values from a local repository.
Thus, we would have
GRANT TYPE = LOCAL CREDENTIALS
REPOSITORY = c:/xxx/yyy/....
CONFIG_ID = MY-config-name-001
This option would obtain the configuration values described above relative to the set "MY-Configuration-name-001" and with them make the request to obtain the token.
If the administrator changes any of the configuration values, the user will be able to update the local repository and it will be available for all requests that use that configuration
Obviously, in each session of the application, the first time the local storage had to be accessed, 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
-
I'm using Insomnia to test API-REST interfaces and the truth is that I have multiple requests (too many) that I have to use frequently.
For authorizations I use "OAuth 2" with GRANT_TYPE = "Client Credentials".
The problem I have is that sometimes the administrators change the URLs to get 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 to create a functionality called "LOCAL CREDENTIALS" (for example) that gets the configuration values from a local repository.
Thus, we would have
GRANT TYPE = LOCAL CREDENTIALS
REPOSITORY = c:/xxx/yyy/....
CONFIG_ID = MY-config-name-001
This option would obtain the configuration values described above relative to the set "MY-Configuration-name-001" and with them make the request to obtain the token.
If the administrator changes any of the configuration values, the user will be able to update the local repository and it will be available for all requests that use that configuration
Obviously, in each session of the application, the first time the local storage had to be accessed, the username and password would be requested.
I hope my suggestion is clear.
Thank you for your time
Beta Was this translation helpful? Give feedback.
All reactions