...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Table of Contents |
|---|
...
Summary
Yes, SNC/SSO is supported by the Docu Performer for BW.
It is planned for HANA and BO.
...
Are you instead of looking for:
General: My SAP System connection properties has changed
...
Error
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
You have no password; you cannot log on using a password. |
Solution
...
Create a ticket in our Help Desk with your SNC Partner Name of the respective SAP system.
Error
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
ProjectB.SAPConnections.Data.Exceptions.ConnectionFailedToSapException: RfcOpenEx failed(RFC_ERROR_COMMUNICATION) SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed
Connect_PM GWHOST=10.118.169.25, GWSERV=sapgw05, SYSNR=05
LOCATION CPIC (TCP/IP) on local host
ERROR SncPDLInit()==SNCERR_INIT
Unable to load GSS-API DLL
named "GX64KRB5.DLL"
TIME Tue May 28 11:32:09 2019
RELEASE 720
COMPONENT SNC (Secure Network Communication)
VERSION 5
RC -1
MODULE sncxxdl.c
LINE 378
DETAIL LoadLibrary("GX64KRB5.DLL")
Error 126 = "The specified m
at ProjectB.SAPConnections.SapConnectionOpeners.SapConnectionOpenerWrapper.HandleConnectionError(Exception ex, BwConnection connection)
at ProjectB.SAPConnections.SapConnectionOpeners.SapConnectionOpenerWrapper.GetOpenConnection()
at ConnectionTester.Helpers.BwConnectionHelper.ConnectToBW(MainViewModel mainViewModel) |
Solution
...
- Check SAP-Transaction RZ10 for the entry snc/gssapi_lib = 'C:\Windows\System32\xxxxx.DLL'
- Add in your 'Environment Variables' the System variable SNC_LIB_x64 and set the Value to the DLL-name you found in the RZ10.
...
| Widget Connector | ||
|---|---|---|
|
...
More Information
Single Sign-On with Microsoft Kerberos SSP
...
You can use Kerberos to overcome the security weakness characteristic of more basic authentication mechanisms such as user ID and password authentication.
The Kerberos authentication process relies on the exchange of session tickets. The session tickets are issued by a Kerberos Key Distribution Center (KDC) when the user attempts to connect to the AS ABAP. The KDC itself establishes and verifies the user identity and the user is not required to interactively provide a user ID and password for the AS ABAP logon.
As a result of the use of session tickets, the AS ABAP authentication credentials of users are not communicated over the network for the connection between the SAP GUI and the AS ABAP. Thereby, the credential confidentiality and integrity protection are guaranteed.
In addition, Kerberos makes use of several systems in your landscape, which may result in additional administrative effort and costs.
You can use X.509 client certificates to enable secure authentication instead of using the traditional user ID and password-based authentication. The authentication credentials are protected during their transport over the network due to the use of public-key technology in X.509 client certificates.
Users need to receive their client certificates from a Certification Authority (CA), using a Public Key Infrastructure (PKI). If you do not have an established PKI then you can use a Trust Center Service to obtain certificates.
...