Skip to content

clarify WebID-TLS #140

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

Closed
wants to merge 1 commit into from
Closed

clarify WebID-TLS #140

wants to merge 1 commit into from

Conversation

elf-pavlik
Copy link
Member

During today's authentication call we discussed WebID-TLS with @dmitrizagidulin and @bblfish. We thought that mentioning it in non-normative section will suffice.
I also think that solid project doesn't need to take any responsibility for WebID-TLS spec itself since it doesn't seem to have any more a special role in solid ecosystem.

I keep in mind #114 but for now we can just use WebID-OIDC and rename everything once we resolve that naming issue.

@csarven
Copy link
Member

csarven commented Jan 20, 2020

Can you share the implementation reports indicating where WebID-TLS "doesn't seem to have any more a special role in solid ecosystem"?

I would've expected some reasonable documentation, data, minutes etc backing up the case for downplaying WebID-TLS to the extent you propose. I don't see it in this repo or in the authn-panel repo. Perhaps I missed? This is not to imply that that is not a preferable direction to take in the spec, but considering where Solid is coming from - essentially why we had WebID-TLS to begin with - I think it'd be appropriate to capture the whys, give interested parties a chance to respond... before making the call.

@bblfish
Copy link
Contributor

bblfish commented Jan 21, 2020

Part of what the WebID group could produce is a report on what the problems with the protocol
are, which could be used to inform further work. It would probably be a good idea to first work this out.

One issue has been for example client side renegotiation in HTTP2.0.
But there seems to be progress on that front.
https://greenbytes.de/tech/webdav/draft-ietf-httpbis-http2-secondary-certs-05.html

The advantage of WebID-TLS is that it is integrated into the browser. The disadvantage is that it is.

The dual of this is that anything we invent eg WebID over HTTP-Signatures is not integrated into the browser, and so is flexible, but then requires building everything related such as a keychain. Note that HTTP-Signatures is now being considered for starndardisation by the HTTP-WG.

@elf-pavlik
Copy link
Member Author

Please see:

Removed references to TLS as primary auth method #171
Removed references to TLS that imply it is the primary form of authenication #26

I think solid spec might go with MAY and just reference https://www.w3.org/2005/Incubator/webid/spec/tls/
Main problem I can see with that comes from lack of active work on WebID-TLS. I don't know if anyone actively participating in solid would want to adopt it as work item. Given amount of work required to agree on one common mechanism combining authentication and authorization (at least part where user can delegate subset of one's own access to specific client application) I think we better focus on that and don't even try to take responsibility of addressing issues related to WebID-TLS.

If we decide to go with MAY I think we should document somewhere, maybe something like charter in process repo, who would want to take responsibility of resolving issues related to WebID-TLS and set clear scope for those responsibilities.

Myself I rather focus on MUST mechanism and until we have this one stable don't divide effort on any of the possible MAYs.

@elf-pavlik
Copy link
Member Author

elf-pavlik commented Apr 21, 2020

Myself I rather focus on MUST mechanism and until we have this one stable don't divide effort on any of the possible MAYs.

I would like to ask if anyone plans to prioritize any WebID-TLS related work over all the other work needed. I really think that what this PR proposes can help us not to get distracted by WebID-TLS, by simply acknowledging its historical role in Solid and warning that one can not rely on broad support for WebID-TLS in Solid ecosystem.

@justinwb
Copy link
Member

justinwb commented May 6, 2020

@elf-pavlik does this pull request have the support of the other members of the authentication panel? If so, and we could see endorsement from panel members, that would be helpful.

Copy link
Member

@dmitrizagidulin dmitrizagidulin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 from me on this PR.

Copy link
Member

@acoburn acoburn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@ewingson
Copy link
Member

ewingson commented May 7, 2020

+1, although having TLS-key as alternative login-method could go with MAY seems to be good...

@justinwb
Copy link
Member

justinwb commented May 8, 2020

@elf-pavlik and others - there seems to be general agreement on the substance of this pull from editors, authentication panel members, and prior threads. There's a large refactoring of this Solid ecosystem document in progress to extract the core solid client/server protocol into it's own document. Authentication modes will be included, and we anticipate that the substance of this pull will be covered when that is done. We can leave this pull open in the meantime, but it's likely that different text will be needed to address the substance of your submission in that new format.

@csarven
Copy link
Member

csarven commented Nov 9, 2020

Reflected in 43a0cc7 . Thanks!

@elf-pavlik
Copy link
Member Author

I still see webid-tls directory in the root.

@csarven
Copy link
Member

csarven commented Nov 9, 2020

That wasn't particularly in use. Removed now. Nighty night.

@elf-pavlik elf-pavlik deleted the webid-tls branch November 9, 2020 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

7 participants