Hi,
I think it's the best strategy : focus our efforts on 4.0.
About the release date, hard to say. 4.0 is a big change and some things
have been broken.
I see 12 JIRA tickets still open for 4.0. I will try to address them this
week...
A RC2 before the end of september would be great.
Best
Hi,
Did you simply check that you have the same value for your JSESSIONID
cookie ?
Just to clarify things about the terminate session listener, it has been
implemented since 3.5.x (not before). And you use CAS 3.4.10, right ?
Best regards,
Jérôme
2013/9/10 Trenton D. Adams tre...@athabascau.ca
Fantastic news!
Thanks!
2013/9/10 Gasper, John jgas...@ewu.edu
Hey all,
** **
Unicon will trying to implement Antoni’s proposed fix, or likely something
based off of it, later this week. We plan to offer a pull request for the
3.5.X branch when we get it working.
** **
We are running one CAS server and are now in the
process of load testing the capability of CAS to match the load
volume tested when using only Banner BEIS authentication.
I responded to this post on cas-dev. Replaying here.
Some on the team assess the situation as an indication that CAS can
Hi,
AOP may be tricky sometimes. I suspect two things :
- the first one is that AOP proxies are created by
the DefaultAdvisorAutoProxyCreator :
https://github.com/Jasig/cas/blob/master/cas-server-webapp/src/main/webapp/WEB-INF/spring-configuration/applicationContext.xml#L122
for
the current
I'm trying to add a forgot password branch to login-webflow.xml. I added an
anchor on casLoginView.jsp which points to a new view,
myForgotPasswordView.jsp. The user should enter their username, then press the
submit button. When they do, I invoke a back-end action.
Unfortunately, when I hit
Please let me know how it goes, thanks!
On Wed, Sep 11, 2013 at 1:29 AM, Miguel Ángel Júlvez ma.jul...@gmail.comwrote:
Fantastic news!
Thanks!
2013/9/10 Gasper, John jgas...@ewu.edu
Hey all,
** **
Unicon will trying to implement Antoni’s proposed fix, or likely
something
We tested CAS last fall and again just after the first of this year when load
testing our new Liferay portal. With the Liferay testing we pushed over 2000
simultaneous connections on two Liferay servers with CAS logins handled by two
clustered servers. The Liferay servers became the
This issues has been known for some time, but we haven't had a
deployer need for a fix until now. Let's target a fix for 3.5.3 and
4.0.
Best,
Bill
On Thu, Sep 5, 2013 at 2:50 PM, Rich Renomeron - TCG
richard.renome...@tcg.com wrote:
So a quick search of the mailing lists, Google, and
Hello,
I did spend very time to search on google if there is example of using CAS
with two differente ways to authenticate, but sorry to say that I didn't
find out...
Please, someone could show me how I can do that?
See key parts of my deployerConfigContext.xml
...
property
On 13-09-11 01:47 AM, Jérôme LELEU wrote:
Hi,
Did you simply check that you have the same value for your JSESSIONID
cookie ?
Just to clarify things about the terminate session listener, it has
been implemented since 3.5.x (not before). And you use CAS 3.4.10, right ?
Best regards,
Jérôme
I'm
So, I have been trying to implement Ehcache on our CAS cluster, and it is
mostly working. It caches tickets, and the two nodes are replicating and
validating each other's tickets. But it still has an issue with availability.
Here is what is happening:
1. I open a session with a browser
Thanks to all for you responses.
Linda
Linda Toth
University of Alaska - Office of Information Technology (OIT) - Identity
and Access Management
910 Yukon Drive, Suite 103
907-450-8320
Fairbanks, Alaska 99775
linda.t...@alaska.edu | www.alaska.edu/oit/
On Tue, Sep 10, 2013 at 1:56 PM, Andrew
On Sep 11, 2013, at 9:24 AM, St Laurent, Mark mark.stlaur...@yc.edu wrote:
So, I have been trying to implement Ehcache on our CAS cluster, and it is
mostly working. It caches tickets, and the two nodes are replicating and
validating each other’s tickets. But it still has an issue with
On 09/11/2013 01:36 PM, St Laurent, Mark wrote:
It still is not working. In fact, I've discovered that if I shut down one of
the nodes I can't even log in to a CASified app under a completely new
session. If one node is down, the entire CAS cluster is down. It is
apparently expiring the
If both nodes are up, it works fine, I can see in the CAS logs where they are
validating each other's tickets. I actually have the firewalls turned
completely off just to make sure they're not interfering.
--
Mark St. Laurent
Web Systems Administrator
Yavapai
16 matches
Mail list logo