ferestation.blogg.se

You can create a Microsoft System Center Operations Manager event to notify you when the master secret server becomes unavailable, and you can then manually promote another SSO server to master secret server and restore the master secret on this server.Īlthough this configuration is not highly available, it can be satisfactory for most scenarios and it is consistent with scaling out the receiving, sending, and processing hosts. You can make the master secret server available in two ways:Īvailable, but not highly available. For more information about backing up the master secret, see How to Back Up the Master Secret ( ) in BizTalk Server Help. If you lose it, you lose the data that the SSO system encrypted by using that master secret. Making the Master Secret Server Availableįor availability of the SSO system, and therefore of the BizTalk Server environment, it is critical that you back up the master secret as soon as it is generated. Therefore, the BizTalk Server environment has a dependency on the availability of the master secret server. However, you cannot encrypt new credentials or port configuration data.

If the master secret server fails, and the SSO service detects the failure in one of its refresh intervals, the SSO service and all run-time operations that were running before the server failed, including decryption of credentials, continue successfully. Every 60 seconds, the SSO service synchronizes the master secret with the master secret server. After a master secret is retrieved, the SSO service caches it.

The master secret server is another SSO service that has an additional subservice that maintains and distributes the master secret.

This encryption key is called the master secret. When an SSO service starts up, it retrieves the encryption key from the master secret server. Each BizTalk server has an SSO service (ENTSSO.exe) that is used for encrypting and decrypting the port configuration data. The port configuration data is encrypted and stored in the SSO database.

Even if you do not use the Enterprise Single Sign-On (SSO) functionality for mapping credentials and single sign-on, SSO is a critical part of the overall Microsoft BizTalk Server infrastructure, because BizTalk Server uses SSO to help secure information for port configuration.