UnboundID version

[Dan McLaughlin]

We are testing moving to 3.4.6 today to check if the binary attribute
fix works. We build the war because the version you publish to Maven
doesn't include all the jars necessary for UnboundID to work, and when
I was updating the pom's I noticed there were newer versions of both.
If there were known issues using the newer versions then I wasn't
going to update them.

For unboundid-ldapsdk you're using 4.0.9 which is from last year,
4.0.12 is the latest version and includes memory leak fixes.  For
ldaptive-unboundid you're using 1.0.13 released last year, the latest
is 1.2.4.

https://www.ldaptive.org/changelog.html

https://github.com/pingidentity/ldapsdk/releases

--

Thanks,

Dan

On Fri, Oct 11, 2019 at 9:51 AM Cantor, Scott <cantor.2 at osu.edu> wrote:
>
> On 10/11/19, 10:48 AM, "dev on behalf of Dan McLaughlin" <dev-bounces at shibboleth.net on behalf of dmclaughlin at tech-consortium.com> wrote:
>
> > Is there a reason you are using such old versions of the
> > unboundid-ldapsdk and ldaptive-unboundid in the 3.4.6 IDP release?
> > Are there known issues with the latest versions?
>
> I don't recall using an "old" version of unboundid itself, but the ldaptive version is what was shipped with 3.0.0 and our API policy does not permit anything else until at least 4.0.0 unless there are security justifications.
>
> -- Scott
>
>
> --
> To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net