Skip to content

RFC8414 metadata locations - #32

Merged
aaronpk merged 2 commits into
mainfrom
rfc8414-metadata-locations
Sep 20, 2026
Merged

aaronpk merged 2 commits into
mainfrom
rfc8414-metadata-locations

Conversation

@aaronpk

@aaronpk aaronpk commented Sep 20, 2026

Copy link
Copy Markdown
Member

No description provided.

…n issuer

IndieAuth requires the issuer to be a prefix of the metadata URL. RFC 8414,
which the next IndieAuth draft follows, places the document at
https://host/.well-known/oauth-authorization-server followed by the issuer's
path, so an issuer with a path is never a prefix of it and servers such as
IndieKey.id were refused with "Issuer in metadata endpoint is not valid".

_isIssuerValid() now accepts either form: the prefix rule as before, or the
metadata URL equal to one of the issuer's RFC 8414 locations (the
oauth-authorization-server and openid-configuration document names). The
https, query and fragment checks are unchanged. Client::wellKnownMetadataURLs()
builds the locations and is public for clients that want to explain a refusal.
…n issuer

IndieAuth requires the issuer to be a prefix of the metadata URL. RFC 8414,
which the next IndieAuth draft follows, places the document at
https://host/.well-known/oauth-authorization-server followed by the issuer's
path, so an issuer with a path is never a prefix of it and servers such as
IndieKey.id were refused with "Issuer in metadata endpoint is not valid".

_isIssuerValid() now accepts either form: the prefix rule as before, or the
metadata URL equal to the issuer's RFC 8414 location. The https, query and
fragment checks are unchanged. OpenID Connect discovery documents are not
accepted; they follow their own rules and are not IndieAuth metadata.
Client::wellKnownMetadataURL() builds the location and is public for clients
that want to explain a refusal.
@aaronpk
aaronpk merged commit b892510 into main Sep 20, 2026
8 checks passed
@aaronpk
aaronpk deleted the rfc8414-metadata-locations branch September 20, 2026 11:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant