Basic authentication
Section titled “Basic authentication”All major implementations support automatic Base64 encoding for Basic auth:
GET https://api.example.com/protectedAuthorization: Basic username passwordVS 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.
Digest authentication
Section titled “Digest authentication”GET https://api.example.com/protectedAuthorization: Digest username passwordThe client handles the challenge-response flow automatically.
AWS Signature v4
Section titled “AWS Signature v4”GET https://service.amazonaws.com/resourceAuthorization: AWS accessKeyId secretAccessKey token:sessionToken region:us-east-1 service:s3JetBrains does not have built-in AWS auth.
AWS Cognito
Section titled “AWS Cognito”GET https://api.example.com/protectedAuthorization: COGNITO username password region userPoolId clientIdUnique to VS Code REST Client.
OAuth 2.0 / OpenID Connect
Section titled “OAuth 2.0 / OpenID Connect”httpyac has the most comprehensive OAuth2 support with multiple grant types:
GET https://api.example.com/protectedAuthorization: openid client_credentials myPrefixSupported 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.
NTLM/Kerberos
Section titled “NTLM/Kerberos”JetBrains uses @use-os-credentials metadata to use OS-level credentials.
Client certificates
Section titled “Client certificates”See SSL & Certificates for SSL/certificate configuration details.
Client support
Section titled “Client support”Per-client support for every auth method: Auth & Security comparison.