%20rotate(90)%20scale(70)'%20gradientUnits='userSpaceOnUse'%3e%3cstop%20stop-color='%23312e81'%20stop-opacity='.72'/%3e%3cstop%20offset='1'%20stop-color='%2309090b'%20stop-opacity='0'/%3e%3c/radialGradient%3e%3cfilter%20id='glow'%20x='-45%25'%20y='-45%25'%20width='190%25'%20height='190%25'%3e%3cfeGaussianBlur%20stdDeviation='4'%20result='blur'/%3e%3cfeMerge%3e%3cfeMergeNode%20in='blur'/%3e%3cfeMergeNode%20in='SourceGraphic'/%3e%3c/feMerge%3e%3c/filter%3e%3c/defs%3e%3cpath%20d='M80%208%20139%2042v76l-59%2034-59-34V42Z'%20fill='%2309090b'%20stroke='url(%23frame)'%20stroke-width='4'%20stroke-linejoin='round'/%3e%3cpath%20d='M80%2015%20132%2045v70l-52%2030-52-30V45Z'%20fill='url(%23core)'/%3e%3cg%20fill='none'%20stroke='url(%23signal)'%20stroke-linecap='round'%20stroke-linejoin='round'%3e%3cpath%20d='M38%2055h18l10%2011'%20stroke-width='5'/%3e%3cpath%20d='M38%20105h18l10-11'%20stroke-width='5'/%3e%3cpath%20d='M94%2066l10-11h18'%20stroke-width='5'/%3e%3cpath%20d='M94%2094l10%2011h18'%20stroke-width='5'/%3e%3cpath%20d='M58%2080h42'%20stroke-width='7'/%3e%3c/g%3e%3cg%20fill='%2309090b'%20stroke='url(%23frame)'%20stroke-width='4'%3e%3ccircle%20cx='35'%20cy='55'%20r='7'/%3e%3ccircle%20cx='35'%20cy='105'%20r='7'/%3e%3ccircle%20cx='125'%20cy='55'%20r='7'/%3e%3ccircle%20cx='125'%20cy='105'%20r='7'/%3e%3c/g%3e%3cpath%20d='M92%2054H72c-8%200-14%206-14%2014v24c0%208%206%2014%2014%2014h20'%20fill='none'%20stroke='%23fff'%20stroke-width='8'%20stroke-linecap='round'%20filter='url(%23glow)'/%3e%3ccircle%20cx='80'%20cy='80'%20r='8'%20fill='%23fff'%20filter='url(%23glow)'/%3e%3c/svg%3e)
Authorization configuration
Resource metadata, token verification, scopes, and optional authorization profiles.
Extension options
| Option | Meaning |
|---|---|
resource | Canonical HTTPS MCP endpoint URI; localhost HTTP is allowed for development. |
authorizationServers | Trusted authorization-server issuer URLs. |
verifyAccessToken | Async verifier returning a normalized McpAuthPrincipal. |
scopes | Base scopes required for every MCP request and advertised by default. |
metadata | RFC 9728 protected-resource metadata fields. |
rootMetadataAlias | Explicitly expose the origin-root well-known alias. |
profiles | Advertise Client Credentials or Enterprise-Managed Authorization. |
clockSkewSeconds | Non-negative expiry tolerance. |
Use authorization.requiredScopes on tools, resources, prompts, or route MCP metadata. Unauthorized
primitives are removed from list results and checked again during call/read/get. Missing or invalid
credentials return 401; insufficient scope returns 403 with authoritative scope and
resource_metadata parameters.
The original Authorization header is preserved for internal Elysia route invocation so existing
application guards remain authoritative. Explicit MCP handlers should use the normalized
authorization context instead of rereading the raw header.
Client Credentials
Enable profiles.clientCredentials only when the external authorization server preregisters
confidential clients, supports client_credentials, binds tokens to the canonical resource, and
applies least privilege and credential rotation. The profile changes discovery; it does not infer
permissions from grant provenance.
Enterprise-Managed Authorization
Enable profiles.enterpriseManaged only when the external authorization server implements the
enterprise profile, advertises ID-JAG support, and exchanges an enterprise assertion through the
required JWT bearer grant. The MCP endpoint accepts only the resulting OAuth access token. It must
not accept SAML assertions, ID tokens, or ID-JAGs directly.
The adapter does not host token endpoints, registration, login or consent pages, enterprise SSO, ID-JAG exchange, JWKS, token refresh/storage, or IdP provisioning.