Skip to content

Implement SEP-991: URL-based Client Registration (OAuth Client ID Metadata) #1538

Description

@felixweinberger

This is a tracking issue for implementation of SEP-991.

Summary

This SEP adopts OAuth Client ID Metadata Documents as an alternative client registration mechanism, allowing clients to use HTTPS URLs as client identifiers where the URL points to a JSON document containing client metadata. The Python SDK needs to implement support for accepting HTTPS URLs as client_id values, fetching and validating client metadata documents from those URLs, and enabling servers to implement flexible trust policies for URL-based client registration without requiring pre-coordination.

Related Issues & PRs

  • Implementation PRs: n/a
  • Related PRs: n/a
  • Related Issues: n/a

Activity

  1. moved this from Ready to In progress in 2025-11-25 Implementationon Nov 20, 2025
  2. brendanator commented on Dec 18, 2025

    @brendanator

    I am looking to use CIMD on the server side and found this issue.

    It appears that #1652 only implements it on the client side?

    Is there another issue I've missed that implements this on the server side, or should this issue be reopened?

    cc @pcarleton

  3. maxisbey commented on Dec 18, 2025

    @maxisbey
    Contributor

    You're correct - #1652 only implemented client-side CIMD support. Server-side support is tracked in #1801.

    AI Disclaimer

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

Metadata

Metadata

Assignees

Labels

authIssues and PRs related to Authentication / OAuthenhancementRequest for a new feature that's not currently supported

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions