Dave Burke - If you don't eat yer CS Licenses, you can't have any pudding

If you don't eat yer CS Licenses, you can't have any pudding

Another brick in the wall, Part II

"Wrong, do it again!"
"If you don't eat yer meat, you can't have any pudding. How can you have any pudding if you don't eat yer meat?"
"You! Yes, you behind the bikesheds, stand still laddy!"

There I was on my Single Sign-On Quest, battling the Forces of Evil in the Land of Custom Cookie Authentication when I realized that it was important to touch on CS Licenses as a pre-requisite to installing any of the CS Security Packages. Don't worry, tales of Custom Cookie Enlightenment will follow.

So a few bits and screenshots on CS Licensing.

Before we can install any of the CS Add-Ons or Additional Features we first need a license for Community Server and a license for the Add-On. There's a short video on how to install a Community Server license at cs.org by Telligent's Ken Robertson, which is pretty cool. I'll cover those basics here. A quick step-by-step list on installing a CS License is also found on this CS Forums post.

We start in Administration->System Tools->Manage Licenses.

Select Browse and our license. We need to start with the Community Server license.

Okay. We're good on the Community Server License. In the Cookie Authentication Installation Instructions, it states to install the license after copying the DLLs to the CS \bin directory. This won't be an issue in CS 2.1, but in CS 2.0, we better do what the instructions say in the order they tell us.