resonate-token-authentication-typescript

Authenticate clients with JWT tokens and authorize access by prefix.

6|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/resonatehq/resonate-skills --skill resonate-token-authentication-typescript
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resonate-token-authentication-typescript
Source: https://github.com/resonatehq/resonate-skills/tree/main/resonate-token-authentication-typescript
Command: npx skills add https://github.com/resonatehq/resonate-skills --skill resonate-token-authentication-typescript

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

JWT-based authentication and prefix-based authorization secure access to the Resonate server, enabling multi-tenant isolation and role-based control.

Core Features & Use Cases

  • JWT-based authentication: Verify client identities via signed tokens and enforce token validity.
  • Prefix-based authorization: Isolate access to promises by tenant or worker using the optional prefix claim.
  • Server configuration and workflow patterns: Provide guidance for generating keys, issuing tokens, and configuring the server for secure API access.
  • Real-world use cases: multi-tenant SaaS apps, cross-tenant isolation, RBAC.

Quick Start

Generate an RSA key pair, configure the server with the public key, and issue signed JWTs with an optional prefix to enable multi-tenant access.

Frequently Asked Questions about resonate-token-authentication-typescript

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement JWT-based authentication for multi-tenant applications?

JWT-based authentication for multi-tenant applications verifies client identities via signed tokens and enforces token validity to control access to server resources.

What is prefix-based authorization and how does it isolate tenant access?

Prefix-based authorization isolates tenant access by using an optional prefix claim in the JWT, restricting different clients to access only their own promises in multi-tenant environments.

How do I configure a server for JWT authentication and RBAC?

Configuring a server for JWT authentication and RBAC requires generating an RSA key pair, providing the server with the public key, and issuing signed tokens with optional prefixes to clients.

Can I use JWT tokens to restrict client access to specific promises?

Yes, you can use JWT tokens with an optional prefix claim to enforce prefix-based authorization, isolating access so different clients only access their own designated promises.

What cryptography do I need to secure multi-tenant API access with JWTs?

Securing multi-tenant API access with JWTs requires a private key for signing tokens and a server configured with the corresponding public key to validate client requests.