>> @Robert : thanks for pointing that out, but the CAS-814 ticket has a
fix version set to 4.0.0 M1. Is it available in 3.5.0 ?
No, its available in the 4.0.0 branch. It requires a decent amount of work
to keep track of that information in order to be able to clean it up.
On Fri, Sep 7, 2012 a
On Sep 6, 2012, at 1:25 AM, jleleu wrote:
> Hi,
>
> I deserve the question ;-)
> I really appreciate all feedbacks on use cases and solutions, but when it
> comes to contribute, things are getting a little harder.
> We have to re-challenge the functional need and the technical solution.
>
> Le
>
> In order to discard old TGT with different IP, you have to query your ticket
> registry with the username : it's not in the default API, I don't like the
> idea to expose this as a default method as for security reason, ticket
> registries should only be queried by (ticket) id. So it's so
ps to the server to achieve the same thing, IIANM.
From: jleleu [lel...@gmail.com]
Sent: Wednesday, September 05, 2012 12:20 AM
To: cas-dev@lists.jasig.org
Subject: re:[cas-dev] Offering a couple solutions
Hi,
For the first issue, I understand you want to che
: jleleu [mailto:lel...@gmail.com]
Sent: den 5 september 2012 09:21
To: cas-dev@lists.jasig.org
Subject: re:[cas-dev] Offering a couple solutions
Hi,
For the first issue, I understand you want to check IP address between SSO
sessions for the same user (does the user use the same IP address as in its
Hi,
For the first issue, I understand you want to check IP address between SSO
sessions for the same user (does the user use the same IP address as in its
previous SSO session ?). It means you need to keep expired TGTs : how that can
be possible as ticket registries are associated to mechanims
Hi. We're using CAS, and we've made some extensions to it that I'd like to
document for anyone else who comes along after us desiring to solve similar
problems.
First, we were asked to allow CAS to limit users to a single IP address at a
time. That is, if the same user signs on from a new IP ad
