Open csarven opened 3 years ago
Maybe we can just include this table in README.md ?
I think the main difference is that ISCAJ keeps its credentials inside a closure, which makes it more secure in some situations, and solid-auth-fetcher exposes them to the calling code, which makes it more versatile in other situations.
There are now client implementations in Perl and Rust so they might belong here.
I'm a bit unclear what should be included on this list. Should it have low-level stuff like oidc-op? How about higher-level libraries which make use of the stack (e.g. Inrupt's solid-client-authn-* or solid-node-client)?
The list should include libraries/applications that implement or intend to implement the specifications defined by this panel. At present, that includes Solid-OIDC.
During call we noticed that we need conformance section which will prescribe which roles (IdP, RS, client) have to implement what.
Solid OIDC Conformance Classes: https://github.com/solid/authentication-panel/issues/133
It would be nice if a) we also had data for NSS and CSS and the other implementations b) the notes mentioned whether the OIDC flow is supported both in the browser and out of the browser as several implementations have supported the first without supporting the second c) there were a date showing how recent the information is (or more likely isn't).
I updated table above adding sai-authentication-java developed by @justinwb
I'm going to move that table into README so that everyone can make PR to update it.
We can document existing, ongoing, or planned implementations. It will serve to advance this panel's specs. This issue is not intended to be the canonical location for implementations or to replace implementation reports made against test suite.
Update table criteria as needed.
Solid-OIDC implementations
webid
claim and DPoP. Supports client identifiers. Can be used with any existing OIDC-conforming identity provider.