start?
Thank you,
Yuriy Zubarev
--
You are currently subscribed to cas-user@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
Hi,
I wanted to upgrade from using version 2.1.1 of the client to version
3.1 but I cannot find anywhere to download it from. I know it sounds
silly but I browsed CAS website and all the repositories I know about.
Yuriy
--
You are currently subscribed to cas-user@lists.jasig.org as:
Hi,
If you have a self-signed SSL certificate then you could try these
instructions: http://blogs.sun.com/andreas/entry/no_more_unable_to_find
They worked for us.
Regards,
Yuriy
On Mon, Sep 28, 2009 at 2:31 PM, Lee, Sung sung...@tamu.edu wrote:
I am trying to test the connection to our new
Guys,
Any help would be appreciated. Even some links to get started.
Thank you,
Yuriy
On Mon, Oct 19, 2009 at 6:03 PM, Yuriy Zubarev yuriyzubar...@gmail.com wrote:
Hi,
We have a business rule that forbids two different users to be logged
in the system under the same set of credentials
them. The default registry will return an
entire collection of tickets, while the memcache registry is unable to. The
JPA one will, but to load the entire table of tickets may not be efficient.
Cheers,
Scott
On Tue, Oct 20, 2009 at 9:05 PM, Yuriy Zubarev yuriyzubar...@gmail.com
wrote
We had similar requirements and we worked them out by wrapping Jasig's
Authentication Filter by our own Authentication Filter.
If anyone is interested in details:
http://midnightit.wordpress.com/2010/02/15/cas-branded-authentication-filter/
Regards,
Yuriy Zubarev
On Sun, Feb 14, 2010 at 7:05
Greetings,
After upgrading from version 3.3.* to 3.4.* we noticed a small
difference in a behavior of login flow and a form. Whenever user
provides an incorrect combination of username and password, CAS flow
goes back to log-in page with a correct error message but username
field is empty. It
tried it :-)
Cheers,
Scott
On Thu, Jun 10, 2010 at 2:55 PM, Yuriy Zubarev yzuba...@boats.com wrote:
Greetings,
After upgrading from version 3.3.* to 3.4.* we noticed a small
difference in a behavior of login flow and a form. Whenever user
provides an incorrect combination of username