Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Identity servers public_key(s) base64 format needs to be clarified #2060

Open
zecakeh opened this issue Jan 21, 2025 · 0 comments
Open

Identity servers public_key(s) base64 format needs to be clarified #2060

zecakeh opened this issue Jan 21, 2025 · 0 comments
Labels
clarification An area where the expected behaviour is understood, but the spec could do with being more explicit

Comments

@zecakeh
Copy link
Contributor

zecakeh commented Jan 21, 2025

Link to problem area:

C-S API:

IS API:

Issue

The documentation of the public_key and public_keys fields issued by identity servers mention unpadded base64, the one from the IS API even linking to the definition in the appendices using standard base64.

However Sydent sends the long-term public key encoded using standard base64 and the ephemeral public key encoded as URL-safe base64 (as can be seen in matrix-org/sydent#10). So this documentation should be clarified to say that both standard and URL-safe base64 can be expected for those fields.

Related: #838.

@zecakeh zecakeh added the clarification An area where the expected behaviour is understood, but the spec could do with being more explicit label Jan 21, 2025
@zecakeh zecakeh changed the title public_key(s) base64 format needs to be clarified Identity servers public_key(s) base64 format needs to be clarified Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
Projects
None yet
Development

No branches or pull requests

1 participant