Weblogic 8.1 Webservice Client Proxy Authentication not working

We have a desktop console based Weblogic webservices client application that uses client stubs to establish the connection and communicate with the server where the WSDL was hosted.
We are facing a problem in authenticating the Proxy user with valid credentials.
We are using the following code to set the system properties and Authenticator class to authenticate the proxy user.
//Code Segment #1
Code:
System.setProperty("http.proxyHost", proxyHost);System.setProperty("https.proxyHost", proxyHost);
System.setProperty("weblogic.webservice.transport.http.proxy.host",proxyHost);
System.setProperty("weblogic.webservice.transport.https.proxy.host",proxyHost);
System.setProperty("http.proxyPort", proxyPort);
System.setProperty("https.proxyPort", proxyPort);
System.setProperty("weblogic.webservice.transport.http.proxy.port",proxyPort);
System.setProperty("weblogic.webservice.transport.https.proxy.port",proxyPort);
//System.setProperty("http.proxyType", "basic");
//System.setProperty("https.proxyType", "basic");
//System.setProperty("http.proxy.auth.type" ,"ntlm"); //This is not showing any impact
System.setProperty("http.proxyUser", "bsil\\ashok.kumar");
System.setProperty("https.proxyUser", "bsil\\ashok.kumar");
System.setProperty("http.proxyPassword", " xyzddd");
System.setProperty("https.proxyPassword", "xyzddd");
Authenticator.setDefault(new MyAuthenticator());
//Inner class
public static class MyAuthenticator extends Authenticator {
protected PasswordAuthentication getPasswordAuthentication() {
String username = System.getProperty("http.proxyUser");
     String password = System.getProperty("http.proxyPassword");
     return new PasswordAuthentication(username, password.toCharArray());
We are using following code initialize the stubs (Which internally opens a connection to the given endpoint base URL)
//Code Segment #2
Code:
SessionService_Impl sessionService = new SessionService_Impl(getEndPointURL(SessionServicePort.class));
port = sessionService.getSessionServicePort();
return port;
Using above code it always throws the following exception:
Code:
weblogic.webservice.tools.wsdlp.WSDLParseException: Failed to retrieve WSDL from https://apiclienttest.intralinks.com:443/webservices51/SessionService?WSDL. Please check the URL and make sure that it is a valid XML file [java.io.IOException: Proxy authenticator  failed: java.lang.ClassNotFoundException: ]
if i replace the above code (Code Segment #2) to as bellow with Code Segment #3 then its working as expected. But we have been told that the Code Segment #2 is required as shwon above for the Weblogic ClientTimeout seconds feature so we cant replace the Code Segment #2 with Code Segment #3 since we don?t want to miss the ClientTimeout seconds feature for the application.
//Code Segment #3
Code:
SessionService_Impl sessionService = new SessionService_Impl();
          SessionServicePort sessionServicePort = sessionService.getSessionServicePort();
          ((SessionServicePort_Stub) sessionServicePort)._setProperty("javax.xml.rpc.service.endpoint.address", endPointBaseURL+"SessionService");
return sessionServicePort ;
why the Proxy authentication is failing with the Code Segment #2 and why it is passing in case of Code Segment #3
The endpoint base URL we are hitting is hosted on Weblogic server 9.0 (which is hosted at client side in US so it is behind our firewall).
Is some thing more do we need to do in Authenticator class???
Please help me if any one has worked on proxy server authenticator in java.

We have a desktop console based Weblogic webservices client application that uses client stubs to establish the connection and communicate with the server where the WSDL was hosted.
We are facing a problem in authenticating the Proxy user with valid credentials.
We are using the following code to set the system properties and Authenticator class to authenticate the proxy user.
//Code Segment #1
Code:
System.setProperty("http.proxyHost", proxyHost);System.setProperty("https.proxyHost", proxyHost);
System.setProperty("weblogic.webservice.transport.http.proxy.host",proxyHost);
System.setProperty("weblogic.webservice.transport.https.proxy.host",proxyHost);
System.setProperty("http.proxyPort", proxyPort);
System.setProperty("https.proxyPort", proxyPort);
System.setProperty("weblogic.webservice.transport.http.proxy.port",proxyPort);
System.setProperty("weblogic.webservice.transport.https.proxy.port",proxyPort);
//System.setProperty("http.proxyType", "basic");
//System.setProperty("https.proxyType", "basic");
//System.setProperty("http.proxy.auth.type" ,"ntlm"); //This is not showing any impact
System.setProperty("http.proxyUser", "bsil\\ashok.kumar");
System.setProperty("https.proxyUser", "bsil\\ashok.kumar");
System.setProperty("http.proxyPassword", " xyzddd");
System.setProperty("https.proxyPassword", "xyzddd");
Authenticator.setDefault(new MyAuthenticator());
//Inner class
public static class MyAuthenticator extends Authenticator {
protected PasswordAuthentication getPasswordAuthentication() {
String username = System.getProperty("http.proxyUser");
     String password = System.getProperty("http.proxyPassword");
     return new PasswordAuthentication(username, password.toCharArray());
We are using following code initialize the stubs (Which internally opens a connection to the given endpoint base URL)
//Code Segment #2
Code:
SessionService_Impl sessionService = new SessionService_Impl(getEndPointURL(SessionServicePort.class));
port = sessionService.getSessionServicePort();
return port;
Using above code it always throws the following exception:
Code:
weblogic.webservice.tools.wsdlp.WSDLParseException: Failed to retrieve WSDL from https://apiclienttest.intralinks.com:443/webservices51/SessionService?WSDL. Please check the URL and make sure that it is a valid XML file [java.io.IOException: Proxy authenticator  failed: java.lang.ClassNotFoundException: ]
if i replace the above code (Code Segment #2) to as bellow with Code Segment #3 then its working as expected. But we have been told that the Code Segment #2 is required as shwon above for the Weblogic ClientTimeout seconds feature so we cant replace the Code Segment #2 with Code Segment #3 since we don?t want to miss the ClientTimeout seconds feature for the application.
//Code Segment #3
Code:
SessionService_Impl sessionService = new SessionService_Impl();
          SessionServicePort sessionServicePort = sessionService.getSessionServicePort();
          ((SessionServicePort_Stub) sessionServicePort)._setProperty("javax.xml.rpc.service.endpoint.address", endPointBaseURL+"SessionService");
return sessionServicePort ;
why the Proxy authentication is failing with the Code Segment #2 and why it is passing in case of Code Segment #3
The endpoint base URL we are hitting is hosted on Weblogic server 9.0 (which is hosted at client side in US so it is behind our firewall).
Is some thing more do we need to do in Authenticator class???
Please help me if any one has worked on proxy server authenticator in java.

Similar Messages

  • Client Certificate Authentication not working in OSB 11g

    Hi All,
    I am currently having an issue with getting a 2 way SSL handshake to work in a production environment.
    We have the set up working and fully functional in a Test environment, however when we have deployed the code and made the same config changes in the Production environment, it does nto work when calling the API (the result being as if we were not presenting the client cert to the API).
    All relevant configuration on Weblogic and OSB was performed (Keystore creation / Security Realm - Service Key Provider / Service Key Providers etc) and I believe to be right.
    We can test the keystore using SOAPUI and we get a valid response from the live API.
    We can see the relevant aliases in OSB Service Key Provider so I know that the Security Realm / Identity settings are correct on the Weblogic Server.
    The Test and Production Weblogic properties all look the same for Keystores / Secuirty Realms / SSL etc (expect with live keystores etc).
    As we can see the aliases in OSB when setting up the Service Key Provider, it should just be a matter of setting the 'Authentication' of the business service making the call to 'Client Certificate' and this has also been done.
    Though we always get an authentication error and code, that matched what we would get if we turn off the client cert authentication on the business service in the test environment (i.e not sending the certificate with the request).
    What I really want to know is how can I find out for sure whether we are sending this certificate with our request or not? As I am struggling to find a way to log these details.
    Any input appreciated.
    Jamie

    This is issue has now been resolved.
    It was an environment specific issue rather than anything wrong with the actual code.

  • ABAP client Proxy authentication required

    Hallo, my problem is about ABAP client Proxy authentication.
    Scenario:
    Our Dev. BW MWDCLNT600 queries “forward” a (RetailPro) database (JDBC Receiver C.Channel), by Dev. XI , in order to "drive" data extraction (realized, backward, from RetailPro to BW).
    Forward communication from BW uses a call on ABAP Client Proxy technology (I mean, a BW class implements an XI outbound Message Interface).
    Problem:
    Something changed, we don't know what or where, and since last week everytime you execute the report (F8) you are prompted for an authentication popup.
    Official manual guide is: (ABAP Proxy Generation)
    http://help.sap.com/saphelp_nw04/helpdata/en/ba/f21a403233dd5fe10000000a155106/frameset.htm
    in which you have to manage the 2 properties for credential supplying:
    com.sap.aii.applicationsystem.serviceuser.name
    com.sap.aii.applicationsystem.serviceuser.pwd
    in order to "drive" authentication to Integration Engine.
    In our scenario, ABAP report ZRTP_FLOW_CONTROL drives data extraction query, by a call to execute method
    of class: ZCO_MI_FLOW_CONTROL_OB
    which implements Outbound MI: MI_Flow_Control_OB (...all in SPROXY).
    In SXMB_ADM, XI IEngine URL is correct...
    In Exchange Profile, the 2 properties (see above) are correctly maintained (user: XIAPPLUSER, and password is OK)
    Any suggestion?
    Thanks all in advance!
    Gianluca

    Hi
    I would like to suggest you to change the password in http destination (sm59) configured to comunicate with XI and put another one using UPPER case only. Another thing to check is tx SLDAPICUST. There is a problem in this transaction (I think it is a problem, maybe it's a feature , you need to use password with UPPER there to, and you need to double save the data there (change something, click save, change another thing, click save, and will work, otherwise not). Check tx SLDCHECK to see if connection with SLD and Integration Directory are ok.
    Regards.
    Roberti

  • Dynamically loading client proxy no longer works

    I've got several instances where we need to dynamically load/initialize a WebService client proxy using a URL classloader all within an Applet. The need for the classloader and dynamic loading is due to the seperate jars holding different system modules. One main module can't possible know which submodules are also installed and have WebServices running.
    Instead, the main module reads the location of a class to load and uses a URL classloader to load that class. The loaded class knows about it's own client proxy to use and tries to load the appropriate jar and class. The proxy is successfully found and loaded using the classloader, but pukes during initialization. It appears the RuntimeModeler can't find the generated IsAvailable class even though it exists in the same signed jar that just got loaded and which contains the very client proxy that is trying to initialize itself.
    This process worked fine using 1.5, but no longer works after migrating to 1.6. Am I missing something obvious?
    Classloader: java.net.FactoryURLClassLoader@863cc1
    WebAppMgr.getServiceProxy -> b4 initialize
    class: com.irista.warehouse.webservice.wmscoredata.server.data.IsAvailable could not be found
         at com.sun.xml.internal.ws.modeler.RuntimeModeler.getClass(Unknown Source)
         at com.sun.xml.internal.ws.modeler.RuntimeModeler.processDocWrappedMethod(Unknown Source)
         at com.sun.xml.internal.ws.modeler.RuntimeModeler.processMethod(Unknown Source)
         at com.sun.xml.internal.ws.modeler.RuntimeModeler.processClass(Unknown Source)
         at com.sun.xml.internal.ws.modeler.RuntimeModeler.buildRuntimeModel(Unknown Source)
         at com.sun.xml.internal.ws.client.ServiceContextBuilder.processAnnotations(Unknown Source)
         at com.sun.xml.internal.ws.client.ServiceContextBuilder.completeServiceContext(Unknown Source)
         at com.sun.xml.internal.ws.client.WSServiceDelegate.processServiceContext(Unknown Source)
         at com.sun.xml.internal.ws.client.WSServiceDelegate.createEndpointIFBaseProxy(Unknown Source)
         at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(Unknown Source)
         at javax.xml.ws.Service.getPort(Unknown Source)
         at com.irista.warehouse.webservice.wmscoredata.server.data.WmsCoreDataWS.getWarehouseCoreDataWSPort(WmsCoreDataWS.java:50)
         at com.irista.warehouse.webservice.wmscoredata.client.WmsCoreDataSvcProxy.initialize(WmsCoreDataSvcProxy.java:92)
         at com.irista.ui.webapp.framework.WebAppManager.getServiceProxy(WebAppManager.java:760)
         at com.irista.warehouse.webapps.scheduling.CycleCountParameterPanel.getCycleCountSets(CycleCountParameterPanel.java:309)
         at com.irista.warehouse.webapps.scheduling.CycleCountParameterPanel.refreshAction(CycleCountParameterPanel.java:236)
         at com.irista.warehouse.webapps.scheduling.CycleCountParameterPanel.preDisplay(CycleCountParameterPanel.java:225)
         at com.irista.warehouse.webapps.scheduling.CycleCountParameterPanel.initialize(CycleCountParameterPanel.java:149)
         at com.irista.foundation.webapps.scheduling.TaskTypeParameterPanel.createParameterPanel(TaskTypeParameterPanel.java:473)
         at com.irista.foundation.webapps.scheduling.TaskTypeParameterPanel.refreshAction(TaskTypeParameterPanel.java:147)
         at com.irista.foundation.webapps.scheduling.TaskTypeParameterPanel.preDisplay(TaskTypeParameterPanel.java:331)
         at com.irista.ui.webapp.framework.TabbedAppletPane.changePanel(TabbedAppletPane.java:311)
         at com.irista.ui.webapp.framework.TabbedAppletPane$TabbedChangeListener.stateChanged(TabbedAppletPane.java:385)
         at javax.swing.JTabbedPane.fireStateChanged(Unknown Source)
         at javax.swing.JTabbedPane$ModelListener.stateChanged(Unknown Source)
         at javax.swing.DefaultSingleSelectionModel.fireStateChanged(Unknown Source)
         at javax.swing.DefaultSingleSelectionModel.setSelectedIndex(Unknown Source)
         at javax.swing.JTabbedPane.setSelectedIndexImpl(Unknown Source)
         at javax.swing.JTabbedPane.setSelectedIndex(Unknown Source)
         at javax.swing.plaf.basic.BasicTabbedPaneUI$Handler.mousePressed(Unknown Source)
         at java.awt.AWTEventMulticaster.mousePressed(Unknown Source)
         at java.awt.Component.processMouseEvent(Unknown Source)
         at javax.swing.JComponent.processMouseEvent(Unknown Source)
         at java.awt.Component.processEvent(Unknown Source)
         at java.awt.Container.processEvent(Unknown Source)
         at java.awt.Component.dispatchEventImpl(Unknown Source)
         at java.awt.Container.dispatchEventImpl(Unknown Source)
         at java.awt.Component.dispatchEvent(Unknown Source)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
         at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
         at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
         at java.awt.Container.dispatchEventImpl(Unknown Source)
         at java.awt.Component.dispatchEvent(Unknown Source)
         at java.awt.EventQueue.dispatchEvent(Unknown Source)
         at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
         at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.run(Unknown Source)

    Are you running SP2 R2? This worked for me as well until I upgraded to SCCM 2007 SP2 R2. I am focusing on the "~Doing Account Cleanup" errors in the ccm.log which should happen every 30 days, not every 20 minutes. Those errors have to be related to client push problems. Also, thanks for the reboot suggestion. I realize anytime a computer object is added to a domain security group that has is a member of a local group on the client, that a reboot is necessary on client systems in order to receive a new Kerberos access token but in the case of my test systems, I have explicitly added the computer account to the local administrators group so a reboot is not required. I have a test site in a completely different forest and it behaves almost the same way (doesn't run the "~Doing Account Cleanup" every 20 minutes) but still fails to install the client using the site server's computer account. Must be me!!!   

  • Server proxy is not working

    Hi Experts,
    I have a scenario from jdbc to SAP.I have made serverproxy.The proxy was not working.I have test the proxy backend it is working fine,but i am staring jdbc channel the data was not insert in to the database table in sap.I have checked in sxmb_moni in sap r/3 system is showing scuessfully,but data was not sent to proxy.I have put one break point in the code for debugging the proxy.But data was not comming to breakpoint.Kindly help me.
    Thanks
    Ravi

    Hi,
    Make sure that you have not done any changes in your XI structure recently otherwise regenerate the proxy and then try agin.
    Secondly if you have not done any changes then it's ok. Just one thing, have you used Commit Work just after modifying/inseting the value into database table. If not use this and then try again.
    It seems that smoethig went wrong at R3 side because you said data is successful in R3 MONI, so data is reaching to R3 but not going into proxy.
    When you kept the break point then were you able to see the debugger screen in R3?
    Regards,
    Sarvesh

  • Proxy was not working  in sap r/3

    Hi All,
    I have a scenario from jdbc to SAP.I have made serverproxy.The proxy was not working.I have test the proxy backend it is working fine,but i am staring jdbc channel the data was not insert in to the database table in sap.I have checked in sxmb_moni in sap r/3 system is showing scuessfully,but data was not sent to proxy.I have put one break point in the code for debugging the proxy.But data was not comming to breakpoint.Kindly help me.
    Thanks
    Ravi

    Hi ,
    Please try with this link.
    http://ecohub.sdn.sap.com/irj/scn/index?rid=/library/uuid/b0dec9f5-e9a0-2b10-c1a8-e355d01af932&overridelayout=true

  • Consuming PI Webservice from Webdynpro Java Not working

    Hello SAP,
    Environment: CE 7.2.
    Resolution expected immediately, Helpful answer is highly appreciated.
    Is the namespace should not exceed 60char for PI Webservice, for executing the webservice from Webdynpro Java.
    I tried with all the options in executing the PI Service from Webdynpro Java, None of the options worked. I am facing the below error while I was calling the PI Webservice.
    I don't see any problem from Webdynpro Java, what ever the procedure I have followed is the standard procedure.
    Fortunately when I execute the service from Webservice Navigator, it is working as expected. The same webservice when I consume it from Webdynpro Java it is not working
    Options tried so far:
    1) Published the Services to Service Registry and there by consuming the PI Service from Service Registry - Not worked
    2) Tweaked the URL with few options - Not worked (Tweaking the URL, ex: portType, Binding)
    3) Changing the Business Systems in PI and there after calling the service - Not worked
    4) Initializing the code, instead of creating Service Controller and calling the PI Service - Not worked.
    5) Created a Provider System and tried to call the PI Webservice from Provider System - Not Worked
    For all the Options, I am facing the same error which is provided in the screenshot.
    Below procedure which I have followed for calling the PI Webservice:
    1) Created Adaptive Webservice Model
    2) Provided PI Webservice URL (It prompts for PI System UserId and Password)
    3) Selected Option - No Service Group Configuration
    4) Provided Logical Destination
    6) Completed creation of Model
    7) Added the model as a UsedModel
    8) Right Click on Comp Contr. and selected Apply Template and Created a ServiceController for the model (Entire mapping to comp contr, Initializing the nodes is taken care by Service Contr.)
    9) Created an Template Action button and there by calling execute method which is auto rendered from CompContr..
    10) Build the project.
    11) Activated the code and Run the Application.
    12) Getting the below error which is showed in the message.
    ERROR MESSAGE:
    Exception on execution of web service on destination 'GetPIHRPeopleData' for operation 'SI_CreateHRPeopleData_OS' in interface 'SI_CreatePeopleCompany_OS'

    Hi Sankar,
    If the webservice is working fine in the Wsnavigator then there is some problem with importing the webservice in webdynpro for Java. Please check the required parameter for creating the Adaptive Webservice Model. After adding in the used model and compoent controller binding, you need to write code for to execute the webservice model.
    Please check the code for initialization and execution for the webservice and then test it.
    Best Regards,
    Arun Jaiswal

  • [svn] 1720: Bugs: LCDS-304 - Authentication not working in all cases when using security constraint with NIO endpoints .

    Revision: 1720
    Author: [email protected]
    Date: 2008-05-14 14:50:06 -0700 (Wed, 14 May 2008)
    Log Message:
    Bugs: LCDS-304 - Authentication not working in all cases when using security constraint with NIO endpoints.
    QA: Yes
    Doc: No
    Details:
    Update to the TomcatLoginCommand to work correctly with NIO endpoints.
    Ticket Links:
    http://bugs.adobe.com/jira/browse/LCDS-304
    Modified Paths:
    blazeds/branches/3.0.x/modules/opt/src/tomcat/flex/messaging/security/TomcatLoginCommand. java

    Revision: 1720
    Author: [email protected]
    Date: 2008-05-14 14:50:06 -0700 (Wed, 14 May 2008)
    Log Message:
    Bugs: LCDS-304 - Authentication not working in all cases when using security constraint with NIO endpoints.
    QA: Yes
    Doc: No
    Details:
    Update to the TomcatLoginCommand to work correctly with NIO endpoints.
    Ticket Links:
    http://bugs.adobe.com/jira/browse/LCDS-304
    Modified Paths:
    blazeds/branches/3.0.x/modules/opt/src/tomcat/flex/messaging/security/TomcatLoginCommand. java

  • Social Client & Nokia blogs not working

    from last week social client & nokia blogs not working. Facebook / Twitter / Conversations / Blog etc... are not opening. Get a blank white screen with only option to exit. Surprisingly the social widget is getting updated with posts from both Facebook & Twitter! But if i click to open then its the same issue...

    Thanks Adrian,
    Am from India and using N8.
    First thing i checked is for updates on suite but no luck with that... Not sure if there are updates released which are not made available for users here.
    Any idea on where to check if updates are available here? Or when it would be made available here?
    Appreciate ur help.
    Merry Christmas...
    Cheers
    Staty

  • How to find the error when client proxy is not successfully triggered?

    Hi all,
    I want to consume a .NET service in SAP.
    But when I want to test the client proxy the following error occur:
    GENERAL_ERROR Error duing proxy processing (PART
    UNKNOWN (NULL) )
    Transaction ST11:
    TRACE SOAP RUNTIME - trace records                                                                               
    E CONTEXT 20090518061404.5255720 : CL_SOAP_CONTEXT ->SET_FAULT   
    SOAP runtime fault handling                                                                               
    E SOAP_RUNTIME 20090518061404.5256990 : CL_SOAP_RUNTIME_CLIENT   
    ->EXEC_PROCESSING Exception handling in SOAP runtime                                                                               
    E CONTEXT 20090518061404.5255620 : CL_SOAP_CONTEXT ->SET_FAULT set
    fault loop detected                                                                               
    E SOAP_RUNTIME 20090518061404.5256920 : CL_SOAP_RUNTIME_CLIENT                                   
    .NullPointerException:                                           
    Transaction SM21:
    SOAP Runtime Protocol: SOAP Fault exception occurred in program CL_SOAP_RUNTIME_ROOT==========CP in include CL_SOAP_RU NTIME_ROOT==========CM004 at position 80
    SOAP Runtime Protocol: Exception message: Severe processing error; SOAP fault handling required
    How can I find what's wrong????
    This error logging is not really helpful to me...
    Any ideas?
    regards

    Hello Mr. Bauer,
    Will you please elaborate on your solution to fix this issue?
    We are facing this issue too.
    Thanks in advance.
    Regards,
    Victor

  • Client proxy message not reaching to XI system

    Hi
    I have done one scenario from CRM to FILE. When i am executing the client proxy through my zprogram its executing without any errors. I have checked in SXMB_MONI of CRD system i can see the messages but they are not with successful flag or not with error flag. But in XI system (SXMB_MONI) i didnt find any messages. Could you please tell me what's the problem is?
    Regards
    Sowmya

    Sowmya,
    As you are not getting any message in SXMB_MONI, there can be following possibilities:
    1. There can be some problem in proxy configuration on your CRM system. Please check with your BASIS team that steps give in this blog are properly followed:
    How do you activate ABAP Proxies? 
    2. Make sure that in
    SXMB_ADM     --->integration engine config -
    >change specific attributes....
    The RUNTIME parameter is defined LOGGING and TRACE_LEVEL and the value is 1.
    3. Make sure the queues are registered in Tx: SMQR.
    Further, I do not think that COMMIT statement or anything like that is missing as in that case you should have got a message in SXMB_MONI with a green flag stating that "Commit statement is missing".

  • ABAP Client proxy message not reaching AAE

    Hi Experts,
    I am facing a strange issue in one of my proxy interfaces. ABAP client Proxy is used to post message to AAE in SAP PI 7.3. The messages are being generated and pushed out of ECC successfully. I can see them in the SXMB_MONI t-code with checkered flag. These messages are reaching the Integartion Engine instaed of the Adapter Engine.
    I have configured the following:
    1. Sender / Receiver ID  in SXMSIF:
    2. Configured the corresponding Runtime parameter in SXMB_ADM
    I have few other such ABAp client proxy i/f's which work fine and their message are being sent to the Adapter engine. Howveere, only this one interface is posing a problem. What can be the issue?
    Please advice.
    Thanks in advance.
    Elizabeth.

    Hi Elizabeth,
    It will be great if you could please let me know all the user profile configured in userID of Logon&Security tab of SM59 for connecting ECC system to post the message via AAE.
    I have used
    SAP_XI_APPL_SERV_USER
    SAP_XI_DEVELOPER_J2EE and
    SAP_XI_IS_SERV_USER
    profiles in my UserID for Basic authentication.
    Currently I am doing the same scenario what you have done with integrated configuration.The message is getting failed in ECC with 403 Forbidden error.
    Please help me.
    Thanks
    Ray...

  • VPN Client: proxy identities not supported

    Phase 1 is complete since I see this message in the debug output:
    *Jan 17 19:41:04.618: ISAKMP:(2029):Input = IKE_MESG_INTERNAL, IKE_PHASE1_COMPLETE
    The checking of the IPSec proposal fails because of "proxy identities not supported":
    =[ BEGIN debug output ]====================================================================
    *Jan 17 19:41:04.634: ISAKMP:(2029):Checking IPSec proposal 4
    *Jan 17 19:41:04.634: ISAKMP: transform 1, ESP_AES
    *Jan 17 19:41:04.634: ISAKMP: attributes in transform:
    *Jan 17 19:41:04.634: ISAKMP: authenticator is HMAC-SHA
    *Jan 17 19:41:04.634: ISAKMP: key length is 128
    *Jan 17 19:41:04.634: ISAKMP: encaps is 1 (Tunnel)
    *Jan 17 19:41:04.634: ISAKMP: SA life type in seconds
    *Jan 17 19:41:04.634: ISAKMP: SA life duration (VPI) of 0x0 0x20 0xC4 0x9B
    *Jan 17 19:41:04.634: ISAKMP:(2029):atts are acceptable.
    *Jan 17 19:41:04.634: ISAKMP:(2029):Checking IPSec proposal 4
    *Jan 17 19:41:04.634: ISAKMP:(2029):transform 1, IPPCP LZS
    *Jan 17 19:41:04.634: ISAKMP: attributes in transform:
    *Jan 17 19:41:04.634: ISAKMP: encaps is 1 (Tunnel)
    *Jan 17 19:41:04.634: ISAKMP: SA life type in seconds
    *Jan 17 19:41:04.634: ISAKMP: SA life duration (VPI) of 0x0 0x20 0xC4 0x9B
    *Jan 17 19:41:04.634: ISAKMP:(2029):atts are acceptable.
    *Jan 17 19:41:04.634: IPSEC(validate_proposal_request): proposal part #1
    *Jan 17 19:41:04.634: IPSEC(validate_proposal_request): proposal part #1,
    (key eng. msg.) INBOUND local= 200.40.164.178, remote= 200.40.164.177,
    local_proxy= 0.0.0.0/0.0.0.0/0/0 (type=4),
    remote_proxy= 192.168.101.22/255.255.255.255/0/0 (type=1),
    protocol= ESP, transform= esp-aes esp-sha-hmac (Tunnel),
    lifedur= 0s and 0kb,
    spi= 0x0(0), conn_id= 0, keysize= 128, flags= 0x0
    *Jan 17 19:41:04.634: IPSEC(validate_proposal_request): proposal part #2
    *Jan 17 19:41:04.638: IPSEC(validate_proposal_request): proposal part #2,
    (key eng. msg.) INBOUND local= 200.40.164.178, remote= 200.40.164.177,
    local_proxy= 0.0.0.0/0.0.0.0/0/0 (type=4),
    remote_proxy= 192.168.101.22/255.255.255.255/0/0 (type=1),
    protocol= PCP, transform= comp-lzs (Tunnel),
    lifedur= 0s and 0kb,
    spi= 0x0(0), conn_id= 0, keysize= 0, flags= 0x0
    *Jan 17 19:41:04.638: IPSEC(crypto_ipsec_process_proposal): proxy identities not supported
    *Jan 17 19:41:04.638: ISAKMP:(2029): IPSec policy invalidated proposal with error 32
    =[ END debug output ]======================================================================
    I see that "local_proxy= 0.0.0.0/0.0.0.0/0/0", but it should have the IP address of the router internal interface.

    Well, finally a coleague found the cause of the problem: I had added a "match address" command to the "crypto dynamic-map" for the RemoteAccess VPN.
    The "match address" command must be used only with VPN L2L.

  • Outlook client proxy authentication settings default to basic

    So we are moving our way towards exchange 2013 and something odd keeps happening. When you setup the outlook client (either 2010 or 2013) the proxy authentication settings keep defaulting to basic despite the fact that I have ntlm setup on the cas. This
    then continues prompting users for a username and password. We could definitely teel them to click the remember this password button but I would like to make the upgrade as smooth as we possible can. Here are the settings:
    ServerName                                   ExternalClientAuthenticationMethod      InternalClientAuthenticationMethod
    MAILHUB2                                                                   Ntlm    
                                   Ntlm
    MAILHUB1                                                                  Basic    
                                   Ntlm
    Mailhub1 is the 2010 frontend, mailhub2 is the new 2013. All DNS and autodiscovery is flowing through mailhub2. Thanks for you help!

    Hi,
    From your description, I recommend you use the following cmdlet to check if the ClientAuthenticationMethod is set to NTLM.
    Get-OutlookAnywhere -Server "xxx" |fl ClientAuthenticationMethod
    If no, you can use the Set-OutlookAnywhere -Name xxx -ClientAuthenticationMethod NTLM cmdlet to set it and check the result.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Communication between SOAP and java proxy does not work

    Hi Group,
    i want to proceed following scenario:
    SOAP->XI->JavaProxy
    For that i have created of the message interface of a remote function module my java proxy.
    Calling the java proxy with following scenario works successfully:
    RFC->XI->JavaProxy
    Further, i have created in the integration engine(configuration) my wsdl file. In the SAP
    Netwaever Developer Studio, i have made a standalone proxy project, that is consuming the
    web service out of the wsdl file.
    Testing the web service client with following example works fine:
    SOAP->XI->RFC
    But when i try the scenario SOAP->XI->JavaProxy, i get following rmi exception on client side:
    java.rmi.RemoteException: Service call exception; nested exception is:
    java.lang.Exception:  Element 'Z_GPS_PING.Response' not found in response message.
    at com.demo.sap.MI_WEBSRV_GPS_PING_OUTBBindingStub.MI_WEBSRV_GPS_PING_OUTB(MI_WEBSRV_GPS_PING_OUTBBindingStub.java:86)
    at com.demo.test.TT_Pinger.main(TT_Pinger.java:36)
    Caused by: java.lang.Exception:  Element 'Z_GPS_PING.Response' not found in response message.
    at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.getResponseDocument(MimeHttpBinding.java:942)
    at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1231)
    at com.demo.sap.MI_WEBSRV_GPS_PING_OUTBBindingStub.MI_WEBSRV_GPS_PING_OUTB(MI_WEBSRV_GPS_PING_OUTBBindingStub.java:79)
    ... 1 more
    In the monitoring, the execution of both directions is ok. In the response message, i can see the result of the java proxy.
    Here is the result:
    <ns:Z_GPS_PING.Response xmlns:ns="urn:sap-com:document:sap:rfc:functions">
         <E_RETURNCODE>PINGOK  </E_RETURNCODE>
    </ns:Z_GPS_PING.Response>
    My first thought, was, that i have a problem with the prefix, so i have changed it via xslt transformation into "rfc",
    but it got the same error message.
    Does anyone know, which problem we have here?
    For any hint or suggestion, i would be much obliged.
    Greetings,
    Sigi
    P.S. WAS and Sap Netweave Dev Studio is on patch level 12

    Hi Group,
    the SAP has solved the Problem now.
    The coresponding OSS note is: 862926
    (release date 18.07.05)
    The reason was, that the response payload name wasn't
    "maindocument". For that, the adapter didn't found the payload and returned an emty one.
    Greetings,
    Sigi

