run into.
From: Lapanja, Bob@POST [mailto:bob.lapa...@post.ca.gov]
Sent: Thursday, August 13, 2015 2:10 PM
To: cas-user@lists.jasig.orgmailto:cas-user@lists.jasig.org
Subject: [cas-user] single log out and login-webflow.xml
Using 4.0.0
I'm configuring single log out on some services and I have
Using 4.0.0
I'm configuring single log out on some services and I have encountered a
situation I would appreciate some clarity on. For this particular use case, we
want the logout callback to be called if the user visits /cas/logout directly,
but not when the TGT expires and is cleared out by
I believe this additional step is for anti-phishing. It is for the site to
verify its authenticity to the user, not for the user to verify their
authenticity to the site. The step to require them to select the correct one
is to make sure they are actively verifying the image, and not ignoring
In the src directory, under
WEB-INF/spring-configuration/propertyFileConfigurer.xml I have this:
bean id=propertyPlaceholderConfigurer
class=org.springframework.beans.factory.config.PropertyPlaceholderConfigurer
You need to register the module in your web.config differently depending on
whether you are using integrated mode (only available in newer versions of IIS)
or classic mode. In integrated mode, it should be registered under
system.webserver/modules, in classic mode it should be registered under
Hi all,
We use the suggested maven WAR overlay method for building CAS 3.5.2
and we have it working. We'd like to change the look and feel of the
login page to personalize it but are running into issues. If we modify
the css files inside of the deployed web application in Tomcat (in our
This is what I used for my authenticationHandler that did not require a
PrincipalResolver:
bean id=authenticationManager
class=org.jasig.cas.authentication.PolicyBasedAuthenticationManager
constructor-arg
map
entry key-ref= passwordHandler value=#{ null
I recently migrated to CAS 4.0 using LDAP. I didn’t need nor use the sslConfig
attribute or bean. As for the search filter, the documentation uses {user}
instead of %u. That’s also what I used and it worked.
The only places I deviated from the documentation you linked to (for the LDAP
In any case I'm open to considering further in the context of an
enhancement targeting 4.1. Please file a Jira issue if that sounds good
to you. Thanks for sharing your use case.
I created issue CAS-1453. Thank you for considering it. I tried my best to be
brief and concise in the
I recently updated my CAS 3.5.2 installation to CAS 4.0.0. I got it working
after working through some initial issues with the LdapAuthenticationHandler
not finding the users. I had to set subtreeSearch to true on
org.ldaptive.auth.PooledSearchDnResolver for my authenticator, in case somebody
1) I have 2 authentication handlers that are used concurrently, one
which uses a DB query and the other a LDAP query...
Is this an appropriate use of the postAuthenticate method, or am I
twisting this extensibility point in a way it isn’t intended?
Sounds like a creative use though I
11 matches
Mail list logo
