-Scott
On 9/1/06,
Arnaud Lesueur <[EMAIL PROTECTED]> wrote:
Scott,
Few weeks ago, I have started a very small admin view with only statistics on tickets and authentication handler. This
implementation was based on a custom EventHandler implementation. I have stopped this work due to the following
remarks :
- For the authentications, we would like to have some stats on which handler has been used (eg spnego, ldap, radius …)
- Failed authentication should also be counted. But in the case of multiple handler this causes a problem while.
Example: we are using SPNEGO and LDAP. In this case. If SPNEGO returns a failure, the user gets the form which is
configured with the LDAP handler. So in that case, there is a failure for SPNEGO and a success on LDAP. The problem
exists also with cascaded/redundant LDAP Handler, there is an event failure event send on the first LDAP server and
then a success on the second LDAP :-/
- We are only counting local information but in case of a cluster global information should also be available.
- There is no event if tickets are cleaned with the DefaultTicketRegistryCleaner. This is a cause of false statistics
for deleted ticket.
Arnaud
Le Jeu 31 août 2006 21:29, Scott Battaglia a écrit :
> Here's some of the stuff we had written down:
> 1. General/Environmental Information (JVM, Memory, etc.)
> 2. Authentications over time (i.e. authntications in the last 5 minutes, 10
> minutes, etc.) 3. The Last Spike
> 4. Export statistics to CSV, etc.
> 5. Current Status of Registry (i.e. how many tickets)
> 6. Trace Authentications/Services granted by NetId.
> 7. Response time of "authentication backing source"
> 8. Exception log/health of servers
>
>
> This is in addition to what you guys came up with.
>
>
> -Scott
>
>
> On 8/31/06, Scott Battaglia < [EMAIL PROTECTED]> wrote:
>
>>
>> Thanks guys. I'm adding these to our list. When I get a few minutes later
>> I'll post the list we came up with in a meeting yesterday (maybe it can
>> spark some more ideas).
>>
>> -Scott
>>
>>
>>
>> On 8/31/06, Liu, Siyuan <[EMAIL PROTECTED]> wrote:
>>
>>>
>>> Maybe the ability to "force" logout a user by admin.
>>> Thanks
>>>
>>>
>>> On 30/08/06, Scott Battaglia < [EMAIL PROTECTED]> wrote:
>>>
>>>> All,
>>>>
>>>>
>>>> One of the open JIRA issues is for a CAS Administration section.
>>>> We're interested in gathering requirements for a possible
>>>> Administration section within CAS. If you have ideas, requirements,
>>>> feature requests, etc. please let us know.
>>>>
>>>> Thanks
>>>> -Scott
>>>>
>>>>
>>>> _______________________________________________
>>>> Yale CAS mailing list
>>>> [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
>>>>
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> Yale CAS mailing list
>>> [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
>>>
>>>
>>> _______________________________________________
>>> Yale CAS mailing list
>>> [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
>>>
>>>
>>
>>
> _______________________________________________
> Yale CAS mailing list
> [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
>
>
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
