Hi all, In OpenID Connect flow there are three main parties.
1. End-User - Resource owner 2. OpenID Connect Provider - Authorization Server that is capable of authenticating the End-User and providing claims to a Relying Party about the Authentication event and the End-User 3. Relying Party - A client requiring End-User Authentication and Claims from an OpenID Connect Provider. When considering the OIDC flow, does sling act as an OpenID Connect provider or a relying party? Thank You. On Tue, Apr 24, 2018 at 5:36 PM, Bertrand Delacretaz <[email protected] > wrote: > On Tue, Apr 24, 2018 at 11:16 AM, Robert Munteanu <[email protected]> > wrote: > > ...My only ask would be to keep all communications on the dev list, for > > everyone's (current and future) benefit.... > > In the same vein I'd say all documentation should be on Apache Sling > "properties", we have: > > - The wiki at https://cwiki.apache.org/confluence/display/SLING/Index > that we usually use for drafts, brainstorming etc > - http://issues.apache.org/jira/browse/SLING which we use for all > coordination, not just bugs > - README etc in the modules themselves > > So for example we (at least I) much prefer having things at > cwiki.apache.org rather than Google Docs, as that belongs to the ASF > and especially is easier to discover. > > -Bertrand > -- *Hasini Witharana* Undergraduate | Department of Computer Science and Engineering University of Moratuwa Linkedin <https://www.linkedin.com/in/hasini-witharana-185785109/>
