You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If your OPDS server needs to receive cryptographically signed messages (e.g. to set up shared secrets with other servers), you can publish your public key in the authentication document.
It might make more sense to standardize the OPDS Directory Registration Protocol and define public_key as an extension to Authentication For OPDS in that spec.
The text was updated successfully, but these errors were encountered:
This is one of a series of proposals for taking NYPL's extensions to Authentication For OPDS and adding them to the core document.
https://github.com/NYPL-Simplified/Simplified/wiki/Authentication-For-OPDS-Extensions#public-key
If your OPDS server needs to receive cryptographically signed messages (e.g. to set up shared secrets with other servers), you can publish your public key in the authentication document.
We've found this very useful for setting up integrations between servers. See the OPDS Directory Registration Protocol for an example.
It might make more sense to standardize the OPDS Directory Registration Protocol and define
public_key
as an extension to Authentication For OPDS in that spec.The text was updated successfully, but these errors were encountered: