Home >> All >> org >> acegisecurity >> providers >> [ cas Javadoc ]

•	org.acegisecurity.providers.cas.cache.* (1)	•	org.acegisecurity.providers.cas.populator.* (1)
•	org.acegisecurity.providers.cas.proxy.* (3)	•	org.acegisecurity.providers.cas.ticketvalidator.* (2)

• org.acegisecurity.providers.cas: Javadoc index of package org.acegisecurity.providers.cas.


Package Samples:

• org.acegisecurity.providers.cas.ticketvalidator: An authentication provider that can process Yale Central Authentication Service (CAS) service tickets and proxy tickets.  
• org.acegisecurity.providers.cas.populator: An authentication provider that can process Yale Central Authentication Service (CAS) service tickets and proxy tickets.  
• org.acegisecurity.providers.cas.proxy
• org.acegisecurity.providers.cas.cache

Classes:

• StatelessTicketCache: Caches CAS service tickets and CAS proxy tickets for stateless connections. When a service ticket or proxy ticket is validated against the CAS server, it is unable to be used again. Most types of callers are stateful and are associated with a given HttpSession . This allows the affirmative CAS validation outcome to be stored in the HttpSession , meaning the removal of the ticket from the CAS server is not an issue. Stateless callers, such as remoting protocols, cannot take advantage of HttpSession . If the stateless caller is located a significant network distance from the CAS server, acquiring ...
• CasProxyDecider: Decides whether a proxy list presented via CAS is trusted or not. CAS 1.0 allowed services to receive a service ticket and then validate it. CAS 2.0 allows services to receive a service ticket and then validate it with a proxy callback URL. The callback will enable the CAS server to authenticate the service. In doing so the service will receive a proxy-granting ticket and a proxy-granting ticket IOU. The IOU is just an internal record that a proxy-granting ticket is due to be received via the callback URL. With a proxy-granting ticket, a service can request the CAS server provides it with a proxy ...
• CasAuthoritiesPopulator: Populates the UserDetails associated with a CAS authenticated user. CAS does not provide the authorities (roles) granted to a user. It merely authenticates their identity. As the Acegi Security System for Spring needs to know the authorities granted to a user in order to construct a valid Authentication object, implementations of this interface will provide this information. A org.acegisecurity.userdetails.UserDetails is returned by implementations. The UserDetails must, at minimum, contain the username and GrantedAuthority[] objects applicable to the CAS-authenticated user. Note that Acegi Security ...
• CasAuthenticationProvider: An org.acegisecurity.providers.AuthenticationProvider implementation that integrates with Yale Central Authentication Service (CAS). This AuthenticationProvider is capable of validating org.acegisecurity.providers.UsernamePasswordAuthenticationToken requests which contain a principal name equal to either CasProcessingFilter.CAS_STATEFUL_IDENTIFIER > CasProcessingFilter.CAS_STATEFUL_IDENTIFIER 55 or CasProcessingFilter.CAS_STATELESS_IDENTIFIER > CasProcessingFilter.CAS_STATELESS_IDENTIFIER 55 . It can also validate a previously created CasAuthenticationToken .
• TicketValidator: Validates a CAS service ticket. Implementations must accept CAS proxy tickets, in addition to CAS service tickets. If proxy tickets should be rejected, this is resolved by a CasProxyDecider implementation (not by the TicketValidator ). Implementations may request a proxy granting ticket if wish, although this behaviour is not mandatory.
• DaoCasAuthoritiesPopulator: Populates the CAS authorities via an org.acegisecurity.userdetails.UserDetailsService . The additional information (username, password, enabled status etc) an AuthenticationDao implementation provides about a User is ignored. Only the GrantedAuthority s are relevant to this class.
• NamedCasProxyDecider: Accepts proxied requests if the closest proxy is named in the validProxies list. Also accepts the request if there was no proxy (ie the user directly authenticated against this service).
• AcceptAnyCasProxy: Accepts a proxied request from any other service. Also accepts the request if there was no proxy (ie the user directly authenticated against this service).
• RejectProxyTickets: Accepts no proxied requests. This class should be used if only service tickets wish to be accepted (ie no proxy tickets at all).
• EhCacheBasedTicketCache: Caches tickets using a Spring IoC defined EHCACHE .
• CasProxyTicketValidator: Uses CAS' ProxyTicketValidator to validate a service ticket.
• ProxyUntrustedException: Thrown if a CAS proxy ticket is presented from an untrusted proxy.
• AbstractTicketValidator: Convenience abstract base for TicketValidator s.
• CasAuthenticationToken: Represents a successful CAS Authentication .
• TicketResponse: Represents a CAS service ticket in native CAS form.

Home | Contact Us | Privacy Policy | Terms of Service