-
Notifications
You must be signed in to change notification settings - Fork 122
Description
Initially asked in #341
Is it possible to mark some fields as "secured" so that their values are not stored when closing Restfox? I have a bad feeling to have passwords or OAuth client secrets of customers stored somewhere on my machine. A bad person could probably extract them from the Restfox settings.
It would be perfect if Restfox would ask for those values if they are empty when executing the request the first time.
My samples are:
- requesting an OAuth token using client_id/client_secret in a request with "FORM URL Encoded" body. The client secret should not be persisted.
- setting an "Authorization" header of type "Basic" with a base64 encoded password (which is the old style way to authorize, was some time ago enhanced by the next one). Here, it would be helpful if only the password part of the Header value ("Basic encoded_password") would be secured instead of the full header value.
- or setting the "Auth" type to "Basic" and entering username/password. Same for Auth type "OAuth 2.0" (see my first point)
Maybe enhance the "Environment" feature, so that I can define variables "PASSWORD_FOR_CUSTOMER1" or "CLIENT_SECRET_FOR_CUSTOMER2" and either enter their values directly or Restfox asks me when they are used? In my sample 2 with the Authorization header, I could define the header value as "Basic {{PASSWORD_FOR_CUSTOMER1}}" and Restfox would look in the environment variables table and ask for the value if it not already entered?