Cassava provides authentication services based on the Jasig CAS protocol.
Cassava allows WordPress to act as a single sign-on authenticator using versions 1.0 and 2.0 of the Central Authentication Service (CAS) protocol.
That way, users on your WordPress install may be able to access different applications that support the CAS protocol by providing a single set of credentials and without exposing the user's password.
By default, CAS method URIs are provided under the
/wp-cas/login: Allows a remote service to request that a user authenticate on the CAS server. Will redirect back to the remote service along with a service ticket.
/wp-cas/logout: Terminates the single sign-on session. May optionally redirect the user back to the remote service.
/wp-cas/proxy[CAS 2.0]: Provides access to remote services with proxy tickets in exchange for proxy-granting tickets. Returns an XML response.
/wp-cas/proxyValidate[CAS 2.0]: Allows a remote service to validate a service or proxy ticket forwarded by the user on redirect. Returns an XML response.
/wp-cas/serviceValidate[CAS 2.0]: Allows a remote service to validate a service ticket forwarded by the user on redirect. Returns an XML response.
/wp-cas/validate[CAS 1.0]: Allows a remote service to validate a service ticket forwarded by the user on redirect. Returns a plaintext response.
There are a few client integration libraries available for CAS, as well as a handy guide for CASifying several existing applications. Independent WordPress installations may integrate with Cassava using a client plugin such as CAS Maestro.
Please follow and contribute to Cassava's development on Github.
Requires: 3.9 or higher
Compatible up to: 4.0.1
Last Updated: 2014-8-28
Active Installs: 20+
0 of 1 support threads in the last two months have been resolved.
Got something to say? Need help?