# Skill: Configure OAuth 2.0 Authorization Server Metadata (RFC 8414)

> **Standard:** RFC 8414
> **Category:** PROTOCOL_DISCOVERY
> **Classification:** SPECIFICATION_AND_GUIDE
> **Author:** TinyCTO Architecture Guild (https://tinycto.tv)

## Overview
Expose RFC 8414 metadata at /.well-known/oauth-authorization-server declaring token endpoints, grant types, and agent_auth extensions.

## Learning Objectives
1. Publish /.well-known/oauth-authorization-server with issuer, token_endpoint, and jwks_uri.
2. Include agent_auth extensions for automated agent registration.
3. Advertise supported OAuth scopes and response types.

## Prerequisites
- OAuth authorization server or NextAuth/Auth.js configuration

## Implementation & Execution Guide

### Step 1: Publish RFC 8414 Metadata
Return structured JSON with agent_auth capabilities.

```http
{
  "issuer": "https://tinycto.tv",
  "authorization_endpoint": "https://tinycto.tv/api/auth/signin",
  "token_endpoint": "https://tinycto.tv/api/auth/session",
  "agent_auth": {
    "register_uri": "https://tinycto.tv/auth.md",
    "identity_types_supported": ["anonymous", "identity_assertion"]
  }
}
```

## Architectural Takeaway
RFC 8414 enables autonomous agents to dynamically negotiate OAuth tokens without human credential copying.