Problem in server response: [Unauthorized] when calling .Net WS

[Former Member]

Hi all,

<u>Scenario</u>:

I need to call Sharepoint's search Web Service from an SAP EP component.

Currently, I only need one operation out of it - the Query operation.

<u>What I did</u>:

I used the NWDS wizard to create a Portal Service from wsdl (client side).

Since the wizard had trouble with this specific wsdl, I used the wizard on the Google web service as an example, and tried to do the wizard work myself on the Sharepoint WS (implementation, serializers, soapconfig.xml).

I also created an HTTP System with the same system alias and created user mapping for my user.

In the test component I get a secured connection, and verified that my mapped username and password to the systemAlias are correct.

<u>The result</u>:

The SOAP message seems to be created and sent OK, but I get the error <b>com.sap.engine. services.webservices.jaxm.soap.accessor. NestedSOAPException:

Problem in server response: [Unauthorized].</b>

I tried all possible options in the Sharepoint's IIS security settings,

and all possible options in the HTTP System properties,

but nothing seems to work.

Any help will be appreciated.

Thanks,

Yoav.

[Andre_Fischer]

Hi Yoav,

if you want to use SSO using SAP Logon Tickets and the SSSO22KerbMap Module you have to configure the HTTP System such that it sends the SAP Logon Ticket of the currently logged on user.

See also my article:

<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e1f93f5c-0301-0010-5c83-968">Integration of Windows File Servers into the SAP KM platform using SSO and the WebDAV repository mananager</a>

[reiner_hille-doering]

I would suggest that you first check if Sharepoint Webservices support basic authentication (username / password). If yes, it should be possible to configure user mapping to transfer username and password from Java.

Else, the only solution would be the "MYSAP To Kerberos Mapping ISAPI filter". You find information about it in some of the articles written by Andre Fischer. You may also search for "OWA" (Outlook Web Access = the application the filter was built for).