A hotfix is available that enables user impersonation and logon tickets when you use Microsoft BizTalk Adapter 3.0 for mySAP Business Suite, which is included in Microsoft BizTalk Adapter Pack 2.0, to connect to an SAP system.
Support for impersonation in a SAP Secure Network Communications (SNC) environment
SAP supports impersonation by providing two connection string properties: EXTIDDATA
. An SAP user who is using SNC can impersonate another SAP user who is identified by EXTIDDATA
, such as a username or a token. The EXTIDDATA
property is specified by EXTIDTYPE
The SAP adapter supports impersonation by providing the following two new binding properties:
binding property specifies the valid SAP user who will be impersonated. The value for this property can be a username, a token, and so on. For example, a value for this property could be in the form of domain\username.
binding property indicates the kind of external identification specified for the ExternalIdentificationData
binding property. The SAP adapter only supports NT as a valid value for the ExternalIdentificationType
- You should only specify the two binding properties when you are using SNC to authenticate a user against the SAP system.
- You need to set the UseSnc parameter in the connection URI to enable SNC.
Support for logon tickets
The SAP system issues logon tickets to enable Single Sign-On on other systems. After SAP authenticates a user, it issues a logon ticket that can be used on other systems for authentication. Therefore, users do not have to provide a user name and a password for authentication.
The SAP adapter enables adapter clients to connect to an SAP system by using logon tickets. The SAP adapter supports logon tickets by providing the following two new binding properties:
binding property specifies the type of logon tickets, and has the following possible values:
- The None value specifies that logon tickets will not be used for authentication. This corresponds to the default behavior of using a user name and a password for authentication.
- The MYSAPSSO1 value specifies that the MYSAPSSO1 ticket type be used for authentication.
- The MYSAPSSO2 value specifies that the MYSAPSSO2 ticket type be used for authentication.
binding property specifies the actual ticket string for the logon ticket type.Notes
- Logon tickets should not be used if you are using SNC for authentication.
- Logon tickets are not supported when you are using the SAP adapter with BizTalk Server.
Cumulative update information
The hotfix that resolves this issue is included in Cumulative Update 1 for BizTalk Adapter Pack 2.0.
For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 2444952
Cumulative update package 1 for BizTalk Adapter Pack 2.0
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note
If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: - Note
The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
You must have Microsoft BizTalk Adapter Pack 2.0 installed to apply this hotfix.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone
tab in the Date and Time
item in Control Panel.
32-bit version of Microsoft BizTalk Adapter Pack 2.0
|File name||File version||File size||Date||Time||Platform|
64-bit version of Microsoft BizTalk Adapter Pack 2.0
|File name||File version||File size||Date||Time||Platform|
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about working with BizTalk Adapter 3.0 for mySAP Business Suite binding properties, visit the following Microsoft Developer Network (MSDN) Web site:
For more information about configuring a physical port binding to the SAP adapter, visit the following MSDN Web site:
For more information about how to enable SNC in a SAP connection, visit the following MSDN Web site:
For more information about security considerations between the SAP System and the adapter, visit the following MSDN Web site:
To obtain this feature for Microsoft BizTalk Adapter 3.0 for mySAP Business Suite that is contained in BizTalk Adapter Pack 1.0, apply the hotfix package that is described in the following Microsoft Knowledge Base article:
FIX: Description of a hotfix that enables Microsoft BizTalk Adapter 3.0 for mySAP Business Suite to support user impersonation and logon tickets while connecting to SAP systems
For more information about the BizTalk Server hot fixes, click the following article number to view the article in the Microsoft Knowledge Base:
Information on BizTalk Server hot fixes