Hi,
I finally got it working, here is what I did:
1. Download and unzip the CAS-server-3.5.1 package on the machine(RHEL6 in
my case).
2. Open CAS-server-3.5.1/cas-server-webapp/pom.xml, and add the following
dependency within dependencies tag in your pom.xml file
3. Build
Hi Shashank,
We are in the process of setting up a standalone CAS server with version
3.5.1 and we ran into the same problem as you described. Their documents
just miss a lot of important details and very confusing. Did you ever fix
the problem? And how? Any insight and advice will be much
Unless you need/want attributes, FWIW I didn't see any meaningful difference in
performance (with our site anyway) between wiring up the 'native' CAS LDAP
adapter (fast bind) and using JAAS/LDAP.
The latter was fairly simple:
- set up JaasAuthenticationHandler in deployerConfigContext.xml
-
rebuilding the CAS project in
case it generates more dependencies in the war bundle.
Best Regards!
Larry
-Original Message-
From: Tom Poage [mailto:tfpo...@ucdavis.edu]
Sent: Friday, June 14, 2013 2:32 PM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] CAS + LDAP initialisation error
On 06/14/2013 11:59 AM, Peng Zhang wrote:
Thanks for your input. I noticed on Jasig wiki that LDAP and your mentioned
JAAS are two different options for configuring CAS authentication. However,
we need to set up our CAS to check user credentials against our LDAP
directory. Did you actually
