Authentication
Authentication
Authorize requests with tokens, keys, OAuth and signatures, set once and inherited.
Overview
Relay adds authentication to a request when it sends it, whether that's a header, a query parameter, a signature, or a response to a server's challenge. You choose an auth type in the Auth tab, and Relay handles the details, from fetching and refreshing OAuth 2.0 tokens to signing requests for AWS.
You can set authentication on a request, a folder, a collection, a workspace or globally. A request inherits it from the nearest level that sets it, so you configure credentials once and every request below uses them.
Topics
Essentials
- Inheriting authentication: Set authentication once on a workspace, collection or folder and let requests inherit it.
Tokens and keys
- Authorizing with tokens and keys: Send a bearer token, username and password, API key or signed JWT with each request.
OAuth
- Authorizing with OAuth 2.0: Get, refresh and send OAuth 2.0 access tokens with the authorization code or client credentials grant.
- Signing requests with OAuth 1.0: Sign requests with OAuth 1.0a consumer and token credentials.
Challenges and signatures
- Authenticating with Digest and NTLM: Answer a server's Digest or NTLM challenge with a username and password.
- Signing requests with AWS Signature: Sign requests to AWS services with Signature Version 4.
- Authenticating with Hawk: Sign requests with Hawk credentials.
See Also
- Keeping secrets on your Mac: Keep tokens and passwords out of shared workspace files.
- Using client and CA certificates: Present client certificates and trust your own certificate authorities.