On Tue, 2018-04-24 at 12:13 +0300, Ioan Eugen Stan wrote: > Hello Hasini, Robert, > > I'm also going to work in this field - working to integrate Keycloak > OpenId Connect with Sling. I should start on it next month.
That's great news as well :-) > > I will share more feedback as I am through the process and hope to > collaborate. Your input would be very much welcomed in this GSOC project and with Apache Sling overall. My only ask would be to keep all communications on the dev list, for everyone's (current and future) benefit. Thanks, Robert > > Good luck with you project. > > @Hasini: I can help with regard to the Oauth / Oidc protocols and > architecture so if you ever find yourself struggling, reach out and > I'll > find some time. > > /Eugen > > > On 24.04.2018 12:06, Robert Munteanu wrote: > > Hi Hasini, > > > > On Tue, 2018-04-24 at 00:51 +0530, Hasini Witharana wrote: > > > Hi Robert, > > > > > > I have been selected to the $subject GSoC project. I am really > > > looking > > > forward to work with you. > > > > Congratulations, this is great news! > > > > > The below [1] is the proposal for the project. There are two > > > approaches for > > > the OIDC implementation. > > > > > > > > > 1. Use Apache Oltu OAuth2.0 implementation as a dependency and > > > build > > > OIDC platform on top of it. > > > 2. Build OAuth2.0 and OIDC implementations from the scratch > > > > > > > > > Since the time is limited, I think first approach is more > > > suitable. I > > > would really like to have some advises from you for the initial > > > starting of > > > the project and community bounding. Thank you very much for > > > giving > > > me this > > > opportunity. > > > > Absolutely, I agree that option 1 is the way to go. We are not in > > the > > business of developing and maintaining OAuth implementations :-) > > > > I would suggest that first you get yourself familiar with Sling, > > following the documentation at [2]. For your specific scenario I > > guess > > that: > > > > 1. Running Sling > > 2. Deploying a new OSGi bundle in Sling > > 3. Updating the initial content from Sling > > > > would be the way to go and would cover 99% of the work that you > > need to > > do in Sling. > > > > Then it would be good to address the original comments on your > > proposal > > that I posted at [3] and adjust the plan accordingly. > > > > Other than that, please use [email protected] for any queries > > that > > you might have - it's our main communication channel and all the > > right > > people are here. > > > > Welcome! > > > > Robert > > > > > > > > [1] - https://docs.google.com/document/d/1ki_mv_ > > > ngtMFsP2cqZkVfZfAYLAYle6M5Srs0WsgHXEs/edit?usp=sharing > > > > > > > [2]: https://sling.apache.org/documentation/getting-started.html > > [3]: https://lists.apache.org/thread.html/34ed2da7489b285fe3b2e4da6 > > dbe8219c94a7f5353d156fba4538824@%3Cdev.sling.apache.org%3E > >
