From 1e1a0ec5e877a32e777bb8d1fac38a0f2129e365 Mon Sep 17 00:00:00 2001 From: Misagh Moayyed Date: Wed, 17 May 2017 16:50:13 -0700 Subject: [PATCH] update readme --- README.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index ebdfe9f..5576b8d 100644 --- a/README.md +++ b/README.md @@ -342,7 +342,14 @@ Validates the tickets using the CAS 2.0 protocol. If you provide either the `acc | `hostnameVerifier` | Hostname verifier class name, used when making back-channel calls | No #### org.jasig.cas.client.validation.Cas30ProxyReceivingTicketValidationFilter -Validates the tickets using the CAS 3.0 protocol. If you provide either the `acceptAnyProxy` or the `allowedProxyChains` parameters, a `Cas30ProxyTicketValidator` will be constructed. Otherwise a general `Cas30ServiceTicketValidator` will be constructed that does not accept proxy tickets. Supports all configurations that are available for `Cas20ProxyReceivingTicketValidationFilter`. +Validates the tickets using the CAS 3.0 protocol. If you provide either the `acceptAnyProxy` or the `allowedProxyChains` parameters, +a `Cas30ProxyTicketValidator` will be constructed. Otherwise a general `Cas30ServiceTicketValidator` will be constructed that does not +accept proxy tickets. Supports all configurations that are available for `Cas20ProxyReceivingTicketValidationFilter`. + +#### org.jasig.cas.client.validation.json.Cas30JsonProxyReceivingTicketValidationFilter +Indentical to `Cas30ProxyReceivingTicketValidationFilter`, yet the filter is able to accept validation responses from CAS +that are formatted as JSON per guidelines laid out by the CAS protocol. See the [protocol documentation](https://apereo.github.io/cas/) +for more info. ##### Proxy Authentication vs. Distributed Caching The client has support for clustering and distributing the TGT state among application nodes that are behind a load balancer. In order to do so, the parameter needs to be defined as such for the filter.