Skip to content

Authentication

All major implementations support automatic Base64 encoding for Basic auth:

GET https://api.example.com/protected
Authorization: Basic username password
VS CodeJetBrainshttpyackulala

VS 2022 does not document automatic Base64 encoding for Basic auth.

VS Code REST Client also accepts username:password (colon-separated) or pre-encoded Base64 values.

GET https://api.example.com/protected
Authorization: Digest username password
VS CodeJetBrainshttpyac

The client handles the challenge-response flow automatically.

GET https://service.amazonaws.com/resource
Authorization: AWS accessKeyId secretAccessKey token:sessionToken region:us-east-1 service:s3
VS Codehttpyackulala

JetBrains does not have built-in AWS auth.

VS Code
GET https://api.example.com/protected
Authorization: COGNITO username password region userPoolId clientId

Unique to VS Code REST Client.

httpyac has the most comprehensive OAuth2 support with multiple grant types:

GET https://api.example.com/protected
Authorization: openid client_credentials myPrefix

Supported flows: authorization_code (with optional PKCE), implicit, password, client_credentials, device_code, and token exchange. Variables configure endpoints: {{prefix}}_tokenEndpoint, {{prefix}}_clientId, etc.

VS Code REST Client supports Azure AD tokens via {{$aadToken}}, {{$aadV2Token}}, and generic OIDC via {{$oidcAccessToken}}.

JetBrains supports OAuth 2.0 through IDE-integrated dialogs rather than in-file syntax.

kulala.nvim supports OAuth2, Negotiate, and SSL auth.

JetBrainskulala

JetBrains uses @use-os-credentials metadata to use OS-level credentials.

See SSL & Certificates for SSL/certificate configuration details.

Per-client support for every auth method: Auth & Security comparison.