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

Provide registry support address to library registry upon registration #913

Open
leonardr opened this issue Mar 29, 2018 · 1 comment
Open

Comments

@leonardr
Copy link
Contributor

The library registry can grab a library's patron support email and DMCA Designated Agent email from the library's public Authentication For OPDS document. But the point of contact for problems with the SimplyE ecosystem itself doesn't need to be public. This person is probably some random library or contractor employee and the only party that needs to know their email address is the library registry itself.

Upon registration, the library should provide this information either directly to the library registry, or by encrypting it with its temporary secret key and sticking the encrypted value in the temporary A4OPDS document retrieved by the registry.

@aslagle
Copy link
Collaborator

aslagle commented Mar 29, 2018

For the private email address, the library registry should create a public key and stick it in its main catalog document along with its register URL. The circ manager should retrieve that public key and use it to encrypt the email address, then either put the encrypted email in the register request or temporarily put it in the auth document. This is better than using the secret key generated on registration because the registry can return an error if the email is missing, rather than having to do a separate step after the library is already registered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants