cancel
Showing results for 
Search instead for 
Did you mean: 

Http Authentication Fails - 401

Former Member
0 Kudos

Hi Everybody,

I successfully configured HTTPS Authentication to my ERP backend in SUP.

Now I wish to change the authentication to point at HTTPS on my Netweaver Gateway. The ERP System Trusts this gateway and so if authenticated things should work ok.

I have verified the HTTPS service on the gateway is active and when I test this in a browser I get a password challenge and everything works ok.

Now, when I test in our APP I am receiving a 401 error back from the Gateway system. This is strange since the URL for authentication is the same as the one tested in a browser.

In the Server logs I see:

2015-07-28 11:25:30.690 WARN Security HttpChannel Thread-372 [com.sybase.security.http.HttpAuthenticationLoginModule] Server responded with the status code "401"

2015-07-28 11:25:30.689 WARN Other HttpChannel Thread-372 [org.apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {negotiate=Negotiate}

It seems like the NWG system is configured differently to the ERP system and is trying to negotiate a more complex authentication protocol.

How can I check this? I have raised a ticket with SAP but as yet their response is not helpful.

Best regards,

Mark.

Accepted Solutions (1)

Accepted Solutions (1)

Kevin_SAP
Advisor
Advisor
0 Kudos

SMP com.sybase.security.http.HttpAuthenticationLoginModule is designed to handle www-authenticate=basic only.  Looks like Gateway is sending www-authenticate=negotiate which I think is NTLM or Kerberos

Former Member
0 Kudos

Hi Kevin,

I think I agree with you, but the service I am calling is not configured to use anything but basic authentication. I'll update this post with any feedback from SAP Support.

Kevin_SAP
Advisor
Advisor
0 Kudos

It's easy enough to trace with an HTTP sniffer or just use Chrome Inspect in a browser with same URL.

Regards,

Kevin


Answers (0)