Hi,
Firstly sorry for my English, and if you don't understand something tell
me it, I will try to explain it again.
I'm looking for a functionnality of validating a proxy ticket which
rendering a SAML ticket, but I don't find any exposed service in CAS (a
service like /samlValidate but for
Well, this is confusing me because i use the same datasource-bean for a
SearchModeSearchDatabaseAuthenticationHandler. Why does the one class
find the driver, the other does not?
Markus
Scott Battaglia wrote:
You do't have a database driver available (according to the error).
Cheers,
Scott
I would argue you'd be better served simply using the SAML-based
single sign out feature that is supported in current CAS server and
client versions. It works out of the box and lots of folks are using
it.
M
--
You are currently subscribed to cas-user@lists.jasig.org as:
Ye3s, however the new version currently only supports #1
(logoutCallback). We don't have any remaining clients using the other
two methods (iframeLogoutUrl and userLogoutUrl), so we have not
re-implemented those features in 3.3.5.
Nathan Kopp
Applications Strategist
Information Technology Group
Well, this is confusing me because i use the same datasource-bean for a
SearchModeSearchDatabaseAuthenticationHandler.
You're saying that you had the database authentication working with
MySQL prior to your attempt to get JpaServiceRegistryDaoImpl working?
Why does the one class find the
Marvin Addison wrote:
Well, this is confusing me because i use the same datasource-bean for a
SearchModeSearchDatabaseAuthenticationHandler.
You're saying that you had the database authentication working with
MySQL prior to your attempt to get JpaServiceRegistryDaoImpl working?
Exactly. And
Tomcat is 6.0.20. But i cannot remember having to put the driver jar
explicitly to a certain location.
My hunch is you're encountering an unusual classloader problem.
Typically the database driver for your application is an environment
concern that you don't explicitly need to define within
Have you verified that clearPass extension is working correctly?
/cas/clearPass should return something like this:
cas:clearPassResponse xmlns:cas='http://www.yale.edu/tp/cas'
cas:clearPassFailureNo authentication information
provided./cas:clearPassFailure
/cas:clearPassResponse
Yes, When I go to
https://localhost:8443/cas/clearPass
cas:clearPassResponse xmlns:cas='http://www.yale.edu/tp/cas'
cas:clearPassFailureNo authentication information
provided./cas:clearPassFailure
/cas:clearPassResponse
But after I login from On the cas using
Marvin Addison a écrit :
I'm looking for a functionnality of validating a proxy ticket which
rendering a SAML ticket, but I don't find any exposed service in CAS (a
service like /samlValidate but for proxy validation so a /samlProxyValidate
service). This feature wasn't implemented ?
It's
Does this error message mean that I'm getting close?
Could this be an authentication error finally contacting the LDAP
server?
2010-05-12 11:38:42,755 INFO
[org.jasig.cas.services.DefaultServicesManagerImpl] - Loaded 0
services.
2010-05-12 11:38:42,895 ERROR
You are missing the
org.jasig.cas.adaptors.ldap.BindLdapAuthenticationHandler class - make sure
you have the following dependency in your pom.xml:
dependency
groupIdorg.jasig.cas/groupId
artifactIdcas-server-support-ldap/artifactId
version3.3.5/version
The documentation for throttling (
http://www.ja-sig.org/wiki/display/CASUM/Throttling+Login+Attempts) seems to
be specific to 3.3.x. The documented method seems to fail in 3.4.2 (for me
at least, probably due to my lack of Spring configuration experience). If I
could get some pointers, I would
I sent out an email the other day with the small snippit of actual config
needed for 3.4.2 I don't have it handy at the moment. If you can't find
it, I can re-send it tonight (and maybe even update the documentation ;-))
On Wed, May 12, 2010 at 1:39 PM, Patrick Berry pbe...@gmail.com wrote:
So, just to clarify (for the sake of updating the wiki of course)
Including the following bean in cas-servlet.xml in addition to the following
file in spring-configuration should enable login throttling in 3.4.2.
!-- throttleInterceptorTrigger.xml --
?xml version=1.0 encoding=UTF-8?
beans
So, blindly stabbing around in the dark with a text editor and a poor grasp
of spring configuration has led me to think that it cas-servlet.xml section
to modify should look something like this:
bean class=org.springframework.webflow.mvc.servlet.FlowHandlerMapping
Is it possible to do something like this in
spring-configuration/throttleInterceptorTrigger.xml?
bean id=throttleInterceptor
class=org.jasig.cas.web.support.InMemoryThrottledSubmissionByIpAddressAndUsernameHandlerInterceptorAdapter
p:failureRangeInSeconds=120
p:failureThreshold=1 /
--
You
That should right. It looks similar to what I had sent out earlier (from my
quick look).
On Wed, May 12, 2010 at 4:15 PM, Patrick Berry pbe...@gmail.com wrote:
So, blindly stabbing around in the dark with a text editor and a poor grasp
of spring configuration has led me to think that it
I'm just wondering if you have to POST to get the proper response from
clearpass when you're authenticating to it (i.e. with a proxy ticket).
KC
--
You are currently subscribed to cas-user@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
On Wed, 12 May 2010, Leandro Dardini wrote:
I just installed CAS plus LDAP authentication and mod_auth_cas. I can review
the installation with you.
Thanks!
I suggest you to remove tomcat5 and java
from the rpm repository and install them from source.
Our site requires the use of packages
Scott, consider yourself signed up. I will circulate a dial-in number
to those of you who would like to join us.
-Jonathan
On 5/12/10, Scott Battaglia scott.battag...@gmail.com wrote:
If you have any interest in higher ed open or community source, the
direction of Jasig, or just open source
I have been fumbling around for two days trying to get CAS running with LDAP-AD
integration. I am hoping that it is a simple fix like enabling the java class
in the pom.xml he is my config followed by the cas.log output (sorry for the
verbosity):
?xml version=1.0 encoding=UTF-8?
beans
22 matches
Mail list logo
