Yep, this is really odd. IDEA knows about a cas-client-core dependency,
but that dependency is not anywhere in the path, in any poms, etc. How
can that be? Is some sort of funky plugin automagically injecting a
dependency into the maven build process?
$ grep -rl 'cas-client-core' ./
./.idea/artifacts/cas_server_webapp_war_exploded.xml
./.idea/libraries/Maven__org_jasig_cas_client_cas_client_core_3_2_1.xml
$ find ./ | grep cas-client
mvn dependency:tree reveals nothing either.
On 13-06-06 11:23 AM, Trenton D. Adams wrote:
Unfortunately, I can't really debug this. The line numbers of the code
in git, for v3.4.10 do not match. And if I try to compile I get an
error building the webapp. I don't even see a cas-client-core anywhere
in the path, and grep returns nothing.
[INFO]
------------------------------------------------------------------------
[INFO] Building JA-SIG CAS Web Application
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).
Project ID: org.jasig.cas:cas-client-core
Reason: Parent: org.jasig.cas:cas-client:jar:3.1.10 of project:
org.jasig.cas:cas-client-core has wrong packaging: jar. Must be 'pom'.
for project org.jasig.cas:cas-client-core
On 13-06-06 10:36 AM, Trenton D. Adams wrote:
Hi Guys,
I'm pointing our CAS to a new test server, running OpenLDAP 2.4. When I
enter an incorrect password, I get the message "CAS is Unavailable". If
I point it back to the old server, it's fine.
I have CAS audit enabled, and with the old ldap I get...
WHAT: error.authentication.credentials.bad
With the new one I get...
WHAT: [LDAP: error code 49 - Invalid Credentials]; nested exception is
javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid
Credentials]
I haven't looked at the LDAP authentication code yet, but by the looks
of it, it's expecting a very specific string response for a failed
authentication? So, it seems like maybe that's changed slightly between
OpenLDAP releases?
Anyhow, I'm betting someone's fixed this in newer versions of the
BindLdapAuthenticationHandler? If so, are they compatible with CAS
3.4.10?
Thanks.
--
Trenton D. Adams
Senior Systems Analyst/Web Software Developer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!
--
This communication is intended for the use of the recipient to whom it
is addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communications received in error, or
subsequent reply, should be deleted or destroyed.
---
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
