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.

Sign up for GitHub

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

Jump to bottom

Security using JWS #22

Open
mattvarghese opened this issue Oct 27, 2020 · 1 comment
Open

Security using JWS #22

mattvarghese opened this issue Oct 27, 2020 · 1 comment

Comments

@mattvarghese
Copy link

Can we require that the message has some sort of signature using JWS?

Additionally, can we recommend that whenever the Application has a web server component, signature is created on the web server, so that the signing credential is not available in JavaScript on the App's client side?

@isaacvetter , @jmandel : FYI - I'm writing this issue up. Let me know what thoughts you folks have.
@jmandel
Copy link
Contributor

jmandel commented Oct 27, 2020

Given where we are in the v1 ballot process, would look at this as a post-v1 request. For v1, messages are authenticated by origin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jmandel @mattvarghese