Connector authentication issues

[Former Member]

I've got what I hope is a simple authentication / authorization issue.

I am trying to use the .NET connector V2.0 to call various BAPIs on our CRM system.

I've set up a server connection in Server Explorer to the CRM system and can see various BAPIs. In this particular case the BAPIs are in the functional group "SU_USER"

For reference I have set the connection as follows:

Client: 0

ConvertPasswordToUpperCase: False

HttpPath: /sap/bc/soap/rfc

httpPort: 80

HttpProtocoll: http

SAPGui: 0

SNCMode: False

SystemNumber: 0

UseSoap: False

I am also using jre 1.3.1_02-b02

(originally I had 1.5.x but noted that the installation documenation specified 1.3.x so I revereted back)

To test out my ability to call these BAPIs and get some data back I am dragging the "BAPI_USER_GETLIST" function over to my proxy "SAPProxy1.sapwsdl"

It then immeditately pops up the "Retrieving Data" window and then an error pops up"

<b>INFO: using logging implementation "AII Logging"

Exception in thread "main" com.sap.aii.upload.LoginException$WrongPassword: Invalid User/password combination

at com.sap.aii.upload.sap.SAPConnection.connect(CAPConnection.java:94)

at Com.sap.aii.upload.sap.SAPConnection <init>(SAPConnection.java:38)

at com.sap.aii.upload.tool.RFC2WSDLTool.getWSDLforRFCs(RFC2WSDLTool.java:81)</b>

Presumably the connector is trying to download the definition for the RFC call and is having authentication problems, however I am not sure where I should start looking.

The fact that I can see the BAPIs in Server Explorer suggests that I have access but perhaps I need additional permissions in order to download the definitions necessary to actually call them.

Any suggestions?

-Sheldon

[Former Member · Accepted solution]

Hi Sheldon,

also please verify the client nr in the connection string

it could also be a cause for the invalid user / password error

a minimal example connection string using custom logon settings :

CLIENT=420 USER=AMIT PASSWD=CHAWATHE LANG=EN ASHOST=10.8.1.63 SYSNR=0

with respect,

amit

[Former Member · Accepted solution]

Interesting! The client I was using was set to 0 ... so it doesn't show up in the connection string!

ex.

USER=dotnet1 PASSWD=CED8WGF2 ASHOST=TORCRMQ1 SYSNR=0

I'll find out what client number I should be using and let you know!

Thx!

[Former Member · Accepted solution]

Whoo hoo!

That was it! As soon as I found out the correct client number it solved the issue!

And the moral of the story is ... it helps to know something about SAP when you actually trying to connect to it

Thanks Amit!

[Former Member · Accepted solution]

Hi Sheldon,

thank you for the 'solved problem' reward points

glad to help out

with respect,

amit

[Former Member]

Hi Sheldon,

thank you for the 'helpful answer' reward points

with respect,

amit

[Former Member]

Hi Sheldon,

how are you doing ?

what version of CRM are you using ?

the older ones [i use CRM 3.0] needed the password to be in upper case

it is the reason for the convert password to uppercase functionality

also the password can be upto 8 characters long

with respect,

amit

[Former Member]

Thanks for the idea Amid!

Unfortunately that doesn't seem to be the problem ...

The specs on our CRM system are as follows

<b>CRM 3.1 SP4, Basis 620 SP60. The Cross-App framework is also 620 SP60</b>

I confirmed that the password IS in upper case and 8 characters long.

This morning I am going to have our admin completely remove any restriction on the account I am using so I can see whether this is a security issue or not.

Please let me know if you think of anything else.

Cheers,

-Sheldon

[Former Member]

<b>Question:</b>

Does the connector use JCO under the hood? I am guessing it must since it requires JRE.

If so, how would I ensure that JCO is making the RFC calls using the userID and password I specified in the connection properties in Server Explorer.

Another minor issue is that the server I am trying to communicate with isn't listsed in my SAPLOGON.INI so the destination type is set to "Custom Logon Setting" ... not sure if that makes an issue.

[Former Member]

>> I confirmed that the password IS in upper case and 8 characters long.

>> This morning I am going to have our admin completely remove any restriction

>> on the account I am using so I can see whether this is a security issue or not.

what kind of restriction are currently in place ?

the password restriction is as far as i know a system wide protocol

no other restriction : group , permission, role would give a similar error message for any dialog / service user

you could run a test by creating a test / service account

for this particular system, i would recommend the 'convert to uppercase', to save the user the hassle of using the upper case & terminate at 8 characters, to replicate the functionality of SapGui for this scenario

>>Does the connector use JCO under the hood? I am guessing it must since it

>>requires JRE.

NCo is dependant on the JRE for design time generation of proxies

At run time :

it uses librfc32.dll to communicate with the SAP system [again similar to SAP GUI / LogonPad]

>> Another minor issue is that the server I am trying to communicate with isn't

>> listsed in my SAPLOGON.INI so the destination type is set to "Custom Logon

>> Setting" ... not sure if that makes an issue.

Custom logon setting : only means that you will not be going via SAP router, it does not matter, as long as the connection string that is generated is valid and the application host port is accessible from the client-application host

with respect,

amit