-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I assume there is a reason you have not looked into this, but you did
not mention it, so I thought I would ask: Why not simply tie App B to
CAS A and be done with it? This is the route we are taking at UNI with
the one application we have that
Hi Anthony,
In a typical deployment scenario you don't actively retrieve Service
Tickets from the CAS Server. You normally just let the CAS Client
drive the interaction that for you.
You might from this helpful:
http://www.youtube.com/watch?v=Ik_11Y17ASg
Best,
Bill
On Sun, Aug 7, 2011 at
Hello,
I'm using CAS 3.4.4 successfully for authentication of two apps behind
mod_auth_cas and phpCAS.
Now, I'm working on adding a third app behind a
org.springframework.security.providers.cas.CasAuthenticationProvider
(Jasperserver).
The redirect to the CAS server works fine but the callback
Hi Alex,
Have you tried to follow the LDAP instructions in the CAS Manual:
https://wiki.jasig.org/display/CASUM/LDAP
Which part are you hung up on?
Bill
On Mon, Aug 8, 2011 at 12:27 PM, Alexandre Adao alexa...@gmail.com wrote:
Hello,
I am new on CAS and I would like some help on How to
I am hung on the next step after my CAS and Tomcat are installed and
running. I was able to get successfully the page
http://localhost:8080/cas-server-webapp-3.4.2.1/login and used the
default password and netID and it works. Therefore, it looks like
that the installation was done correctly. Now
On Mon, Aug 8, 2011 at 1:55 PM, Alexandre Adao alexa...@gmail.com wrote:
I am hung on the next step after my CAS and Tomcat are installed and
running. I was able to get successfully the page
http://localhost:8080/cas-server-webapp-3.4.2.1/login and used the
default password and netID and it
I'm using CAS 3.4.2.1, It is working fine with jdbc and ldap authentication
configured falling through.
Principle resolvers configured correctly do work for ldap. I even have a
jdbc attribute repository working correctly.
I've searched for documentation on how to configure a principle resolver
Folks,
I've been working on CAS 3.4.8 Maven Overlay build for a few weeks
with a BindLdapAuthenticationHandler configured in
deployerConfigContext.xml and working well against AD. I'd like to
move to 3.4.9 as I'm running into the the Inspectr issue that was
resolved and also looking at taking
Looks like a new searchContext property needs to be set on
BindLdapAuthenticationHandler if your using that and want to upgrade
to 3.4.9. I realize I'm a little ahead of the release announcement,
so perhaps a note about this was going to be included there. In any
case this config seems to be