Maybe you are looking for

  • Can we configure the new time unit in invoicing plan in OM7R

    SAP has provided the four time units in Define Rules for Date Determination (OM7R) which are 1- Day, 2-Week, 3-Month and 4-Year, I wanted to have the new time unit like "Quarterly" and "Half Yearly". Would somebody guide me on this how to get these n

  • Start managed server on the console problem

    I use the weblogic server 6.1 sp1 on the microsoft NT 4.0 and 2000 server sp2, But i have a problem. When i use the default setting to start the administration server and node managed, Then i try to start the managed server on the console, Then <2002

  • Can't trash files on Windows Server

    I have several .mov files that I created and copied to a Windows server on the network for viewing by my associates. But once they view them I can't trash them. Every time I try I get an error that says "The operation cannot be completed because you

  • Import xml/xsl using javascript

    I had problem in import a xml file with xsl using javascript. CS3 only take the elements in xml without any xsl information when I defined doc.xmlImportPreferences.transformFilename="c:\\sample.xsl"; What else do I need to define to allow CS3 know th

  • Blog Format Different in Safari vs Chrome

    For some reason, my blog is formatted differently in Safari vs Chrome. I am using Business Catalyst to create my blog. I want the Recent Posts and Tags to be on the right side as seen in Chrome, not at the bottom of the page as seen in Safari. What c