Authorization
Secrets and what goes into files
Which authorization fields are secrets, where Luvin stores them, what is written to files and git, and where values are masked.
A secret is a value that must not leak: a password, a token, a key. Luvin keeps the values of secrets out of the files of your workspace, so you can put the workspace in git.
Example: the same request, saved two ways
Section titled “Example: the same request, saved two ways”You type abc123 in Token. The request file keeps no token:
auth: type: bearer prefix: Bearerabc123 is stored encrypted on your computer. A teammate who opens the collection has to type it again.
You type {{token}} in Token. The file keeps the name:
auth: type: bearer token: "{{token}}" prefix: BearerEach person fills in token in their own environment. The setup is shared, the value is not.
A value that contains {{ counts as a reference and goes to the file as written.
Which fields are secrets
Section titled “Which fields are secrets”| Type | Secret fields | Written to the file as typed |
|---|---|---|
| API Key | Value | Name, Send in |
| Basic Auth | Password | Username |
| Bearer Token | Token | Header prefix |
| OAuth 2.0 | Client Secret, Password | URLs, Client ID, Username, Scope, Audience |
| OAuth 1.0 | Consumer Secret, Access Token, Token Secret | Consumer Key, Realm, Signature method |
| Digest Auth, WSSE Auth, NTLM Auth | Password | Username, Domain, Workstation |
| AWS Sig v4 | Secret Access Key, Session Token | Access Key ID, Service, Region |
| Akamai EdgeGrid | Client Token, Client Secret, Access Token | Headers to sign, Max body size |
Secret fields are hidden while you type. Click the eye (Show / Hide) to see them. Use a variable for any other value you do not want in git, such as a username or a Client ID.
The values you paste in the Credentials of an environment and the variables you mark as secrets are also kept out of the files.
Where the values are stored
Section titled “Where the values are stored”| Version | Storage |
|---|---|
| Desktop app | Encrypted with the keychain of the operating system. If it is not available, the app does not store secret values: you type them again. |
| Browser version | Encrypted in the browser of this device, with a key that cannot be exported. |
Secrets typed as-is are kept per request, per collection (collection.yaml holds the rest), per workflow setting (flow-auth.yaml holds the rest) and per environment.
What goes into files and git
Section titled “What goes into files and git”| File | Has |
|---|---|
requests/*.request.yaml |
The auth block, without the secret fields typed as-is. |
collection.yaml |
The collection’s auth, without secrets typed as-is. |
flow-auth.yaml |
The authorization of workflows, without secrets typed as-is. |
environments/*.yaml |
The names of secrets, never their values. |
The OAuth 2.0 access and refresh tokens are never written anywhere: they stay in memory while the collection is open.
Where values are masked
Section titled “Where values are masked”- Sent request of a request shows the
Authorizationheader shortened, likeBearer eyJhbGci…x9Qw. Secret values in the URL and headers show as••••. - Results and reports of workflows show the secrets and credentials of the environment as
••••. - Dev Tools shows secrets masked, and Copy as cURL writes
<secret>where you must put the value. - In the Headers tab, the
Authorizationrow added by Luvin is shown asBearer ••••••.