skills.rest
berkayoztunc
berkayoztuncCOMMUNITY
Explore all skills by this author →
Website𝕏@whitemoondevGitHub

OAuth Discovery Support

Publish OAuth and OpenID Connect discovery metadata for Orquestra-hosted APIs.

21|1|Updated Feb 20, 2026
Search Tags:#oauth#discovery#jwks#agent authentication#openid-configuration#authorization endpoint#protected APIs
One-click install
npx skills add https://github.com/berkayoztunc/orquestra --skill oauth-discovery-support
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: OAuth Discovery Support
Source: https://github.com/berkayoztunc/orquestra/tree/main/packages/frontend/assets/.well-known/agent-skills/oauth-discovery
Command: npx skills add https://github.com/berkayoztunc/orquestra --skill oauth-discovery-support

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

It helps clients discover the correct OAuth authorization and token endpoints (and related identity configuration) for Orquestra’s protected REST APIs without manual configuration.

Core Features & Use Cases

  • Publishes OAuth and OpenID discovery documents for browser-based authorization flows hosted on the Orquestra API host.
  • Standardizes required discovery fields like issuer, JWKS URI, endpoints, and supported grant/response types.
  • Supports protected API access from OAuth-capable client apps and web frontends that need to bootstrap authentication parameters automatically.

Quick Start

Ask your AI agent or OAuth client to fetch Orquestra’s discovery URLs and read the issuer, authorization_endpoint, token_endpoint, and jwks_uri values for configuring its login flow.

Frequently Asked Questions about OAuth Discovery Support

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

FAQPage Schema
What is OAuth discovery and how does it work for protected APIs?▼

OAuth discovery auto-advertises standardized OpenID Connect metadata, allowing browser-based clients to dynamically fetch authorization endpoints, token endpoints, and JWKS URIs without manual configuration.

How do I configure an OAuth client using openid-configuration?▼

To configure an OAuth client, fetch the .well-known openid-configuration URL and read the issuer, authorization_endpoint, token_endpoint, and jwks_uri values to bootstrap your login flow.

What fields are required in an oauth-authorization-server metadata document?▼

Required fields include issuer, authorization_endpoint, token_endpoint, jwks_uri, grant_types_supported, and response_types_supported to ensure clients can properly authenticate with protected APIs.

Can I use dynamic endpoint discovery for browser-based API clients?▼

Yes, dynamic endpoint discovery is specifically applicable when building or configuring browser-based protected API clients that need to automatically bootstrap identity parameters and authentication endpoints.

Do I need to manually specify jwks_uri for agent authentication?▼

No, you do not need to manually specify the jwks_uri because the discovery support automatically exposes it within the standardized metadata documents for your OAuth-capable client apps.

Related Skills

Explore More Software Engineering Skills→
berkayoztuncberkayoztunc
21

OAuth Protected Resource Metadata Support

Publish OAuth protected resource metadata via a .well-known endpoint and WWW-Authenticate headers.

Community
Basic
team-telnyxteam-telnyx
3

telnyx-oauth-javascript

Implement OAuth 2.0 authentication flows for Telnyx API access using JavaScript SDK examples.

Official
Intermediate
majiayu000majiayu000
258

auth-security

Implement OAuth 2.1 with PKCE and JWT verification for secure authentication.

Community
Advanced
team-telnyxteam-telnyx
3

telnyx-oauth-java

Implement OAuth 2.0 authentication flows with Java SDK examples for the Telnyx API.

Official
Intermediate