to
Sent: Thursday, January 28, 2021 11:41 PM
To: CAS Community mailto:cas-user@apereo.org>>
Subject: [EXTERNAL SENDER] Re: [cas-user] CAS 5.0.x newer ldaptive?
Since the approach of trying to use an updated ldaptive library was rapidly
getting complicated, I tried the suggested Un
boundid-ldapsdk:4.0.9"
>
>
>
> to the Gradle build dependencies. I would assume it would be the same for
> Maven.
>
>
>
> *From:* cas-user@apereo.org *On Behalf Of *Baron
> Fujimoto
> *Sent:* Thursday, January 28, 2021 11:41 PM
> *To:* CAS Community
>
4.0.9"
to the Gradle build dependencies. I would assume it would be the same for
Maven.
From: cas-user@apereo.org On Behalf Of Baron Fujimoto
Sent: Thursday, January 28, 2021 11:41 PM
To: CAS Community
Subject: [EXTERNAL SENDER] Re: [cas-user] CAS 5.0.x newer ldaptive?
Since the approach of try
imoto
Sent: Thursday, January 28, 2021 11:41 PM
To: CAS Community
Subject: [EXTERNAL SENDER] Re: [cas-user] CAS 5.0.x newer ldaptive?
Since the approach of trying to use an updated ldaptive library was rapidly
getting complicated, I tried the suggested UnboundIDProvider[*] with the
following in my cas.
Since the approach of trying to use an updated ldaptive library was rapidly
getting complicated, I tried the suggested UnboundIDProvider[*] with the
following in my cas.properties:
cas.authn.ldap[0].providerClass=org.ldaptive.provider.unboundid.UnboundIDProvider
But CAS throws this exception on
using the UnboundID provider.
From: cas-...@apereo.org on behalf of Baron Fujimoto
Sent: Wednesday, January 27, 2021 19:06
To: CAS Users
Subject: [cas-user] CAS 5.0.x newer ldaptive?
I'm working with Oracle to troubleshoot a bug we've encountered with their JDK
(1.8u231+) and LDAP errors. Accordin
__
From: cas-...@apereo.org on behalf of Baron Fujimoto
Sent: Wednesday, January 27, 2021 19:06
To: CAS Users
Subject: [cas-user] CAS 5.0.x newer ldaptive?
I'm working with Oracle to troubleshoot a bug we've encountered with their JDK
(1.8u231+) and LDAP errors. According to their analysis,
Baron,
You are approaching the amount of work required to upgrade cas and java.
Is there a reason why you are not upgrading cas? (rhetorical)
We upgraded to openJDK 11 for our applications (open source and internal) and
the process was relatively painless.
One potential trap with compiling
that. I have spring and log4j in those
>> excludes. I'm excluding Duo out of a normal dependency section. I have a
>> different GAV bringing that dependency in.
>>
>> We're using the UnboundID provider.
>> --
>> *From:* cas-...@
You have to do overlay exclusions. Which for me looks like. Obviously close the
XML out as appropriate. I have further build plugins.
maven-war-plugin
2.6
false
false
false
${project.build.directory}/war/work/org.apereo.cas/cas-server-webapp/META-INF/MANIFEST.MF
org.apereo.cas
Hmm, the older ldaptive-1.2.0.jar and ldaptive-beans-1.2.0.jar don't appear
in the packages dependency tree, I'm not sure how I would exclude them from
the build. If I manually delete them from the resulting cas.war file, then
when I start CAS, I encounter the following error/exception:
ERROR
Baron,
Check what packages are included in the build with:
mvn dependency:tree
You can transitive dependencies for the old library.
But, the overlay, itself, may include an old version of the library, which
means that you would have to manually remove the old one from the war. Maybe
the
luding Duo out of a normal dependency section. I have a
> different GAV bringing that dependency in.
>
> We're using the UnboundID provider.
> --
> *From:* cas-...@apereo.org on behalf of Baron
> Fujimoto
> *Sent:* Wednesday, January 27, 2021 19:
@apereo.org on behalf of Baron Fujimoto
Sent: Wednesday, January 27, 2021 19:06
To: CAS Users
Subject: [cas-user] CAS 5.0.x newer ldaptive?
I'm working with Oracle to troubleshoot a bug we've encountered with their JDK
(1.8u231+) and LDAP errors. According to their analysis, they're claiming
I'm working with Oracle to troubleshoot a bug we've encountered with their
JDK (1.8u231+) and LDAP errors. According to their analysis, they're
claiming that the problem lies with the ldaptive library being used by this
old (I know) version of CAS. More specifically that the subsequent JDKs
adhere
15 matches
Mail list logo
