MPASSid-proxy OAuth (Facebook) and OIDC (Google) IdP AuthN Integration

Philip Smart Philip.Smart at jisc.ac.uk
Tue Nov 27 04:56:02 EST 2018


Hi Henri,

Thanks kindly for looking over it and giving feedback. 

Yes, I can see you have a valid use case without requiring the session layer, that makes sense. I was just looking at it from the perspective of a more standard Shib AuthN implementation - which as you say, was not its exact purpose. 

Thanks for pointing me at the other GitHub repository, I will take a look.

Phil


> On 27 Nov 2018, at 07:55, Henri Mikkonen <henri.mikkonen at csc.fi> wrote:
> 
> Hi Phil,
> 
> Thank you for very good analysis!
> 
> As you've probably noticed, even though the authors of the MPASSid code are the same with the GEANT OIDC -plugin (i.e. me and Janne), the approach is very much different. In the MPASSid case, we got funding from the Finnish Ministry of Education and Culture to develop an SSO solution with open source software. We chose to use Shibboleth as basis, but the main goal has clearly been the Finnish MPASSid proxy instance itself, instead of "a generic product". That explains for instance the attribute resolution parts being incompatible with SSO sessions: we only need one principal from social user module in the MPASSid use cases.
> 
> Anyway, in the future people should take the MPASSid modules from this GitHub organization: https://github.com/mpassid
> 
> It contains the same modules in their own repositories that use to exist under one big repository in the Digipalvelutehdas organization (which was mentioned in Phil's document). There are some package naming changes as the names were harmonized between the modules.
> 
> BR,
> Henri.
> 
> On 22/11/2018 15.10, Philip Smart wrote:
>> Hi All,
>> I have been trying out the MPASSid-proxy social user authentication extensions for the IdP.
>> Rather than adding the libraries to an already deployed IdP, I added the source as a dependency of the idp-parent. The idea being
>> to understand what it would mean to add the extension as a native IdP AuthN implementation.
>> It all looks pretty feasible, I have attached my workings. If anybody wants to take a look
>> and or has any comments, great. Janne and or Henri will now quite a bit about it already! but any comments welcome.
>> Phil
>> Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.
>> Jisc Services Limited is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under company number 2881024, VAT number GB 197 0632 86. The registered office is: One Castle Park, Tower Hill, Bristol BS2 0JA. T 0203 697 5800.
> -- 
> To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net



More information about the dev mailing list