Skip to Content
0
Former Member
Sep 11, 2013 at 09:07 AM

HTTP 401 when testing RFC Destination Type G

728 Views

Hello,

I have a problem with a RFC Destination of type G that I want to use in a HTTP adapter in PI 7.1.

It is configured in SM59 to a path on a server that needs user/password authentication via HTTPS. The service number is 443 and I already tested that this is the correct port. In the logon&security tab I am using "No Logon", but also with basic authentication I get the same error. SSL is active and the server certificate is imported in the default PSE. This works because before that I got a HTTPIO_PLG_CANCELED error. My problem now occurs when testing the connection.

When I click Connection Test I am prompted a user and password for the correct Resource (Realm). So my assumption is that ABAP connects to the server correctly and receives the request to authenticate. But when I enter the correct user and password it re-prompts 2 more times and then shows "HTTP 401" as result. The Response Text contains:

<h1>Authorization Required</h1> <p>This server could not verify that you are authorized to access the document requested.  Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.</p>

The only thing I can think of is, that maybe a special character in the password is not sent correctly. Is there a known bug?

I hope you can help me with this. Please let me know if you need further information.