apereo / dotnet-cas-client-memcached

Memcached backed Proxy/Service Ticket Managers for the Apereo .NET CAS Client

Introduction

This project is an add-on to the Apereo .NET CAS Client that implements the proxy and service ticket managers backed by a Memcached data store.

By storing your proxy and service tickets in a centralized data store your applications running in a distributed, clustered or load balanced environment will all have access to the same proxy and service ticket data. This is not possible to achieve with the default in-memory proxy and service ticket managers that ships with the Apereo .NET CAS Client.

Configuration

You will need to make modifications to your application's web.config file after installing this NuGet package.

First Modification:

The first modification will be to add the pertinent Memcached configuration elements. This project has a dependency on EnyimMemcached in order to integrate with Memcached. Please see the EnyimMemcached configuration documentation with regards to which pertinent elements need to be added to the web.config file.

Second Modification:

The second modification will be to modify the <casClientConfig> xml element in your web.config file. Specifically we will be changing the proxyTicketManager (if you use that) and the serviceTicketManager XML attribute values.

Set the serviceTicketManager attribute value to: DotNetCasClient.State.MemcachedServiceTicketManager, DotNetCasClient.Memcached

Set the proxyTicketManager attribute value to: DotNetCasClient.State.MemcachedProxyTicketManager, DotNetCasClient.Memcached

Also, don't forget to wire-up the rest of the .NET Cas Client configuration too.

After all that configuration you should be good to go!

Contributing

If you have already identified an enhancement or a bug, it is STRONGLY recommended that you simply submit a pull request to address the case. There is no need for special ceremony to create separate issues. The pull request IS the issue and it will be tracked and tagged as such.

This project follows the GitFlow branching/workflow model. As such, please base all of the code changes in your pull request off of the develop branch in our repo. We will merge your pull request, if accepted, into our develop branch.

Also take a look at the Apereo Contributor Guidelines article for an more information about contributing.