dp.attribute.resolver.LDAP.returnAttributes idp v3.3.0
Lipscomb, Gary
glipscomb at csu.edu.au
Tue Nov 15 20:40:07 EST 2016
Hi Scott,
I removed the property from our build process, both in ldap.properties and attribute-resolver.xml thinking it was not required and that the upgraded v3.3.0 would return all attributes from LDAP as default. All I was picking up was just the memberOf attribute. This broke things. My misunderstanding of the release notes.
Regards
Gary
> -----Original Message-----
> From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor,
> Scott
> Sent: Wednesday, 16 November 2016 12:33
> To: Shib Users <users at shibboleth.net>
> Subject: Re: dp.attribute.resolver.LDAP.returnAttributes idp v3.3.0
>
> On 11/15/16, 8:25 PM, "users on behalf of Klingenstein, Nate" <users-
> bounces at shibboleth.net on behalf of nklingenstein at calstate.edu> wrote:
>
> > Specifically, if any property that is defined in Spring somewhere doesn't
> resolve to "something", your IdP is toast.
> > It doesn't even need to make sense, but it has to be there in some form.
>
> That was the reason it was removed, people were commenting it out and
> breaking things. Take out the property and you just choose whether to
> specify ReturnAttributes yourself, perfectly normal.
>
> > I haven't encountered this, but we haven't upgraded yet.
>
> There is no way the property removal can affect anybody upgrading. Neither
> the property files nor the resolver files would be touched.
>
> -- Scott
>
>
> --
> To unsubscribe from this list send an email to users-
> unsubscribe at shibboleth.net
More information about the users
mailing list