Skip to content

feat(auth): complete auth coverage — clients access.check, Clients.new scope fields, Credentials.User.new stub #76

Description

@nycomp

Description

Smaller auth-service gaps from the 2026-10-04 client↔server delta sweep (campus weekly @ 74738e1). No consumer app needs these today — backlog.

  1. Clients.access.check() — GET /auth/v1/clients/<client_id>/access/check?vault=&permission= → {"vault": ..., "permission": <bool>}. The only access sub-route the client lacks (get/grant/revoke/update exist).
  2. Clients.new() scope/bridge fields — POST /auth/v1/clients/ also accepts allowed_scopes, upstream_scopes, token_bridge; new() drops them (update() has supported them since PR feat(auth): client update() accepts allowed_scopes/upstream_scopes/token_bridge #65).
  3. Credentials.User.new() stale stub — raises NotImplementedError("Method not expected to be called on API"), but the endpoint is live: POST /auth/v1/credentials/<provider>/<user_id> body {scopes, expires_in} → 201 (client_id comes from the auth context, not the body).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions