User type "System" - Test

[Former Member]

Dear All,

I am not quit sure if this is the right place for my question....

We have in our ERP System one user which is type system.. an external application needs to connect our system using this user..but it is having problems because apparently user / password is wrong..... we do not think the problem is on SAP side ... but we need to prove this.....Is there some way to test that user and password are OK ?

I will appreciate any idea

Thanks.

FedeX

[Former Member]

Moved to the security forum...

My first guess would be an UPPER-CASE conversion of the password or possibly a special character which is not accepted.

Second quess would be to check for short-dumps (ST22).

Otherwise, which release are you on? Are you familiar with the logon trace procedure?

Cheers,

Julius

[Former Member]

I agree with Julius. Trace that user and see what is going on through ST01. Also, if auditing is enabled, you might get some information from SM20.

Michael

[Former Member]

>

> My first guess would be an UPPER-CASE conversion of the password or possibly a special character which is not accepted.
> Julius

We had experience the same issue, it ended up being the upper/lower case password problem. The problem was fixed on the other end.

How do you prove that it is not SAP? Temporarily change the user type to "dialog" or "service" and logon with the user and password. If you can successfully logon with the correct user and password, the problem is on the external application side.

Edited by: John Navarro on Aug 11, 2009 5:10 PM

[Former Member]

> How do you prove that it is not SAP? Temporarily change the user type to "dialog" or "service" and logon with the user and password. If you can successfully logon with the correct user and password, the problem is on the external application side.

If the user type is incorrect (i.e. DIALOG or COMMUNICATION) then this can be the cause as well, as the system would request that the initial or expired password must be changed, however the external application cannot handle this password change dialog.

Additionally, the system can be instructed to reject any such RFC type of logon with an expired password - bar SYSTEM and SERVICE type users. See RZ11 param rfc/reject_expired_password.

It can also be instructed to reject a current password which is not compliant with the password policy. Again dependent on the user type.

That is why I was asking for the release and SP levels, as there were a few program errors in the beginning, where the system dealt with SYSTEM type users incorrectly.

Cheers,

Julius

[Former Member]

This message was moderated.