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

Upgrade to use authenticated web socket protocol #360

Open
timbl opened this issue Nov 5, 2020 · 3 comments
Open

Upgrade to use authenticated web socket protocol #360

timbl opened this issue Nov 5, 2020 · 3 comments

Comments

@timbl
Copy link
Contributor

timbl commented Nov 5, 2020

This needs to be done in conjunction with NSS being upgraded to allow (and check if sent) authentication information.

There is a question as to the extent that this should be negotiated between the parties or with time just required.

@timbl
Copy link
Contributor Author

timbl commented Nov 5, 2020

Here is the relevant issue in the spec and a possible alignment .

@michielbdejong
Copy link
Contributor

Sounds like inrupt/solid-client-authn-js#538 is now a WONT_FIX.
So I'll wait for a few more weeks to see what happens, and if it seems clear that Inrupt's client will not support it, then we can always just add our own code for it (but still use Inrupt's client as much as possible).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants