SSO Compatability between .msc to BTDF way

Topics: General Questions
Sep 29, 2016 at 7:51 PM
At current client, they didn't opt for BTDF at first, but they did go for SSO for config variables.

We use c:\Program Files (x86)\Microsoft Services\SSO Application Configuration\SSO Application Configuration.msc tool to update the SSO, and we have our own C# routines to access it.
[That utility is available here:].

So now we have maybe 5 or 6 BizTalk Apps using that, and now we have our first potential BTDF app. I know you're not bored and looking for things to do, but it would be really nice if there was a switch in the whole SSO code to use the "standard" format, rather than the BTDF format.

They are essentially the same, a bunch of key/value pairs. Except I think you pack them in an XML and stuff them in one SSO key/value pair, where as the utility above put each one in a separate key/value pair.

So for now, I'm thinking we just turn set <IncludeSSO>False</IncludeSSO> and continue to do the SSO like we've been doing for consistency.

The above .msc approach has several downsides

1) When you export from one environment to another (using the .msc above), the export file is encrypted and you cannot edit it with notepad. So what we sometimes do is edit the values on QA to PROD, export, then change them all back.
2) And of course, it doesn't integrate to your EnvironmentSettings.xml spreadsheet.

I realize there probably aren't many people in this situation, and it probably doesn't warrant any changes on your side, but it never hurts to mention it.

Neal Walters