idp-war-3.4.4.war in Maven Repo is bad

[Dan McLaughlin]

With the root logger set to ALL I was able to use Beyond Compare to
diff the login and attribute resolution and the only difference I can
find is that the objectGUID is getting corrupted with UnboundID ID is
used.  When using JNDI we set   <LDAPProperty
name="java.naming.ldap.attributes.binary" value="objectGUID"/>, but
that seems to be getting ignored by the UnboundID  provider.

[objectGUID[GqzJ3AninkS/SGDsawhnYg==]]
[objectGUID[ ��� �D�H`�k gb]]


--

Thanks,

Dan McLaughlin
Technology Consortium, LLC
dmclaughlin at tech-consortium.com
mobile: 512.633.8086
http://www.tech-consortium.com

NOTICE: This e-mail message and all attachments transmitted with it
are for the sole use of the intended recipient(s) and may contain
confidential and privileged information. Any unauthorized review, use,
disclosure or distribution is strictly prohibited. The contents of
this e-mail are confidential and may be subject to work product
privileges. If you are not the intended recipient, please contact the
sender by reply e-mail and destroy all copies of the original message.

On Thu, Jun 13, 2019 at 5:51 PM Cantor, Scott <cantor.2 at osu.edu> wrote:
>
> > I get where you're coming from.  Maybe update the release notes to let people
> > know that if they got the idp-war from Maven they will still need to download
> > and install the ldaptive jars and put them in their classpath as was discussed in
> > one of the related ticket on the topic.
>
> I don't plan to, but if somebody else wants to add material about something we don't support, the wiki is not limited to us to edit.
>
> > As to why adding the new property is causing failures, I still haven't figured out
> > why yet. It looks like I narrowed down the failures to something related to us
> > using JAASAuthnConfig.
>
> I use JAAS with it FWIW.
>
> > was using JAAS Authn. One thing to note is that it doesn't seem to break the
> > JAAS Authn, but it would seem that something with the attribute resolution
> > breaks.
>
> Those are unrelated, so it can't be caused by JAAS but then affect attribute resolution. I think you're misdiagnosing something. An attribute resolver issue is not connected to how you authenticate.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net