Support Skills authorization without cross-package dependencies
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- csharp
- Área
- api, authentication, backend
Línea de trabajo
Start by reading the Core hosting primitive-filter composition and the existing AddAuthorizationFilters policy evaluator, then trace how Skills composes skills/list and skills/get handlers. The issue requires a shared hook that preserves existing authorization checkpoints, request services, and Tasks dispatch order while avoiding package dependency changes. Done means the acceptance criteria pass, including Native AOT compatibility and no new package dependency.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem
The registered-Skills/typed-handler design associated with #1863 should participate in AddAuthorizationFilters. Authorizing the file resources alone does not protect the frontmatter and manifests exposed by skills/list and skills/get. Wrapping the optional custom Skills handlers is insufficient: registered entries augment the list afterward, and matched registered gets take precedence over the fallback.
Applications should be able to use WithSkills(...) plus AddAuthorizationFilters() with their existing ASP.NET authorization services, without a separate integration registration or package. ModelContextProtocol.AspNetCore must not reference Skills, and Skills must not acquire an ASP.NET authorization dependency.
Recommended approach
Add a small, experimental, policy-neutral primitive-filter seam in Core/hosting over IMcpServerPrimitive and its server-local metadata. It needs a typed invocation hook around the complete composed handler after matching, plus a listing-visibility hook for entries mapped to registered primitives. A McpServerPrimitiveFilter-style contract is illustrative; this does not require a new catalog abstraction or a large generic framework.
AddAuthorizationFilters registers an adapter that reuses its existing policy evaluator. Skills owns the protocol-specific matching and list projection and consumes the shared hook automatically. Keep the existing tool/prompt/resource typed adapters at their current checkpoints rather than replacing them with a single outer filter: intervening filters can change the principal or matched primitive, and tool authorization must still precede Tasks dispatch.
Expected behavior and acceptance criteria
WithSkillsandAddAuthorizationFilterswork in either registration order, with no additional application integration step or cross-package dependency.- Protected registered entries are omitted from the complete composed listing. Registered gets are matched and authorized before dispatch, including URI-equivalent requests; denial never falls through to the custom handler. Authorized direct get/read does not depend on listing membership.
- Reuse the existing
IAuthorizeData, explicitAuthorizationPolicy,IAuthorizationRequirementData, andIAllowAnonymousbehavior. Unprotected/anonymous entries remain usable; missing authorization services or filters produce actionable local diagnostics rather than silently exposing protected entries. - Preserve repeated authorization checkpoints around changes to the user or matched primitive, existing typed-filter order, and denial before task creation.
- Resolve authorization services from
context.Servicesand usecontext.User. Reuse stateless HTTP'sHttpContext.RequestServicesand existing MCP request scopes/disposal; do not manufacture scopes or capture request services in shared filters. - Preserve Skills snapshots, validation, initial-null-cursor augmentation, registered-get precedence, conservative get defaults, protocol-version handling, and source-generated/Native AOT compatibility.
Boundaries and open decision
Custom database entries without registered primitive metadata remain application-owned: authorize before pagination and cursor construction, and authorize direct get/read independently. A generic post-page filter cannot sanitize an arbitrary application cursor. Do not load a whole database source or mutate shared registrations per caller to compensate.
Skill files remain ordinary resources with separately applied corresponding policies, especially when files are shared. Do not implicitly copy/merge skill metadata onto files or add automatic file revocation when a skill is removed.
The prototype preserves handler-supplied cache hints. Caller-dependent results must not be reused through public caching; decide whether authorization filtering should constrain/reject public hints or leave that enforcement with the application.
A local-only prototype exercised composed Skills list/get, stateless HTTP service identity and async disposal, policy/guard parity, repeated checkpoints, and pre-Tasks authorization, and built and ran under Native AOT without changing the package dependency graph. The recommendation is the small shared seam, not shipping the prototype verbatim. Related: #1941 for request-service integration and #1704 for broader extension-handler composition.
[!NOTE]
This issue was generated by GitHub Copilot from a local prototype at the maintainer's request.
- Lenguaje dominante
- C#
- Estrellas
- 4.6k
- Forks
- 849
- Merge medio
- 1 d 16 h
- PR fusionados (30 d)
- 24
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de modelcontextprotocol/csharp-sdk
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
modelcontextprotocol/csharp-sdk#2031 ·
Los mantenedores suelen responder en 1 día
-
Static resources whose URIs differ only in the fragment or user info collapse into onePosiblemente ocupada @halter73 la tomó hace 9 días. AbiertoP2
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
modelcontextprotocol/csharp-sdk#1970 · 4 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
POST /mcp with a missing or unparseable Content-Type returns HTTP 500 instead of a 4xxPosiblemente ocupada @halter73 la tomó hace 9 días. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
modelcontextprotocol/csharp-sdk#1966 · 5 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Reserved URI-template expansion throws for supplementary Unicode charactersPosiblemente ocupada @tarekgh la tomó hace 2 días. AbiertoP3
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
modelcontextprotocol/csharp-sdk#1913 · 1 comentario · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
ClaimsPrincipal parameter injection sample requestPosiblemente ocupada @utsavjain2809 la tomó hace 48 días. Abiertohelp wanted P3
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
modelcontextprotocol/csharp-sdk#1899 ·
Los mantenedores suelen responder en 1 día
Todos los issues de modelcontextprotocol/csharp-sdk
Issues similares
-
account bug effort:S P2
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
nightscout/nocturne#3745 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
grate-devs/grate#969 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
jsboige/CoursIA#27768 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 63/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
martin-stromberg/FinanceManager#562 ·
Los mantenedores suelen responder en 1 día