-
Notifications
You must be signed in to change notification settings - Fork 379
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
Use Case: storing WebCrypto generated public key for an app #47
Comments
As this is bound to take a lot of iterations to work out correctly I opened a wiki page so that edits can be placed together: |
Please state the objective. And when you say "app" do you mean always "web app with a given origin"? Do you mean here the public key of a given origin? If so, cac one use the TLS cert public key for that origin? |
My use case was to store the WebCrypto generated public key on the server to give apps from that origin access to the apps' folder where the user could store her preferences. This was in order to finish my implementation of HTTP-Signature documented in issue-52 of solid-spec After discussion on gitter I realised that acl:origin would solve one important part of this problem, and also that it would allow this to work with WebID-TLS too! So that is really neat, and opens a few possibilities I had not thought of. |
There is a pull request out now for this, so it's easier to comment on the details |
I have continued editing this on my wiki, as it is easier to think that way, and as my PR is taking time to get reviewed. I have now looked at four protocol options:
|
You can find more conversation on this subject here https://forum.solidproject.org/t/use-case-storing-webcrypto-generated-public-key-for-an-app/386 |
I have a simple foaf-browser application that can produce a public key using Http-Signature ((but this issue would be the same were I to use webid-rsa)). I can't really test it without saving that key. So I need a space for the application to save that key which can then identify the application when used by that browser.
The text was updated successfully, but these errors were encountered: