Enterprise Single Signon component in BizTalk Server can be used to provide single signon capabilities, as the name suggests, where in the mapping of non-windows credentials can be done to windows credentials and so on. Ent SSO can also be used for storing any application specific configuration data that needs to be encrypted and should to be kept secure. You also may rely on Ent SSO for storing any non-secure configuration data for a BizTalk application if you do not want to put that in BizTalk configuration file (BTSNTSvc.exe.config or BTSNTSvc64.exe.config) as it requires host instances restart to reflect the changes you make. Ent SSO provides a quick and reliable way to store and retrieve data. However you should be careful for not using this for storing any transactional data as it can be too heavy on the enterprise single sign-on server.
In this blog, we are going to talk about new utility “SSO Configuration Application MMC Snap-In”. This snap-in is available for download here.
Here is the overview of the snapin (taken from the documentation):
The downloaded zip file extracts to 3 another zip files:
– SSOMMCSnapInSetup.zip: Extracts to setup and msi file for installing mmc snapin.
– SSOConfigurationApplicationClientHelper.zip: Extracts to SSOClientHelper.cs that can be used in your application to read the values stored in SSO.
– SSOConfigurationApplicationMSBuildImportTask.zip: Contains MSBuild custom task that can be used to automate the deployment of your applications’ SSO configuration data. All you need to do is export the application and then use the MSBuild task to automatically import it into your environment
Attached screenshot (SSO Application Configuration Snap In Screenshot.png) shows how the snap in looks like after installation. I have created a dummy application called POApplication and a key-value pair in the application called SQLConnectionString.
Please do leave comments, if any questions or issues or suggestions. Thanks!