mirror of https://github.com/mountain-loop/yaak.git synced 2026-08-21 02:44:12 +02:00

Files

T

Gregory Schier 0f8413c441 Read OAuth 2.0 token responses from the send instead of the filesystem

Both token requests opened HttpResponse.bodyPath with readFileSync, which
ties the plugin to bodies living on a filesystem. The send now hands the body
back, so they read it from there and keep working once bodies move into the
blob DB and in the browser Worker, where there is no fs to read.

text() on a response with no body returns "", which is what the bodyPath
check produced, so an empty response still parses to {} rather than throwing.

2026-08-16 10:09:43 -07:00

src

Read OAuth 2.0 token responses from the send instead of the filesystem

2026-08-16 10:09:43 -07:00

tests

fix: Add username to the tokenStoreKey so the saved token is invalidated when the user changes in the environment (#426 )

2026-08-14 13:50:48 -07:00

package.json

Run oxfmt across repo, add format script and docs

2026-03-13 10:15:49 -07:00

README.md

Run oxfmt across repo, add format script and docs

2026-03-13 10:15:49 -07:00

screenshot.png

OAuth 2 plugin README

2025-07-19 21:47:19 -07:00

tsconfig.json

Fix lint errors after upgrades and narrow tsc

2025-07-14 10:09:08 -07:00

README.md

OAuth 2.0 Authentication

An OAuth 2.0 authentication plugin that supports multiple grant types and flows, enabling secure API authentication with OAuth 2.0 providers.

Overview

This plugin implements OAuth 2.0 authentication for requests, supporting the most common OAuth 2.0 grant types used in modern API integrations. It handles token management, automatic refresh, and PKCE (Proof Key for Code Exchange) for enhanced security.

Supported Grant Types

Authorization Code Flow

The most secure and commonly used OAuth 2.0 flow for web applications.

Standard Authorization Code flow
Optional PKCE (Proof Key for Code Exchange) for enhanced security
Supports automatic token refresh

Client Credentials Flow

Ideal for server-to-server authentication where no user interaction is required.

Implicit Flow

Legacy flow for single-page applications (deprecated but still supported):

Direct access token retrieval
No refresh token support
Suitable for legacy integrations

Resource Owner Password Credentials Flow

Direct username/password authentication.

User credentials are exchanged directly for tokens
Should only be used with trusted applications
Supports automatic token refresh

Features

Automatic Token Management: Handles token storage, expiration, and refresh automatically
PKCE Support: Enhanced security for Authorization Code flow
Token Persistence: Stores tokens between sessions
Flexible Configuration: Supports custom authorization and token endpoints
Scope Management: Configure required OAuth scopes for your API
Error Handling: Comprehensive error handling and user feedback

Usage

Configure the request, folder, or workspace to use OAuth 2.0 Authentication
Select the appropriate grant type for your use case
Fill in the required OAuth 2.0 parameters from your API provider
The plugin will handle the authentication flow and token management automatically

Compatibility

This plugin is compatible with OAuth 2.0 providers including:

Google APIs
Microsoft Graph
GitHub API
Auth0
Okta
And many other OAuth 2.0 compliant services