RequestTailor Preview (22 November 2026): requests as files in Git, no account, offline – on the Mac, in the browser and in the pipeline. What’s inside → +43 664 1964199Contact →

Authentication

In the Auth tab you set how a request identifies itself – for the request itself or inherited from folder and collection. RequestTailor fetches OAuth 2.0 tokens itself, refreshes them and keeps them like secrets: in the keychain or encrypted in the browser, never in the collection files.

Edition
Free
Kinds
Inherit, No auth, Basic, Bearer token, API key, OAuth 2.0, AWS Signature V4
OAuth 2.0 flows
client credentials, password, authorization code with PKCE, device code, SAML 2.0 bearer
Tokens
keychain or encrypted in the browser
Certificates
PEM, PKCS#12 (Mac app, rt)

The kinds

ChoiceWhat it does
InheritTakes the auth of the folder or collection (auth: inherit in the file).
No authSends without authentication.
BasicUser and password as Authorization: Basic.
Bearer tokenA token as Authorization: Bearer.
API keyA key as a header or query parameter.
OAuth 2.0Fetches and renews tokens itself, see below.
AWS Signature V4Signs the request for AWS services.

Passwords, tokens and keys belong in secret variables: you write {{token}} into the field and the value lives in the keychain (secret variables). If a credential is typed into a file in plain text, the secret scanner refuses the commit.

OAuth 2.0

RequestTailor supports the flows client credentials, password, authorization code with PKCE, device code and SAML 2.0 bearer; implicit is read only. OpenCollection does not know device code and SAML 2.0 bearer – they work only as the collection default and are kept in the extensions section of opencollection.yml.

Auth tab with OAuth 2.0 and the flow Authorization code, Endpoints with Authorization URL, Callback URL, Token URL and Refresh URL, below it Client with the client secret as a secret variable, Send client as and Scope
The Auth tab with OAuth 2.0 and the Authorization code flow.
  1. Auth set to OAuth 2.0, the Flow below.
  2. Endpoints: Authorization URL, Callback URL, Token URL and optionally Refresh URL.
  3. Client: Client ID, Client secret (as a secret variable), Send client as and Scope.
  1. Open the request, folder or collection and choose OAuth 2.0 in the Auth tab.
  2. Choose Authorization code as the Flow and enter the identity provider’s endpoints.
  3. Enter the client ID; the client secret as a secret variable such as {{clientSecret}}. Leave PKCE at S256 (recommended).
  4. Under Token, set which token goes where – for example Access token into the Authorization header with the prefix Bearer.
  5. Send. If there is no token yet, RequestTailor opens the sign-in in the browser; after that it fetches and renews tokens itself as long as Fetch a token automatically and Refresh an expired token are ticked.

View and delete tokens

Get new token fetches a new token right away, Tokens… shows the stored ones.

OAuth 2.0 tokens dialog with one token for idp.example and mock-client, the fetch time, status valid for 59 min refreshable, Delete and Delete all
Stored tokens: provider, fetch time and validity – never the value.

The interface sees only a token’s provider, time, validity and whether it can be refreshed. Tokens are stored like secrets: in the operating system’s keychain – the Mac app and rt share the entries – or encrypted in the browser, never in collection files. Every token is masked in a request’s report.

AWS Signature V4

With AWS Signature V4, RequestTailor signs the finished request for AWS services. The signature is checked against AWS’s official test vectors. Keys belong in secret variables; they are masked in the report. The signature is made after the OAuth token and after the plugins, so it covers the request as it goes on the wire.

In a pipeline

rt send and rt run use the same auth. With --no-prompt, a flow that needs a person (browser sign-in, device code) fails instead of waiting – right for pipelines. Client credentials run without a person; pass the secret with --var clientSecret="$CLIENT_SECRET".

See also

Sources on this page

The superscript numbers in the text point here. Tap one to see the source right where it is used; all sources of this website are listed on one page.

  1. 1

    OAuth 2.0, AWS SigV4, client certificates ↑Product · RequestTailor core repository, crates/rt-core (model::auth), crates/rt-format/src/auth, testdata/sigv4 · checked on 2026-11-22

  2. 2

    Secrets in the keychain and from external vaults ↑Product · RequestTailor core repository, CLAUDE.md (Produktprinzip 3), crates/rt-cli/README.md (externe Secrets), website/docs/environments · checked on 2026-11-22

Frequently asked

Short answers.

Does RequestTailor support OAuth 2.0 with PKCE?
Yes. Authorization code with PKCE (S256), plus client credentials, password, device code and SAML 2.0 bearer. Implicit is read only.
Where does RequestTailor keep OAuth tokens?
In the operating system’s keychain (the Mac app and rt share the entries) or encrypted in the browser (web app), never in the collection files. The interface only sees validity and provider.
Can I sign requests to AWS?
Yes, with AWS Signature V4. The implementation is checked against AWS’s test vectors; the keys belong in secret variables.

Your question isn’t here? Talk to me: +43 664 1964199 office@clouddna.at Get in touch

Contact

Requests in the repo instead of an account? Talk to us.

Free is free and stays free. For an early copy, for Enterprise, for the OData plugin on your SAP system or for a wish for Pro and Team: write to me. I reply within one working day, personally.

Martin KochManaging Director, CloudDNAI read every request myself and reply personally.