-
Notifications
You must be signed in to change notification settings - Fork 30
Describe session key sharing mechanism #171
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
base: push-mpvqoqvpkvlm
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not fully understanding this at the moment, so not marking as approved yet. Addressing some of the comments may help.
spec.bs
Outdated
1. If |algorithm list| is empty, return null. | ||
1. Let |unshared key| be a key pair created for |algorithm list|. | ||
1. If any of |params|["provider_key"], |params|["provider_id"], or | ||
|params|["provider_site"] exists: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want provider_site or provider_origin? We use provider_origin in the section "Secure-Session-Registration
HTTP header field"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah this is inconsistent because I went back and forth and seems like I didn't quite settle on either. I was struggling with two things:
- How do we lookup the session given the
origin
andsession id
. - How do we get the well-known URL from
origin
.
I think we want to have that field be a URL, from which we can easily derive the site (as the registrable domain), expected origin, and well-known URL. Therefore I've renamed it "provider_url". Let me know what you think.
No description provided.