Hi guys,
We have an up & running installation of CAS 3.5 with LDAP auth. Thanks
for such a great tool :)
Now, we need to add X509 based authentication. The idea is that the
user will be able to choose between regular LDAP auth with login/pass
or X509 certificate.
Is this supported by CAS? I have
Indeed, I'm taking the point about the documentation. But it's worth
mentioning that it's still experimental and needs to be implemented on CAS
clients side...
Best,
Jérôme
2014-03-06 21:21 GMT+01:00 Marvin Addison :
> > I've seen some mention of front channel slo in cas 4.x but no mention of
I'm sure it does if I understand it better.
I tried adding the log4jconfigurer section to applicationContext, but
the build says:
Running org.jasig.cas.WiringTests
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.462
sec <<< FAILURE!
Results :
Tests in error:
testWiring(
Does this help?
https://issues.jasig.org/browse/CAS-1094
https://groups.google.com/forum/#!topic/jasig-cas-user/5RZqSQyRFEQ
> -Original Message-
> From: Marvin E Budd [mailto:mb...@andrews.edu]
> Sent: Thursday, March 06, 2014 1:19 PM
> To: cas-user@lists.jasig.org
> Subject: [cas-user]
> I've seen some mention of front channel slo in cas 4.x but no mention of
> whether this is a fix for the shortcomings of 3.x in regards to single logout
> in clustered environments. Has cas 4.x finally addressed this issue?
Yes, see https://issues.jasig.org/browse/CAS-1292 for more
information
This is a new CAS install on RH6 using the Ellucian instructions. I've
done everything like they suggested, hopefully. I built and deployed the
cas.war to a weblogic base domain successfully, and when I browse to
https://mycas/cas it redirects to https://mycas/cas/login, so I know
something is
Hi,
I've seen some mention of front channel slo in cas 4.x but no mention of
whether this is a fix for the shortcomings of 3.x in regards to single logout
in clustered environments. Has cas 4.x finally addressed this issue?
--
You are currently subscribed to cas-user@lists.jasig.org as:
arch...
Hi there,
I have a CAS Server that uses three credentialsToPrincipalResolvers: x509v3
certificate, Openldap user and password, and kerberos.
It all works fine, except CAS only returns the user attributes when the user
logs in through x509v3 certificate or user/password. If the user has us