ShellYard

Auth presets

Basic, Bearer, API key, OAuth2 (auth code with PKCE, client credentials, password), Digest, NTLM, AWS SigV4, vault, inherit. {{env}} substitution in every OAuth field.

Auth applies per-request or via collection / folder inheritance.

Presets

PresetNotes
NoneNo auth header sent
Basicusername + password
Bearerstatic token
API keyheader or query, configurable name
OAuth2authorization code (with PKCE), client credentials, password grant — token caching included
DigestRFC 2617
NTLMWindows-style NTLMv2
AWS SigV4service + region + credentials
Vaultresolves a vault credential ID at request time
Inherituse the parent collection or folder’s auth

OAuth2 details

The OAuth2 preset supports three grants:

  • Authorization code with PKCE — opens a browser to the authorize URL, captures the code, exchanges for a token. PKCE (S256 verifier) is mandatory for public clients.
  • Client credentials — server-to-server, no user interaction.
  • Password grant — username + password against the token endpoint (deprecated by OAuth 2.1 but still supported by many enterprise IdPs).

Negotiated bearer tokens cache in memory for the request batch. Refresh tokens auto-renew before expiry.

{{env}} substitution works in every OAuth string field — token URL, client ID, client secret, scope, redirect URI, audience, custom params. Same Environment-variable syntax as URLs and headers.

Inheritance + override

Set auth on a collection and every request beneath inherits unless it explicitly overrides. Folder-level overrides cascade the same way (folder auth overrides collection, request auth overrides folder).

The request row shows an inherits from hint when auth is not local to the request — no surprise about which auth is actually flying. Right-click any folder for Edit inherited auth to open an AuthEditor bound to that folder so a single OAuth config can cover every request beneath it.