Outbound SOAP Adapter Authentication issue

Hi All,
We have a scenario vendor to ECC (SOAP to Proxy) scenario. They are consuming Xi webservice. Now we don't want to give them the USERNAME and PASSWORD for our Integration Engine. Is there a way we can hard code UserID/Passowrd in the Adapter instead?
Regards,
XIer

Ashish,
>Is there a way we can hard code UserID/Passowrd in the Adapter instead?
No
Cheers
Agasthuri Doss

Similar Messages

  • Sender SOAP Adapter Authentication issue

    All,
    We have a SOAP-XI-RFC scenario. We exported the wsdl from the Integration Directory. When we try to call the web service using webservice studio client. We get the following error. We are using a user that has (SAP_XI_ADMINISTRATOR role on it).
    ResponseCode: 401 (Unauthorized)
    Connection:close
    Pragma:no-cache
    Content-Length:1790
    Cache-Control:no-cache
    Content-Type:text/html
    Date:Fri, 30 Nov 2007 20:01:23 GMT
    Expires:0
    Server:SAP J2EE Engine/7.00
    WWW-Authenticate:Basic realm="XISOAPApps"
    Any thoughts?
    Thanks.

    hi thezone  ,
    <i>ResponseCode: 401 (Unauthorized)</i>
    as per this specific error try checking that
    1.check the wsdl url format
    http://<server>:<port>/XISOAPADAPTER/MESSAGESERVLET?channel=:<Service>:<Channel>
    2. test the wsdl by putting the url in internet explorer and see if you are getting a dialog box for user name and password, also in this step you will confirm the working status of message servlets of web service.
    3. by step 2 IE will send a message to XI, now you check your adapter
    4. test ur xml instance in your soap tester, go to its properties and make sure that  you had given correct user name and password over there on specified fields.
    regarding your soap communication channel it will be activated after receiving first message. you can detect any problem in connection only after receiving first message.
    Regards,
    Mandeep Virk
    reward points if helpful

  • SOAP adapter - authentication

    Hi
    I have a problem with connection to an external service. I use SOAP receiver adapter with authentication (uname & pwd).
    When I connect I get the response "com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized". They say they have authentication method based on this: http://en.wikipedia.org/wiki/Basic_access_authentication. To me it looks like I have to encode the username and password to be able to process the request. Am I correct?
    Question: Can I implement encoded uname & pwd with SOAP adapter?
    If not, what options do I have?
    Thanks!!
    regards Marianne

    Hey
    We have checked that user and password is not expired. And of course I use the standard User Authentication.
    What I was thinking, if I have to use this authentication method: http://en.wikipedia.org/wiki/Basic_access_authentication
    could it be that what I am trying to do can be achieved with HTTP adapter? That should be the last option though...
    regards Marianne

  • SOAP adapter Module Issue

    Hi,
    i had configured a JDBC to SOAP scenario and the SOAP adapter has the Module (localejbs/ReplaceXMLTag)
    now the issue is while execute teh scenario, it works fine at DEV but shows error at QA as given below
    "Delivery exception: Object not found in Lookup of Replace XML tag"
    please let me know how to resolve this issue.
    Thanks in advance....

    > i had configured a JDBC to SOAP scenario and the SOAP adapter has the Module (localejbs/ReplaceXMLTag)
    > "Delivery exception: Object not found in Lookup of Replace XML tag"
    Have you spelled this correct? The name in the error message seems to be different from th module name.

  • SOAP adapter 404 issues

    Dear friends,
    My scenario is web serivce to proxy, and i created the sender interface and relevant sender soap adapter, finally I exposed the outbound service with a web service, the URL is http://hostname:port/ISOAPAdapter/MessageServlet?channel=:servicename:channelname
    After that, i called the web service from XMLSPY, but got the exception information in the response message:
    <faultcode>SOAP:Server</faultcode>
                   <faultstring>Server Error</faultstring>
                   <detail>
                        <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                             <context>XIAdapter</context>
                             <code>ADAPTER.JAVA_EXCEPTION</code>
                             <text><![CDATA[
    com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 404 : Not Found
         at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:158)
         at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:917)
         at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
              ]]></text>
                        </s:SystemError>
                   </detail>
    and then I opened the RWB to find the detail information from message monitoring, the relevant error information are as below:
    2008-09-02 17:20:54     Success     SOAP: request message leaving the adapter (call)
    2008-09-02 17:20:54     Success     Application attempting to send an XI message synchronously using connection SOAP_http://sap.com/xi/XI/System.
    2008-09-02 17:20:54     Success     Trying to put the message into the call queue.
    2008-09-02 17:20:54     Success     Message successfully put into the queue.
    2008-09-02 17:20:54     Success     The message was successfully retrieved from the call queue.
    2008-09-02 17:20:54     Success     The message status set to DLNG.
    2008-09-02 17:20:54     Error     Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 404 : Not Found.
    2008-09-02 17:20:54     Error     Transmitting the message using connection http://hostname:50000/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 404 : Not Found.
    2008-09-02 17:20:54     Error     The message status set to FAIL.
    2008-09-02 17:20:54     Error     Returning to application. Exception: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 404 : Not Found
    Does anybody know what's the problem? I ever cheched the message servlet: http://hostname:port/XISOAPAdapter/MessageServlet?channel=:servicename:channelname, the status is OK.
    Regards,
    Bean

    Dear friends,
    The problem has been finally solved, it's due to the wrong configuration of the pipeline URL in SLD for the integration server, the port should be 80*, not 5*00, thanks to all of you.
    Bean

  • Sender SOAP Adapter Security Issue

    Hi All,
    We are building a SOAP to proxy scenario. The sender is a SOAP Adapter and the receiver is Proxy. The SOAP WSDL and URL is provided to the legacy system. When the legacy system is trying to send the data using the WSDL and the URL provided, they are receiving a dialog box to enter the user name and password. We can create a system user and provide those credentials to the legacy system. However, the legacy folks are not interested in including this in their web service.
    Could you please suggest, if there is a way to create the web service such that it wouldn't request for user credentials? Something like no authorizations in the web service?
    Thanks,
    Manohar Dubbaka.

    Hi Preeti,
    Thanks for the response. Since we are on PI 7.0, I believe the setting that you are referring to should be on Visual Admin. Could you please let us know the parameter or the setting that needs to be changed in VA?
    I am not sure, how we can make use of SSO to prevent them from entering the user credentials. Your help in this regard would be much appreciated.
    Thanks,
    Manohar Dubbaka.

  • Web Service SOAP Sender Authentication issue

    Hi Experts,
    Synch Scenario: Webservice call from SOAP client-> XI -> RFC Bapi call to R/3 and back to SOAP client with data.
    Soap Adapter on J2ee receives and process call ok, the error we are getting is on connection from AFW to IS; the error in the security log is:
    Attempting to create outgoing ssl connection without trusted certificates ,
    Warning , /System/Security/SecureConnectionFactory ,
    com.sap.security.core.server.https.SecureConnectionFactory , 
    Any tips where to look? We have enabled Principal Propagation via assertion tickets following SAP document to carry user id to R3 for authority check when Bapi runs.
    IS self signed cert has been imported to J2ee Ticketkeystore and J2ee cert has been imported to IS Strust/StrustSOO2 store adn added to ACK list. WE are using Http between J2ee and IS...hwoever from the erroe message it looks like it is evaluatiing https library com.sap.security.core.server.https.SecureConnectionFactory ?
    Thanks in advance for any help.
    Margaret

    did u instsall CA in ur visual admin for https/ssl t owork

  • SOAP adapter: WSDL issue

    Hi Experts,
    I am working on File-XI-->Mail scenrio using SOAP adapter. My file contains only one line fields say:
    TATA 407
    I have configered File adapter perfectly and CC of it is showing perferctly green (Data is coming in MONI). On the counter SOAP side, I would like to send this file to the Gmail. But I am not able to do this due to the fact that I am not understanding the WSDL ? I have read several doucments but not one is giving the perfect idea about it.
    Please tell me how to accomplish it. Please avoid to send the links. Please help ASAP.
    -=Soniya=-

    Hi Soniya,
    >>I do agree that Mail adapter can be used in place of SOAP
    No, it's not that.
    SOAP and Mail adapter are two different things. SOAP adapter is used to exchange SOAP messages (do not confuse "message" with "email message") between applications (XI/PI to third pary OR third-party application to XI/PI) using SOAP/HTTP protocol. Whereas Mail adapter is used to send email using IMAP/POP3 protocol.
    >>Somebody is saying that Webservices are the one, where you send your messages either side people are saying.
    Correct. You can configure SOAP adapter as sender in PI and receive SOAP messages in PI sent by some third-party application. OR you can configure SOAP adapter as receiver and post the message form PI to some third-party provided URL.
    For exposing webservice from PI all you need to do is to go to Integration directory. Select the sender aggrement you want to puslish as web service. From TOOLS menu say display WSDL. Save this WSDL and provide it to client/third-party application. They will have to generate the client proxy class and post the message from there to PI.
    For cosuming webservice in PI (posting message from PI), third-party application has to provide you with a URL which you will enter into SOAP receiver type adapter.
    Regards.

  • Synchronous messages through Soap Adapter

    Hi XI Guru's
    In my scenario I am sending a synchronous soap message over soap adapter. Message flow is  like
    3rd Party Application --> XI --> SAP R/3.
    My message do get processed in SAP R/3 and I do get response in SXMB_MONI as well as in Message Monitoring in RWB.
    The return message for message f1bdf1d0-cec5-11de-a9c0-0050569626f6(OUTBOUND) was successfully passed to the waiting "call" thread.
    2009-11-11 05:27:26     Information     The message status was set to DLVD.
    2009-11-11 05:27:26     Information     SOAP: response message entering the adapter (call)
    2009-11-11 05:27:26     Information     SOAP: response message leaving the adapter
    But still the response from XI does not reaches 3rd party application.
    On digging the logs I found following message.  Can this be an issue in XI which is blocking the reponse message from reaching the 3rd Party Application.( I tried posting the message through XML spy and I do get the response in XML spy.)
    (Note : My XI Installation has central adapter engine)
    #1.5 #0050569626F6004200000D0B00000B5000F66675B4B8DEA5#1257401122698#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/com.sap.aii.adapter.soap.app#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#LOVEIN#25369##sapnw03_NPI_6935550#Guest#2fd59d51c9d111debb440050569626f6#HTTP Worker [4]##0#0#Warning##Plain###Cannot send an HTTP error response [500 "Application error occurred during the request procession." (details: &quot;The WebApplicationException log ID is [0050569626F6004200000D0800000B5000F66675B4B8DEA5].&quot;)]. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: *The stream is closed.*
    +     at com.sap.engine.services.servlets_jsp.server.runtime.client.ServletOutputStreamImpl.ensureOpen(ServletOutputStreamImpl.java:354)+
    Any help in this regard is appreciated .
    Thanks
    Lovein

    Thanks for your reply Stephan / Abhishek.
    To add some more info on the issue. This issue is when I am using PI 7.1 version.
    I do not face the issue if I use XI 3.0 and end to end flow works fine and response message reaches 3rd party application.
    Only difference I have in 2 versions is that in XI 3.0 we have been able to disable the soap adapter authentication (by changing web.xml file) where as in PI 7.1 we have not been able to disable that authentication and userid/ password info has to be provided while sending the soap message from 3rd Party application.
    (Security if not disabled gives 401 message as described on following blog [SOAP Sender ADAPTER 401 No Authorisation|SOAP Sender ADAPTER 401 No Authorisation] )
    On the other note do you guys know a way to disable this authentication on PI 7.1 version.
    Thanks ,
    Lovein

  • XI 2.0 Standalone J2SE SOAP Adapter as client - SOAP:encodingStyle

    Hi,
    We're setting up the J2SE SOAP Adapter of XI 2.0 to talk to a synchronous web service provided by a webmethods platform.
    When we generate the Request message using the WSDL and post it directly via the HTTP test tool the message is understood and a response message is returned.
    Here is the Request:
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
      xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <SOAP-ENV:Body>
              <m:callFP091 xmlns:m="http://destserver/FP091.flows" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
                   <iw1_RECTPE xsi:type="xsd:string">String</iw1_RECTPE>
                   <iw1_DLRCODE xsi:type="xsd:string">String</iw1_DLRCODE>
                   <iw1_FRNCODE xsi:type="xsd:string">String</iw1_FRNCODE>
                   <iw1_JOBNUM xsi:type="xsd:string">String</iw1_JOBNUM>
                   <iw1_CHASIS xsi:type="xsd:string">String</iw1_CHASIS>
                   <iw1_COLOUR xsi:type="xsd:string">String</iw1_COLOUR>
                   <iw1_DESCRIP xsi:type="xsd:string">String</iw1_DESCRIP>
                   <iw1_INVNUM xsi:type="xsd:string">String</iw1_INVNUM>
                   <iw1_CAPAMT xsi:type="xsd:string">String</iw1_CAPAMT>
                   <iw1_INTFRE xsi:type="xsd:string">String</iw1_INTFRE>
                   <iw1_LOC_IND xsi:type="xsd:string">String</iw1_LOC_IND>
                   <iw1_REGISTRATION xsi:type="xsd:string">String</iw1_REGISTRATION>
                   <iw1_ENGINE_NUM xsi:type="xsd:string">String</iw1_ENGINE_NUM>
                   <iw1_VIN_NUM xsi:type="xsd:string">String</iw1_VIN_NUM>
              </m:callFP091>
         </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    When we try to use the SOAP Adapter and pass it the following message from XI:
    <m:callFP091 xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:m="http://destserver/FP091.flows"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
    SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" >
              <iw1_RECTPE xsi:type="xsd:string">E1</iw1_RECTPE>
              <iw1_DLRCODE xsi:type="xsd:string">3009838</iw1_DLRCODE>
              <iw1_FRNCODE xsi:type="xsd:string">333</iw1_FRNCODE>
              <iw1_JOBNUM xsi:type="xsd:string">123</iw1_JOBNUM>
              <iw1_CHASIS xsi:type="xsd:string">2</iw1_CHASIS>
              <iw1_COLOUR xsi:type="xsd:string">3</iw1_COLOUR>
              <iw1_DESCRIP xsi:type="xsd:string">4</iw1_DESCRIP>
              <iw1_INVNUM xsi:type="xsd:string">5</iw1_INVNUM>
              <iw1_CAPAMT xsi:type="xsd:string">6</iw1_CAPAMT>
              <iw1_INTFRE xsi:type="xsd:string">7</iw1_INTFRE>
              <iw1_LOC_IND xsi:type="xsd:string">8</iw1_LOC_IND>
              <iw1_REGISTRATION xsi:type="xsd:string">9</iw1_REGISTRATION>
              <iw1_ENGINE_NUM xsi:type="xsd:string">1</iw1_ENGINE_NUM>
              <iw1_VIN_NUM xsi:type="xsd:string">2</iw1_VIN_NUM>
    </m:callFP091>
    The SOAP adapter wraps the envelope and body around this message, provides an empty header but changes the SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" attribute to SOAP:actor='http://schemas.xmlsoap.org/soap/encoding/'.
    The generated SOAP message is:
    <SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
    <SOAP:Header/>
    <SOAP:Body>
    <m:callFP091 xmlns:m='http://196.11.134.83/FP091.flows'
    SOAP:actor='http://schemas.xmlsoap.org/soap/encoding/'
    xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
    xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
              <iw1_RECTPE xsi:type='xsd:string'>E1</iw1_RECTPE>
              <iw1_DLRCODE xsi:type='xsd:string'>3009838</iw1_DLRCODE>
              <iw1_FRNCODE xsi:type='xsd:string'>333</iw1_FRNCODE>
              <iw1_JOBNUM xsi:type='xsd:string'>123</iw1_JOBNUM>
              <iw1_CHASIS xsi:type='xsd:string'>2</iw1_CHASIS>
              <iw1_COLOUR xsi:type='xsd:string'>3</iw1_COLOUR>
              <iw1_DESCRIP xsi:type='xsd:string'>4</iw1_DESCRIP>
              <iw1_INVNUM xsi:type='xsd:string'>5</iw1_INVNUM>
              <iw1_CAPAMT xsi:type='xsd:string'>6</iw1_CAPAMT>
              <iw1_INTFRE xsi:type='xsd:string'>7</iw1_INTFRE>
              <iw1_LOC_IND xsi:type='xsd:string'>8</iw1_LOC_IND>
              <iw1_REGISTRATION xsi:type='xsd:string'>9</iw1_REGISTRATION>
              <iw1_ENGINE_NUM xsi:type='xsd:string'>1</iw1_ENGINE_NUM>
              <iw1_VIN_NUM xsi:type='xsd:string'>2</iw1_VIN_NUM>
    </m:callFP091>
    </SOAP:Body>
    </SOAP:Envelope>
    This message has no SOAP:encodingStyle attribute and is therefore not understood by the WebMethods web service. Here is the error message from the web service:
    [B2BCORE.0076.9201] SOAP Message Coder cannot decode message; no encoding style is specified
    How do I configure the outbound SOAP adapter within the XI 2.0 J2SE adapter engine to add the SOAP:encodingStyle attribute to the outbound message?
    I have tried playing around with the XMBWS.* parameters outlined in the adapter engine documentation but these don't seem to have any influence on the way the SOAP request message is formed.
    Any suggestions would be appreciated.
    Regards,
    -Derek

    Hi,
    You could use the webMethods XI adapter to create the connection.
    Best Regards,
    Sander

  • SP13 : SOAP Adapter Problem

    Hi All,
    Recently we upgraded from SP9 to SP13. Every since we upgraded to SP13 we are experiencing weird problem with Outbound SOAP adapter.
    We have exposed an outbound interface as a webservice, which is consumed by a .Net application. When the .Net application try's to call the webservice, we get soap exception "Server Error".
    To make sure the call is reaching XI, we put in wrong credentials and we got authorization error. So the call is getting to XI.
    Has anyone encountered this weird problem? Any thoughts or suggestions will be very much appreciated.
    Thanks,
    naveen

    Hi,
    There is a tool called SOAPScope from www.Mindreef.com
    Its a webservices diagnostic tool. Use this to troubleshoot.you can get a evaluation for 4 days i guess.
    Regards,
    Sridhar

  • SOAP receiver adapter configuration issue

    Hi Everyone,
    When I am trying to excute a sync scenario from SAP<>XI<>Webservice from Integration engine , I am getting the below error message.
    Error while sending message: com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Cannot process the message because the content type 'text/xml; charset=utf-8' was not the expected type 'application/soap+xml; charset=utf-8'.
    In the receiver SOAP adapter, I have configured Transformation module where I kept the MessageTransformationBean in processing sequence as a priority and also provided the module configuration.
    ModuleKey: transform
    ParameterName: Transform.ContentType
    Parameter Value: application/soap+xml;charset=utf-8.
    But still get the above error message in the communication channel. I am using certificates in my configuration that were deployed in visual Admin.
    In the adapter configuration, I have just provided the Target URL, Configured User Authentication, certificate authentication and SOAP action.
    Can anyone help me.. how to rectify the issue.....
    Thanks in advance,
    Hareen

    HI Hareen,
    I decided to give SOAP1.2 using the standard SOAP Adapter a try
    There are a few noticeable differences between the request message of SOAP1.1 and SOAP1.2
    1.) SOAP 1.1 uses a different namespace from SOAP 1.2. For SOAP 1.1 it is "http://schemas.xmlsoap.org/soap/envelope/" while for SOAP 1.2 it is "http://www.w3.org/2003/05/soap-envelope".
    2.) SOAP 1.2 does not use SOAPAction in its header.
    3.) Content type is also different, for SOAP 1.1 it is "text/xml" while for SOAP 1.2 it is "application/soap+xml"
    So a sample request for SOAP 1.1 would be like this:
    Content-Type: text/xml;charset=UTF-8
    SOAPAction: "http://sampleaction"
    While for 1.2 it is:
    Content-Type: application/soap+xml;charset=UTF-8;action="http://sampleaction"
    The SOAP action is moved to the content type (experts please correct me on this).
    Based on the differences, you need:
    1.) Construct the correct SOAP Envelope for request message mapping and remove it for the response mapping
    2.) Use MessageTransformBean to change content type
    3.) Leave SOAPAction as blank
    I think dynamic soap action is no longer possible because the action is hardcoded in the module configuration (please correct).
    Hope this helps,
    Mark

  • SOAP Adapter (Client Authentication)

    Hi Guys,
    I am trying to follow this blog
    How to use Client Authentication with SOAP Adapter
    Am new to this security settings stuffs , i hear that we have to maintainn keys in visual admin and then later authenticate , am confused all around
    My Question
    1) Who would provide the Key or certificate ?
    2) Should we generate and give it to client r is it given by the client??
    3) Where to maintain these key , i know in visual admin , but what r the steps and which place ?
    $) How to use this to get authenticated with SOAP Sender Adapter ?
    Can any one elobrate this in details and provide any more links on this.
    thx in advance for help
    with regards
    Srini

    HI
    1.These will be provided by th Client or they can be downloaded from the website n then the Basis Team or the System Adminstrator will do the needful for us.
    2.it depends , if the client wishes to give to us he will give or Basis team will be helping us in this Query.
    Digital certificates
    A digital certificate is an electronic "credit card" that establishes your credentials when doing business or other transactions on the Web. It is issued by a certification authority (CA). It contains your name, a serial number, expiration dates, a copy of the certificate holder's public key (used for encrypting messages and digital signatures), and the digital signature of the certificate-issuing authority so that a recipient can verify that the certificate is real. Some digital certificates conform to a standard, X.509. Digital certificates can be kept in registries so that authenticating users can look up other users' public keys.
    Certificates are issued by Certifying Authority(CA) for people or an organization. This is used to identify unique person or unique organization.
    Also look at these links
    http://www.abanet.org/scitech/ec/isc/dsg-tutorial.html
    http://mindprod.com/jgloss/certificate.html
    Please go through these links and i am sure they will help you in some ways.
    http://help.sap.com/saphelp_nw04/helpdata/en/a8/882a40ce93185de10000000a1550b0/content.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/db3d8798-0701-0010-9781-8a6e925dd5da
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/092dddc6-0701-0010-268e-fd61f2035fdd
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b2a56861-0601-0010-bba1-e37eb5d8d4a9
    cheers
    Edited by: vemuganti naga phalguna on Jul 2, 2008 1:00 PM

  • Remove authentication in sender soap adapter pi 7.1

    Hello
    Did anyone manged to remove authentication in PI 7.1 sender soap adapter?
    I have updated file web.xml in the file com.sap.aii.adapter.soap.war
    and now I want to deploy it,but I dont have any sda in the folder
    thx
    Shai

    hi Shai,
    just something to try in case:
    you don't need any java parameters of SOAP sender
    you can try approach from Stefan:
    /people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
    and then:
    1. in SICF copy the engine service to a new one
    2. put the credentials for this new service inside SICF
    then you will have sender SOAP adapter without a password right?
    I didn't try it but I guess it would work without
    crashing the whole original SOAP sender adapter by
    making changes into web.xml
    Regards,
    Michal Krawczyk

  • How to use Basis Authentication in Sender SOAP Adapter

    We implemented one Sender SOAP Adapter and we had to implement the modified WEB.XML method to remove the security specification.  We have now asked the developer to correct this situation so we can remove this modification.  The Interface developer would like to use Basic Authentication. If you have an automated interface sending in a SOAP Message, how do you do Basic Authentication? 
    I've tried using:
    http://host:port/XISOAPAdapter/MessageServlet?channel=:<Service>:<Channel>&sap-user=xiappluser&sap-password=<Password>&sap-language=EN&sap-client=<Client>
    When I do this, I still get the Authentication Pop-Up Window.
    How does the Sending Interface either supply the ID and Password on the incoming SOAP Message or respond to the Authentication Pop-Up?
    Thanks,
    Anne

    By Defualt the web service exposed by you will use Basic Authentication mode only.
    But the way you do Basic Authentication in the web client is platfrom dependent.
    This is not the way to do Basic authentication
    http://host:port/XISOAPAdapter/MessageServlet?channel=:<Service>:<Channel>&sap-user=xiappluser&sap-password=<Password>&sap-language=EN&sap-client=<Client>
    I am providing you a code snippet on how to Basic Authentication in Java when making the Web Service Call.
    If the client is on some other platform just look for the corresponding api.
    Please award points if you find this answer useful.
    Code Snippet
    URL url = new URL(URL);
    URLConnection connection = url.openConnection();
    if( connection instanceof HttpURLConnection )
    ((HttpURLConnection)connection).setRequestMethod("POST");
         //connection.setRequestProperty("Content-Length",Integer.toString(content.length()) );
         connection.setRequestProperty("Content-Type","text/xml");
         connection.setDoOutput(true);
         String password = User + ":" + Password ;
          //Where con is a URLConnection 
         connection.setRequestProperty ("Authorization", "Basic " + encode(User + ":"+ Password));
         connection.connect();
    Encode Method
    public static String encode (String source) {
    BASE64Encoder enc = new sun.misc.BASE64Encoder();
    return(enc.encode(source.getBytes()));

Maybe you are looking for