Download Flexible authentication for stateless web services

http://ux-desktop03/geoserver/stateless_service?ticket=PT-957ZuucXqTZ1YcJw81T3dxf
The proxied application has an CAS filter in its chain looking for requests containing
a “ticket” parameter. The value should start with “PT-”.
If such a request is received the filter validates the proxy ticket with
http://ux-server02:8080/cas/proxyValidate/?
targetService=http://ux-desktop03/geoserver/stateless_service&
ticket=PT-957-ZuucXqTZ1YcJw81T3dxf
On success the answer contains the user name and the URL of the proxy callback.
<cas:serviceResponse xmlns:cas='http://www.yale.edu/tp/cas'>
<cas:authenticationSuccess>
<cas:user>myuser</cas:user>
<cas:proxies>
<cas:proxy>https://uxdesktop03/geoserver/j_spring_cas_security_proxyreceptor
/cas:proxy>
</cas:proxies>
</cas:authenticationSuccess>
</cas:serviceResponse>
3.5.3.2 Protocol elements for proxy tickets
The “/proxy” URI requests a proxy ticket. Parameters are
–
targetService (required)
The target service. This does not necessarily have to be an URL, the target
may be any type of software providing services. This parameter must match
the service parameter used in “proxyValidate”.
–
pgt (required)
A valid PGT.
The “/proxyValidate” URI validates proxy tickets and service tickets. Its parameters
are equal to “/serviceValidate”.
3.5.3.3 Entry Point
If the authentication token has expired from the cache or the proxy ticket does not
validate successfully an HTTP 401 (UNAUTHORIZED) is sent back.
3.5.3.4 Cache key derivation
The proxy ticket PT is a one time ticket comparable to the service ticket ST. The
proxy application is responsible for acquiring a new proxy ticket before a cache time
out occurs. The cache key is the ticket value. If the ticket value is not in the cache for
56