Closed acoburn closed 3 years ago
@acoburn I'm not fully sure I understand the issue. OIDC is built explicitly on top of OAuth2, it's just a profile of oauth2, specifically. What do you have in mind, in terms of alignment?
@dmitrizagidulin I would say that this issue is primarily about naming. My understanding of https://github.com/solid/authentication-panel/issues/21 was that the proposal was closer to OAuth2 than OIDC (and so the name WebID-OIDC could be viewed as a bit of a misnomer). However, if you feel that the OIDC part of the name "WebID-OIDC" is appropriate, then feel free to mark this issue as resolved.
@acoburn please re-open if you see need to follow up on this issuer.
Some of the interactions defined in the WebID-OIDC protocol make it more similar to OAuth2 than a classic OIDC interaction. It may make sense to generalize the protocol, aligning it with OAuth2. If so, it should be decided which formalisms from OIDC would be carried over (e.g. endpoint discovery via
/.well-known/openid-configuration
)