In my last Blog I wrote about the ease of implementing basic Single Sign-on. Today I want to take the chance and time to extend our basic setup. Our setup is currently straight forward allowing the detection of basic web applications. The first step we are going to take is to widen or current implementation in terms of user configuration. Probably you already tried that and there is really no point of no return as we could revert really quickly to our original configuration.

User configuration

The modifcations I have made are the following.

Setting Status Comment
Basic Plug-in interaction \ Allow users to

reveal all passwords in Logon Manager
Enabled This probably should only be available to more advanced users (if it comes to more secure deployments you want to make sure to check “Force re-authentication before revealing user passwords”.
Client-side Interaction \ Log Single Sign-on Plug-in events using Windows event logging Enabled This allows events being transmitted into the Windows event logging.
Licensing \ Allow license to be consumed for offline use Enabled If you have mobile users working on notebooks this setting should be enabled to allow Single Sign-on also to run if the user is not connected to the central store.
Application Support \ Enable support for terminal emulators Depends If you need to support host emulators you should enable this setting.

So now we have still a very basic setup which is now allowing the use of host emulators and the other main change is that we support offline usage of the Single Sign-on functionality. There are still many other settings that needed to be considered in terms of each respective environment.

Application definitions

Our current setup allows us to store passwords for web application if the fields are detected correctly. What if the fields are not detected correctly? Your best friend will become the Application Definition Tool. This tool can be started using the Delivery Services Console or using the Application Definition Tool directly from the Start Menu.

On starting the Application Definition Tool, the first question that we need to find an anser will be about the type of application. We recently made a video public about how to use the Application Definition Tool to define a basic Application Definition. The video can be found here and for more complex applications a series of videos can be found at the following links, or

Happy application defining.