Authorization Server Discovery changedspecification/draft/basic/authorization/authorization-server-discovery
Nearest release: v2.1.305, published under an hour before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 20 Oct 2026 20:02 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 22 Oct 2026 20:37 UTC.
Upstream edited
Recorded here
Lines+2added
Lines−2removed
From line
27
where the diff opens
First seen
26 Aug 2026
this site's first read of the page
Recorded edits3to this page, all time
The whole hunk
from line 27, old and new numbered
/
from line 27
2727separate registration state (client credentials, tokens) per authorization server and
2828**MUST NOT** assume that credentials valid for one authorization server will be accepted by
2929another. See
30[Authorization Server Binding](/specification/draft/basic/authorization/client-registration#authorization-server-binding)
30[Authorization Server Binding](/specification/draft/basic/authorization/client-registration.md#authorization-server-binding)
3131for the requirements on associating client credentials with the authorization server that issued them.
3232
3333## Protected Resource Metadata Discovery Requirements
from line 46
4646
4747Servers can also include a `scope` parameter in the `WWW-Authenticate` challenge to indicate the
4848scopes required for accessing the resource; the scope semantics and the associated client behavior
49are defined in the [Scope Selection Strategy](/specification/draft/basic/authorization#scope-selection-strategy) section.
49are defined in the [Scope Selection Strategy](/specification/draft/basic/authorization.md#scope-selection-strategy) section.
5050
5151## Authorization Server Metadata Discovery
5252
No line in this hunk matches that.