UnboundID version
Dan McLaughlin
dmclaughlin at tech-consortium.com
Fri Oct 11 12:03:05 EDT 2019
I'm happy to report that 3.4.6 worked seamlessly with 4.0.12
unboundid-ldapsdk and the binary attribute works now. The only
change to our ldap.properties was to add
idp.ldaptive.provider=org.ldaptive.provider.unboundid.UnboundIDProvider.
Thanks for getting this fixed! I won't know if it solves the LDAP
connection leak until later this week.
--
Thanks,
Dan
On Fri, Oct 11, 2019 at 10:22 AM Cantor, Scott <cantor.2 at osu.edu> wrote:
>
> On 10/11/19, 11:18 AM, "dev on behalf of Dan McLaughlin" <dev-bounces at shibboleth.net on behalf of dmclaughlin at tech-consortium.com> wrote:
>
> > 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.
>
> We don't generally update dependencies in patch releases unless there are security issues but unboundid is relatively recently added and I hadn't paid real close attention (not to mention it's not the default yet). Moving to that wouldn't likely be any trouble if desired.
>
> > For ldaptive-unboundid you're using 1.0.13 released last year, the latest is 1.2.4.
>
> Which we cannot move to and would break your system. That would require updating ldaptive itself, and that won't work.
>
> -- Scott
>
>
> --
> To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net
More information about the dev
mailing list