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

Update readme WebID_TLS Section #221

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -183,10 +183,9 @@ identity provider, such as (2018/2) [solid.community](https://solid.community/),

#### WebID_TLS

A WebID profile from one of the Solid-compliant [identity providers](https://solid.github.io/solid-idps/), such as [databox.me](https://databox.me/),
WebID-TLS currently only works in Firefox at the moment (Oct 2018)
Copy link
Contributor

Choose a reason for hiding this comment

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

@perploug Yeah I noticed that Chrome didn't give me the popup anymore lately. Would that still be possible behind a flag?

@melvincarvalho @timbl @kidehen You are client certificate users, what browser(s) work(s) for you?

Copy link

Choose a reason for hiding this comment

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

@RubenVerborgh ,

There are no browser specific issues that impede my use of WebID-TLS. It just works :)

/cc @melvincarvalho @timbl

Copy link
Contributor

Choose a reason for hiding this comment

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

@perploug But it didn't work for you in other browsers?

Copy link
Contributor

Choose a reason for hiding this comment

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

I use TLS certs to log in to with chrome, and this still works for me.

Copy link
Member

Choose a reason for hiding this comment

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

I use WebID-TLS on chrome and firefox. No issues here either.

Copy link
Author

Choose a reason for hiding this comment

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

I don't use the WebId-TLS option as there is it apparently not supported on the solid.community pods (I seem to recall a comment that this option was being deprecated)

The reason the firefox comment is in there is because it was there before, I just moved to the beginning of the sentence - but based on your comments it seems it can be removed all together - will update the PR

And to confirm I do get prompted for a certificates on Osx Chrome and firefox.

Copy link
Member

Choose a reason for hiding this comment

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

WebID-TLS has always been the primary login system for solid. It is not deprecated. The plan is to support it on solid.community in future. But code needs to be there first.

Copy link
Author

Choose a reason for hiding this comment

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

@melvincarvalho okey - that clears things up a bit - is there any provider which supports WebID-TLS? otherwise I think that should be part of the documentation that users cannot currently expect this functionality

Copy link
Member

Choose a reason for hiding this comment

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

databox is the provider that supports WebID-TLS, but it doesnt yet support WebID-OIDC

There is in theory a way where you wrap WebID-TLS inside WebID-OIDC, which also works today, or should work today.

However, by nature the TLS is more secure because it involves two parties, and OIDC is less secure because it requires a trusted third party. On the other hand, the trusted third party has a good network effect today, due to the nature of large email and identity providers.

Over time, it would be good for both protocols to be supported. That was the design aim, but we are not there yet.


With WebID-TLS, you will need to make a WebID browser certificate from the above profile (this is usually created
when you sign up for a WebID profile account, but it only works on Firefox at the moment (2018)).
To use WebID-TLS, you will need to make a WebID browser certificate from one of the Solid-compliant [identity providers](https://solid.github.io/solid-idps/) - this is usually created when you sign up for a WebID profile account.
perploug marked this conversation as resolved.
Show resolved Hide resolved

### Running a server

Expand Down