solid-oidc
solid-oidc copied to clipboard
solid
The repository for the Solid OIDC authentication specification.
Match diagrams in /oidc and /oidc-primer , including consistent use of terminology/description, direction of requests/responses. The diagram with more details (/oidc-primer ?) should extend the other (/oidc ?).
Consider matching code examples, e.g., currently /oidc uses https://oidc.example and /oidc-primer uses https://secureauth.example . Alternatively, make obvious extensions, e.g., currently, /oidc uses https://app.example/id and /oidc-primer uses https://decentphtos.example/webid#this . /oidc-primer could...
In the [recently submitted](https://github.com/solid/specification/pull/386) iteration of the Solid-OIDC specfication there are references made to an Authorization Server that SHOULD implement a [UMA 2.0 Grant for OAuth 2.0 Authorization](https://docs.kantarainitiative.org/uma/wg/rec-oauth-uma-grant-2.0.html) (UMA). Specifically:...
In #request-flow-step-15: >Given all went well, the RS should return the requested content. Consider using more accurate language from RFC 7230, 7231.
In #request-flow-step-14: Update to use valid HTTP headers and message.
In #request-flow-step-8: >`GET https://alice.coolpod.example/profile/card#me` Should be `GET https://alice.coolpod.example/profile/card` Probably best to change values like `https://localhost:8443/profile/card#me` to `https://alice.coolpod.example/profile/card#me`.
In #request-flow-step-7: >header jwk `header.jwk`? ..but maybe express it differently instead of code.
In #request-flow-step-4: Go full out in a Primer example including required HTTP headers and values. Don't truncate values.
In #request-flow-step-2: Mention that the request target is the value of `as_uri` concatenated with "`.well-known/uma2-configuration`"