Closed tfabraham closed 6 years ago
[tfabraham@2/18/2014] The Microsoft SSO snapin stores each config setting as a separate field within the SSO app. This makes sense with the GUI, but is a bit trickier for the Deployment Framework. The Framework's source for the settings is generally a settings spreadsheet, which can be edited at any time to add, remove or change settings. SSO requires that all fields be defined before use, so each setting in the spreadsheet would have to be added to SSO as a field. This creates a synchronization headache, because each import would have to examine which fields are currently in SSO, compare to the incoming set from the spreadsheet, then add, remove or modify fields in SSO as needed.
There is not sufficient benefit to justify the development and testing effort, particularly since the Deployment Framework already provides an SSO GUI editor on the BizTalk servers.
[UnknownUser@2/18/2014]
Issue closed by tfabraham with comment Too much effort for no compelling benefit
Reason closed Declined
Attempt to make Deployment Framework SSO apps compatible with Microsoft's SSO snapin.
This work item was migrated from CodePlex
CodePlex work item ID: '10068' Vote count: '2'