Skip to Content

SSL / User Authentication issue when consuming Web Service - Consumer Proxy

Dec 21, 2016 at 11:28 AM


avatar image
Former Member


I'm trying to consume an SSL webservice from non-sap system and I am struggling with SSL certificates and user/authentication.

I have the consumer proxy correctly configured in SOAMANAGER (I think), but when I call the webservice 2 problems occur:

If I have the configuration in SOAMANAGER as in the picture:

I am able to call the webservice and establish connection, but then always asks for the user ID and Password in the T-CODE that calls the webservice to login to the external system:

But I do not want the popup to appear. The user and password should be inserted automatically.

However, if I change the configurations in SOAMANAGER to:

We get an error on the SSL handshake:

Is there anyway in SOAMANAGER to have both X.509 SSL and User/Authentication?

Or is the SSL option available anywhere else? Am I missing some configuration?

Our basis team have configured all SSLs on STRUST and confirm all required SSLs are properly installed.

Thank you for your help.

config-x509.jpg (30.7 kB)
popup.jpg (21.8 kB)
configuser.jpg (26.5 kB)
ssl-error.jpg (69.7 kB)
trace.jpg (55.1 kB)
trace.jpg (111.8 kB)
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Jonatan Sanchez Jan 10 at 03:13 PM


I have exactly the same problem, I am unable to avoid the user/password popup when consuming the service, but when it is created via an RFC connection from SM59 it works fine.

Did you manage to solve the problem?

Show 2 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Jonatan,

We are also facing the same, could you please provide the steps about solution...




Hi Mohammad,

The solution was to install the certificates into the SSL Anonymous folder on Trust Manager. Then select Username/password in SOAMANAGER. This way, we provide an username, a password and the system finds the necessary certificate inside the Anonymous folder. We couldn't find another way to manage this. I hope this is helpful for you as well.