Skip to content

Commit 5797f9b

Browse files
GitHubber17ecfan
andauthored
Update articles/logic-apps/connectors/sap.md
Co-authored-by: Esther Fan <ecfan@users.noreply.github.com>
1 parent ccc62ea commit 5797f9b

File tree

1 file changed

+1
-1
lines changed
  • articles/logic-apps/connectors

1 file changed

+1
-1
lines changed

Diff for: articles/logic-apps/connectors/sap.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -571,7 +571,7 @@ For more information about SNC, see [Getting started with SAP SNC for RFC integr
571571
| **SNC SSO** | Select either **Logon using the SNC identity** or **Logon with the username/password provided on RFC level**. <br><br>Typically, the SNC identity is used to authenticate the caller. You can choose to authenticate with a username and password instead, but this parameter value is still encrypted. |
572572
| **SNC My Name** | In most cases, you can omit this value. The installed SNC solution usually knows its own SNC name. In the case where your solution supports multiple identities, you might have to specify the identity to use for this particular destination or server. |
573573
| **SNC Partner Name** | Enter the name for the backend SNC, for example, **p:CN=DV3, OU=LA, O=MS, C=US**. |
574-
| **SNC Quality of Protection** | Select the quality of service to use for SNC communication with this particular destination or server. The back-end system defines the default value, and the security product used for SNC defines the maximum value. |
574+
| **SNC Quality of Protection** | Select the quality of service to use for SNC communication with this particular destination or server. The back-end system defines the default value. The security product used for SNC defines the maximum value. |
575575
| **SNC Certificate** | Enter the base64-encoded *public* key for the certificate to use for identifying your client to SAP. <br><br>**Note**: - Don't include the PEM header or footer. <br><br>- Don't enter the private key for the client certificate here. Your Personal Security Environment (PSE) must contain the matching private key for this certificate and might contain other private certificates. For more information, review the next parameter. |
576576
| **PSE** | Enter your SNC Personal Security Environment (PSE) as a base64-encoded binary. <br><br>- Your PSE must contain the private key for the client certificate where the thumbprint matches the public key for the client certificate in the **SNC Certificate** parameter. <br><br>- Although your PSE might contain multiple client certificates, to use different client certificates, create separate workflows instead. |
577577

0 commit comments

Comments
 (0)