Developing login plugin

[Joseph Fischetti]

Thanks for the quick reply Scott,
Looks like the Duo documentation references CanonicalUsernameLookupStrategy
Is CanonicalPrincipalNameLookupStrategy different, or is that what you're referring to?

Something like this?
usernameLookupStrategy = new CanonicalUsernameLookupStrategy();
username = usernameLookupStrategy.apply(profileRequestContext);

Joe

Joe Fischetti
Linux System Administrator
Marist College

E-mail: joseph.fischetti at marist.edu

-----Original Message-----
From: dev <dev-bounces at shibboleth.net> On Behalf Of Cantor, Scott
Sent: Tuesday, November 19, 2019 10:12 AM
To: Shib Dev <dev at shibboleth.net>
Subject: Re: Developing login plugin

[EXTERNAL EMAIL]

On 11/19/19, 9:11 AM, "dev on behalf of Joseph Fischetti" <dev-bounces at shibboleth.net on behalf of Joseph.Fischetti at marist.edu> wrote:

> My question revolves around calling the attribute resolver, I’ve 
> included some code below.  I currently have it working, but I want to make sure it’s working correctly based on the way the IdP is plumbed.

Mostly. I would stuff the contexts under the AuthenticationContext to keep them safely isolated, but as long as it's cleaning itself up, that's not a big deal.

> High level:  The flow is called and it looks at the c14n principal name from the profileContext that’s passed to it.

That won't work for pre-existing sessions, use the CanonicalPrincipalNameLookupStrategy function as a default to acquire the value, that handles both cases. That's what Duo uses.

-- Scott


--
To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5597 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/dev/attachments/20191119/9852678e/attachment.p7s>