[cas-dev] CAS server fail-over

[Scott Battaglia]

CAS3 has abstract classes for creating distributed ticket registries which
provide hooks for updating state in stored registries.

-Scott

-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: http://www.linkedin.com/in/scottbattaglia


On Sat, Jan 10, 2009 at 5:02 AM, Lekhnath Bhusal <lbhusal at d2hawkeye.com>wrote:

> Hell team,
> I have 6 different applications authenticated through single CAS server.
> CAS server version is 3.2.1 I need to use CAS fail-over implementation
> through DNS fail-over. For the TicketGrantingTicket sharing, I have used
> common database.
> Since I cannot write to database after each grantServiceTicket()
> execution, I need to know the result of service ticket validation and
> add the service ticket to database. Currently services from
> TicketGrantingTicket are not exposed and I can not access the tickets to
> restore the TicketGrantingTicket from the database. Can we change the
> ProxyValidateController to allow some custom operation after successful
> ticket validation? This will help for custom logging purpose also.
>
> Is there any implementation for fail-over in CAS 4?
>
> Lekhnath
>
>
>
>
>
>
> PRIVACY NOTICE
>
> This email and any attachments may be confidential and/or privileged. Use
> of the information contained in this email by anyone other than the intended
> recipient is strictly prohibited. If you have received this email in error,
> please notify the sender by replying to this message and delete this email.
> _______________________________________________
> cas-dev mailing list
> cas-dev at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas-dev/attachments/20090111/724f513f/attachment.html