SOAP Sender Adapter gets error '(401) Unauthorized.'

Hi all,
we are using XI 3.0 and have a scenario with a SOAP Sender Adapter, which is using "HTTPS with Client Authentication". I have configured everything I have found on the forum at Visual Admin and Integration Directory:
Set the UME property ume.logon.allow_cert to TRUE in 'Service-->UME Provider'
Imported client certificate and root CA certificate to 'Service-->Keystore'
Created user with role role SAP_XI_APPL_SERV_USER
Assigned this user to the client certificate in 'Security Provider-->UserManagement'
Added the user to xi_adapter_soap_message and xi_adapter_soap_help in 'Security Provider'
Added the root CA in 'SSL Provider>Dispatcher>Client Authentication' and marked 'Request client certificate.
Added the user to BusinessSystem at tab 'Assigned Users'
Added the user to Sender Agreement at tab 'Assigned Users'.
Our business partner got a certificate of our server and the according PrivateKey is added to 'SSL Provider>Dispatcher>Server Identity'
Unfortunately, our server certificate is not verified by an root CA!!
When the business partner now browse the URL 'https://url:port/XISOAPAdapter/MessageServlet?channel=:BS_3RD_PARTNER:SOAP_SENDER&nosoap=true' on his system, he will get a 'Message Servlet is in Status OK'.
But when he tries to process the URL directly in his messaging system, he gets an error '(401) Unauthorized.' 
Any hints what could be the problem between browing the URL in InternetExplorer and sending from the messaging system?
Does it really mean that authorization was successful, when getting  'Message Servlet is in Status OK' in the Browser?
How can I assign an user when not using ClientAuthentication?
I would be very thankful for every help...
Grtz, Juergen

Hi Satish,
could the user or password also be wrong, even if you get 'Message Servlet is in Status OK' when browsing the URL in the Internet Explorer? I would have seen this as a sign, that the user authentication works basically...
Is there a special place to store the password in the Visual Admin, or will the password be used, which is available in the SU01 ?
Grtz,
Juergen

Similar Messages

  • OBIEE 11.1.1.7 SSO for Windows Native Clients Error 401-UnAuthorized issue.

    I configured OBIEE to work with AD authenticator and AD authentication works fine. My AD users can login with their credential. I am having issues with Kerberos authentication. My keytab looks fine and kinit is successful too and do not have any duplicate SPNs. After configuring Kerberos, "I am getting error 401 Unauthorized" .
    I have an AD user bisystem which I generated SPN and key tab looks fine. My other AD users belong to AD group "Technical".
    What should be the principal-name in weblogic.xml?
    I have put <principal-name>bisytem</principal-name>
                     <principal-name>Technical</principal-name> in weblogic.xml

    from bi_server.out:
    default etypes for default_tkt_enctypes: 17 23 3 1 23.
    Pre-Authenticaton: find key for etype = 3
    AS-REQ: Add PA_ENC_TIMESTAMP now
    >>> EType: sun.security.krb5.internal.crypto.DesCbcMd5EType
    >>> KrbAsReq calling createMessage
    >>> KrbAsReq in createMessage
    >>> KrbKdcReq send: xxxx  timeout=30000, number of retries =3, #bytes=270
    >>> KDCCommunication: kdc=xxxx #bytes=270
    >>>DEBUG: TCPClient reading 106 bytes
    >>> KrbKdcReq send: #bytes read=106
    >>> KrbKdcReq send: #bytes read=106
    >>> KdcAccessibility: remove xxxxx
    >>> KDCRep: init() encoding tag is 126 req type is 11
    >>>KRBError:
             sTime is Wed Apr 15 13:32:41 EDT 2015 1429119161000
             suSec is 553936
             error code is 14
             error Message is KDC has no support for encryption type
             realm is xxxx
             sname is krbtgt/xxxxx
             msgType is 30
                    [Krb5LoginModule] authentication failed
    KDC has no support for encryption type (14)
    Any insight???

  • Receiver SOAP Adapter Problem-HTTP 401 Unauthorized

    We are using XI-7.0. We have scenario IDOC >> XI >> SOAP by making asynchornous call.
    Vendor has two web server - A and B. Both the servers set up are identical in the vendor system.
    Web server "A" works fine from XML spy tool as well as XI for sending service order SOAP messages.
    Web server "B", we are able to send SOAP messages from XML spy successfully and vendor also confirms that it updates database in their system.
    But we are not able to send SOAP messages from XI on Server "B". We are getting following error message in the adpter engine.
    Can someone please help me?   Thanks!
    <i>SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
    MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
    Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
    Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized.</i>
    Thanks!
    MP

    Hi Riya,
    For SSL configuration you can check,
    Rajendra's blog http://scn.sap.com/people/rajendra.badi/blog/2011/11/23/pi-711-transport-level-secuirty-communicating-with-external-web-service-from-soap-adapter-through-ssl
    Khade's blog http://scn.sap.com/people/s.khade/blog/2011/09/06/secured-connection-to-external-web-service-using-sap-xipi.
    Regards.

  • SOAP Asynch Message Giving HTTP 401 Unauthorized error

    Hi experts,
    <Br>
    We are sending ORDERS IDOC Asynchronously from ECC To XI and XI is sending it to Vendor using SOAP.
    This interface was working OK and now we had HTTP 401 error. Checked URL,Username and password to the Vendor. It looks OK. It is working OK if I try it in browser.
    </br>
    <Br>
    I tried to refresh the object by changing values and reactivating,did cache refresh..Still didn't work.When I try to check for the problem found J2EE_GUEST user was locked.Same was unlocked and tried again.
    </BR>
    <BR>
    This IDOC is requesting for acknowledgement( trying to suppress ack by running IDX_NOALE).
    But now I need to reprocess these failed messages.I was trying in different ways and it is not going thru.
    Any pointers are really appreciated.
    </BR>
    Adapter Engine Log is as follows:
    <BR>
    2009-10-27 16:37:30 Success The message was successfully retrieved from the receive queue.
    <BR>
    2009-10-27 16:37:30 Success The message status set to DLNG.
    <BR>
    2009-10-27 16:37:30 Success Delivering to channel: CC_ORDERS05_TO_XYZ_SOAP
    <BR>
    2009-10-27 16:37:30 Success MP: Entering module processor
    <BR>
    2009-10-27 16:37:30 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    <BR>2009-10-27 16:37:30 Success SOAP: request message entering the adapter with user J2EE_GUEST
    <BR>2009-10-27 16:37:30 Error Exception caught by adapter framework: SOAP: response message contains an error <BR>XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
    <BR>2009-10-27 16:37:30 Success SOAP: completed the processing
    <BR>2009-10-27 16:37:30 Error SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - <BR>HTTP 401 Unauthorized
    <BR>2009-10-27 16:37:30 Success SOAP: sending a delivery error ack ...
    <BR>2009-10-27 16:37:30 Success SOAP: sent a delivery error ack
    <BR>2009-10-27 16:37:30 Success Acknowledgement creation triggered for type: SystemErrorAck
    <BR>2009-10-27 16:37:30 Success Acknowledgement creation triggered for type: AckNotSupported
    <BR>2009-10-27 16:37:30 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: <BR>response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
    <BR>2009-10-27 16:37:30 Success Acknowledgement sent successfully for type: SystemErrorAck
    <BR>2009-10-27 16:37:30 Success Acknowledgement sent successfully for type: AckNotSupported
    <BR>2009-10-27 16:37:30 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System <BR>failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error <BR>XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized.
    <BR>2009-10-27 16:37:30 Error The message status set to NDLV.
    <BR>
    <BR>Regards,
    <BR>Ramesh
    Edited by: RameshK99 on Oct 28, 2009 1:57 AM

    Can you run a sniffer tool & see the actual reason for 401 unauthorized error? 6172 weblog: Troubleshooting SOAP, HTTP and Mail Adapter Scenarios with TCPGateway by Stefan Grube...
    Generally, 401 unauthorized is when the target system rejects the request...  Also, What type of authentication does the target webservice have.?? B'cos i ran into a similar problem with Ms-Webservice. (they were using NTLM authentication). It works from a browser but not from PI. So we installed SOAP-AXIS adapter to support NTLM based authentication.
    Regards,
    Siva Maranani

  • Call Adapter Error - 401 Unauthorized

    Hi,
    We are using Multi Mapping where it splits 1 message into n messages. The n messages split by this scenario in trun calls another scenario configured in the same PI server using SOAP Adapter.
    The called scenario is SOAP --> Siebel using iWay Adapter.
    When the number of messages split are huge in order of thousands, the server is going for a toss and the called scenaio is failing at Call Adapter Step in IE with HTTP Error 401 Unauthorized. Few of the messages manage to pass successfully.
    Anticipating your valuable inputs.
    Thanks.
    Regards,
    Sudharshan N A

    Hi Sudharshan,
    There can be different reasons for getting HTTP 401: Unauthorized error. As you said, few of the messages are being passed to the called application, I would request you to check the scalability of the Seibel Server.
      Also if you are using a connections from a connection pool, then it may be that the pool itself is getting exhausted, though mostly we get Socket exception/Connection Exception/IO Errors in these cases.
      The other reasons can be that the user you are using to connect Seibel dont have enough permissions. But it is ruled out as you said some messages have been processed.
    If the Seibel server is SSL enabled, and your PI doesn't have any certificate configured, then also you may get such errors.
    Regards,
    Sugata

  • Error while posting messages to SOAP sender adapter SP 13

    Hi Friends,
                    I have configured a SOAP sender adapter in XI 3.0 and is using the URL
    http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to post the messages. When I open the URL in the browser I am getting the error.
    Message Servlet is in Status ERROR
    Status information:
    Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#5 $) bound to /MessageServlet
    Classname ModuleProcessor: null
    Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
    Lookupname for remoteModuleProcessorLookupName: null
    ModuleProcessorClass not instantiated
    ModuleProcessorLocal not instantiated
    ModuleProcessorRemote not instantiated
    But when I test the URL http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to check the communication channel I am getting the right response as below.
    <?xml version="1.0" ?>
    <http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_EBTR_WEBSERVICE:CC_EBTR_WEBSERVICE_SOAP> <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
      <channelID>e7ac884596ea3d088cbfd8b434f942f2</channelID>
      <name>CC_WEBSERVICE_SOAP</name>
      <type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
      <direction>INBOUND</direction>
      <party />
      <service>BS_WEBSERVICE</service>
      </s:ChannelInfo
    I used the http capture to debug, In the 1st case though I am getting "Message Servlet in status error" I am seeing a 200 OK code in the http capture tool. When the message is posted from .net client proxy we are getting a 500 internal server error.
    Am not sure what causes the error ? I saw two notes in SDN related to SOAP - J2EE SP13. We are in SP13. Is this the issue ? Wanted to know your opinion before applying the notes.
    Thanks & Regards,
    Mathew

    ABAP & Java stack was on different SP levels.

  • Getting error as 'Error 401 - unauthorized'

    Hi ,
    I have a af:goImageLink on a .jsff on clicking on which I am supposed to open a screen with print window . Code in .jsff is
    <af:goImageLink text="Print Current Data" targetFrame="_blank"
    icon="/theme/img/print.png"
    partialTriggers="Search"
    disabled="#{viewScope.Bean.printFlag}"
    destination="#{Bean.strPrintPath}"
    id="gil2" styleClass="print_margin_div"/>
    destination sting is the url of the .jspx to be opened for print.
    It is working fine.
    No on the .jspx I need to do data control binding. After doing that when i click on hypelink to open the print screen i am getting erro as 'Error 401 - unauthorized'
    Using Jdev 11.1.1.5.0
    start code in jspx is
    <?xml version='1.0' encoding='UTF-8'?>
    <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
    xmlns:c="http://java.sun.com/jsp/jstl/core"
    xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
    <jsp:directive.page contentType="text/html;charset=UTF-8"/>
    <af:messages id="m1"/>
    <af:outputText value="#{bindings.emptyText.inputValue}" id="ot1"/>

    Hi,
    Have you configured ADF security ? If yes give access to this peg def file as well.
    Thanks
    Prateek

  • Another SOAP Sender adapter "com.sap.aii.af.mp.module.ModuleException" erro

    I am working on a synchronous scenario SOAP <-> XI <-> RFC.
    This worked fine, when I run it without SOAP adapter, direct via XI Pipeline.
    Now I want to use the SOAP sender adapter, but get the error as described below this post.
    As this is a real new XI installation, some patches or updates might be required to make it work. Or some adapter modules ?
    Any suggestions on how to solve this problem will be rewarded.
    What worries me a bit is the line "  " in the error description.
    Extra info: I use SoapSonar as a test webservice client. The error is the message as received in te test client.
    <?xml version="1.0"?>
    <!-- see the documentation -->
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SOAP:Body>
        <SOAP:Fault>
          <faultcode>SOAP:Server</faultcode>
          <faultstring>Server Error</faultstring>
          <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
              <context>XIAdapter</context>
              <code>ModuleUnknownException</code>
              <text><![CDATA[
    com.sap.aii.af.mp.module.ModuleException: either no channelID specified or no channel found for the specified party, service, and channel name, MessageServlet(Version $Id: //tc/xi/645_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#9 $)
         at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:427)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
              ]]></text>
            </s:SystemError>
          </detail>
        </SOAP:Fault>
      </SOAP:Body>
    </SOAP:Envelope>

    Hi Chandravadhana,
    The colon should be there :
    http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
    The inbound address for SOAP messages is: http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
    Under party:service:channel enter the party name, the service name, and the name of the communication channel. If no party has been created, enter the following: channel=:service:channel
    Regards
    Suraj

  • Using SOAP Sender adapter in PI 7.1

    Hi Guys,
    I've created a sync scenario with SOAP sender adapter, but I have troubles with calling it.
    I use following URL: http://<host>:50000/XISOAPAdapter/MessageServlet?channel=:BS_Bus_Sys:CC_SOAP_Test as I did in XI 3.0, but I'm getting error HTTP 400 Bad Request. I'm using the request generated from the IR Configuration.
    Has something changed in 7.1 for this type of scenario?
    Thanks guys,
    Olian

    Hi! Olian,
    I think u r going in a wrong way. The above given URL is wrong and incomplete one.
    The above url comes only after generating the WSDL. You ill gives that URL to ur source team to post their data at which this URL itselfs acts as an Gateway to enter into SAP XI/PI.
    The generated WSDL contains URL like this>>
    "http:// Host:Port/XISOAPAdapter/MessageServlet?senderParty=&amp;senderService=Business Service&amp;receiverParty=&amp;receiverService=&amp;interface=SenderInterfaceI&amp;interfaceNamespace=http://XXXXXXXX" />
    Also follow the below procedure for generating the WSDL.
    Except generating WSDL remaining all development steps are same as creating File to Proxy Scenario.
    CREATING THE WEBSERVICE IN XI :
    1) In Integration Directory, go to Tools tab --> Define Web Services.
    2) Now one Wizard window will opens and follow the below steps:
    Here donu2019t go for the u2018 Proposed URLu2019, instead specify the URL as::
    http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?channel=:<service>:<channel>
    If there is party then ::
    http://host:port/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<channel>.
    3) Specify the Source Messageu2019s Message Interface.and remaining other input parameters.
    4) Specify the Sender Business Serviceu2019s details:
    5) Here, Cross check the details displayed and then click on u2018Finishu2019 button to create the Web Service
    document(WSDL)
    6) Now Save the WSDL code to the local system. At the bottom u ill get URL based on the above input
    URl:
    Note: Here in XI there is no XML Testing tool or SOAP client tool to test SOAP messages. That is why most of the people prefer either ALTOVA XML SPY Tool or SOAP CLIENT TOOL or INFO PATH.
    If your working on PI 7.1 means::
    1) Simply after creating Sender Agreement go to options above to that sender agreement instead of tools menu... and there you can observe 2 options at the bottom side.
    a) PUBLISH in SR
    b) Generate WSDL.
    2) Once after activating your ID componenets just Press or go for option Publish in SR. Then automatically it will generate WSDL and publish that WSDL in the SERVICE REGISTRY. which is latest concept in PI 7.1.
    3) Now by entering authentification details you can able to enter into service registry.
    There are 4 tabs::
    a) Service definitions
    b) Publish
    c) classifications
    d) Manage.
    Go for Service definitions::
    4) Enter your sender SOAP interface and press GO or enter.
    5) Select your interface and then at the bottom u can observe again 4 tabs:
    a) General b) End Points c) classifications d) System Details.
    6) In the general you can able to see your WSDL URL by again entering Authentification details.
    7) Now Click End Points>Test Button>Enter Authentification details-->Seelct your Interface
    Note:: Now you can test your scenario in this WEB SERVICE NAVIGATOR.
    8) There you can enter you can pass your Input data parameters in your SOAP interface and execute or test your scenario here itself without any using of external tool like Altova XML or SOAP client tool.
    I hope the above information will give you a detailed information in generating and testing webservice right.
    Regards::
    Amar Srinivas Eli

  • ASMA in SOAP Sender adapter.

    Hi All,
    Using ASMA under SOAP sender adapter I am trying to get the username of the user . I am referring below links for the same:
    /people/michal.krawczyk2/blog/2009/05/26/pixi-pseudo-principal-propagation (referring this only for getting username)
    getting user name from sopa header
    But while testing through XML SPY , i am getting error :
    Com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Error during parsing of SOAP header.
    Please help??.
    Thanks
    Amit

    Hi.
    I have created WSDL file using below URL:
    http://ISVSAPPIDEV:50100/XISOAPAdapter/MessageServlet?channel=:BS:CC_SOAP_Sender
    Actually its a synchronous SOAP -PI - RFC scenario. When i am pinging the PI through XML spy(ASMA AND Transport Binding is UNCHECKED in soap sender channel)  i am getting the response back from RFC,  but when i am pinging after chking the ASMA and Transport Binding in SOAP sender adapter i am getting this error(the message is itself not reaching the PI):
    Com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Error during parsing of SOAP header.
    Thanks
    Amit

  • Set up https SOAP Sender adapter

    Hello, I am doing the Webservice -- XI --   RFC
    I have successfully configured the whole scenerio and it works when the SOAP Sender adapter is set to HTTP security
    But when I set it to HTTPS without client auth or with I can not get it to work, I redid the wsdl entering in a url of https and get the following error
    Wed Feb 27 11:02:56 PST 2008:ERROR:javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
       javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
            at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
            at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
            at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(Unknown Source)
            at com.sun.net.ssl.internal.ssl.AppOutputStream.write(Unknown Source)
            at java.io.BufferedOutputStream.flushBuffer(Unknown Source)
    via soapui
    Does anyone have any suggestions or documentation or success in successfully setting up the SOAP adapter to use https?
    I also always reward points
    Cheers
    Devlin

    have you checked that:
    https://service.sap.com/sap/support/notes/891877
    https://service.sap.com/sap/support/notes/856597
    * Q: Can I use SSL for my sender adapter?
               A: Yes. Normally, the SOAP adapter servlet runs on the engines HTTP port. But you can activate the engine's HTTPS port so that this servlet can receive messages sent to the HTTPS port. See the documentation about the J2EE engine's security configuration.
    /wg

  • Debug Weblogic 10.0 with 2-Way SSL: Error 401--Unauthorized

    Hi,
    I am working on Weblogic 10.0 with 2-Way SSL configuration. User uses X.509 certificate to login into the system. I have a default UserNameMapper which maps the CN to the a user name in the LDAP user store. User can login without problem. But after user login, when he tries to hit a new page before the original page fully loaded, he will get a "Error 401--Unauthorized".
    I turned on the Weblogic security debug and got the following warning with stack trace. Can anybody help me to figure out what's wrong? How do I troubleshoot this issue? Any help is really appreciated.
    <Oct 31, 2008 7:34:27 PM GMT> <Debug> <SecurityAtz> <BEA-000000> <com.bea.common.security.internal.service.AccessDecisionServiceImpl.isAccessAllowed AccessDecision returned PERMIT>
    <Oct 31, 2008 7:34:27 PM GMT> <Debug> <SecurityAtz> <BEA-000000> <com.bea.common.security.internal.service.AuthorizationServiceImpl.isAccessAllowed returning adjudicated: true>
    <Oct 31, 2008 7:34:27 PM GMT> <Debug> <SecuritySSL> <BEA-000000> <write APPLICATION_DATA, offset = 0, length = 167>
    <Oct 31, 2008 7:34:27 PM GMT> <Debug> <SecuritySSL> <BEA-000000> <write APPLICATION_DATA, offset = 6, length = 1518>
    <Oct 31, 2008 7:34:27 PM GMT> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: WARNING, Type: 0
    java.lang.Exception: New alert stack
         at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
         at com.certicom.tls.interfaceimpl.TLSConnectionImpl.closeWriteHandler(Unknown Source)
         at com.certicom.tls.interfaceimpl.TLSConnectionImpl.close(Unknown Source)
         at javax.net.ssl.impl.SSLSocketImpl.close(Unknown Source)
         at weblogic.socket.SocketMuxer.closeSocket(SocketMuxer.java:449)
         at weblogic.socket.SocketMuxer.cleanupSocket(SocketMuxer.java:795)
         at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:759)
         at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:700)
         at weblogic.servlet.internal.VirtualConnection.close(VirtualConnection.java:327)
         at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1431)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1375)
         at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    >
    <Oct 31, 2008 7:34:27 PM GMT> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
    <Oct 31, 2008 7:34:27 PM GMT> <Debug> <SecuritySSL> <BEA-000000> <close(): 14324285>
    <Oct 31, 2008 7:34:27 PM GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.removeContext(ctx): 7034906>
    <Oct 31, 2008 7:34:27 PM GMT> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
    <Oct 31, 2008 7:34:27 PM GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 19096081>
    <Oct 31, 2008 7:34:27 PM GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
    <Oct 31, 2008 7:34:27 PM GMT> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
    <Oct 31, 2008 7:34:27 PM GMT> <Debug> <SecuritySSL> <BEA-000000> <18691735 SSL3/TLS MAC>
    <Oct 31, 2008 7:34:27 PM GMT> <Debug> <SecuritySSL> <BEA-000000> <18691735 received HANDSHAKE>
    <Oct 31, 2008 7:34:27 PM GMT> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ClientHello>
    <Oct 31, 2008 7:34:27 PM GMT> <Debug> <SecuritySSL> <BEA-000000> <Will use default Mac for algorithm MD5>
    <Oct 31, 2008 7:34:27 PM GMT> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.5 for algorithm RC4>
    <Oct 31, 2008 7:34:27 PM GMT> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Mac: SunJCE version 1.5 for algorithm HmacMD5>
    Thanks,
    Wayne

    I decided to use pki with jaas/custom authentication provider to solve this problem. It works. If you want more details, please let me know.

  • Error 401--Unauthorized when deployed on WL Managed server (10.3.3)

    Hi,
    I created & started a WL-Managed server on my window desktop machine. I deployed to this Managed server, an application which is running without problem on Admin Server. (The managed server is created in the same Domain as that of Admin Server)
    However, when I log on to the application on Managed server & enter the UID & PW I get the Error 401--Unauthorized page. The same security works perfectly well for Admin Server.
    Any clues what could be going wrong.
    Thanks in advance.
    Edited by: Prakash Chavan on Feb 28, 2011 4:57 PM

    Thanks Faisal,
    Here is the log after I add the 2 flags
    <Mar 1, 2011 8:59:30 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server stat
    e changed to RUNNING>
    <Mar 1, 2011 8:59:30 AM EST> <Notice> <WebLogicServer> <BEA-000360> <Server star
    ted in RUNNING mode>
    Mar 1, 2011 9:13:27 AM oracle.jbo.uicli.mom.CpxUtils$Visitor logMainApplicationC
    px
    INFO: zip:C:/JDev11g/Middleware/user_projects/domains/base_domain/servers/Svr0/t
    mp/_WL_user/TestTrackApp_V2.0/77qs7f/war/WEB-INF/lib/_wl_cls_gen.jar!/view/DataB
    indings.cpx
    [JpsAuth] Check Permission
    PolicyContext: [TestTrackApp#V2.0]
    Resource/Target: [view.pageDefs.ttsPageDef]
    Action: [view]
    Permission Class: [oracle.adf.share.security.authorization.RegionP
    ermission]
    Result: [FAILED]
    For more information on this failure, please set -Djps.auth.debug.verb
    ose=true
    I have emailed you the requested log & the config files.
    Edited by: Prakash Chavan on Mar 1, 2011 9:35 AM

  • The remote server returned an error: (401) Unauthorized

    We are attempting to upload a file to SharePoint on Office 365 and get the following error:
    The remote server returned an error: (401) Unauthorized.
    We also tried using NetworkCredentials and that got the following error: The remote server returned an error: (404) Not Found.
    The code is shown below.
    Any idea on to fix this error?
    public
    void uploadDocument(string
    siteurl, string username,
    SecureString securepassword,
    string domain,
    string filestreamPath =
    "NewDocument.docx",
    string serverRelativeUrl =
    "/Shared Documents/NewDocument.docx")
    ClientContext context =
    new
    ClientContext(siteurl);
            //context.Credentials = new NetworkCredential(username, securepassword, domain);
    context.Credentials = new
    SharePointOnlineCredentials(username, securepassword);
    using (FileStream
    fileStream =
    new
    FileStream(filestreamPath,
    FileMode.Open))
    ClientOM.File.SaveBinaryDirect(context,
    serverRelativeUrl, fileStream, true);

    Yes, it has access.  In fact, it has no problem getting the site properties using the code below.  It is just when I am uploading a file that the error occurs.
    public Web getProperties(string
    siteurl, string username,
    SecureString securepassword)
    Web web = null;
    // Starting with ClientContext, the constructor requires a URL to the
    // server running SharePoint.
    ClientContext context = new ClientContext(siteurl);
    // The SharePoint web at the URL.
    web = context.Web;
    // We want to retrieve the web's properties.
    context.Load(web);
    // Execute the query to the server.
    context.Credentials = new SharePointOnlineCredentials(username, securepassword);
    context.ExecuteQuery();
    return web;

  • The remote server returned an error: (401) Unauthorized error while using Microsoft.SharePoint.Client.dll

    I have access to sharepoint site and I have tested this by manually creating the lists and announcements in the sharepoint site.
    now the same thing when I try to do it through the c#.net code it always gives me the following :
    "An unhandled exception of type 'System.Net.WebException' occurred in
    Microsoft.SharePoint.Client.dll Additional information: The remote server returned an error:
    (401) Unauthorized."
    My code looks like below:
    string userName = "[email protected]";
    SecureString password = new SecureString();
    foreach (char c in "abc123".ToCharArray()) password.AppendChar(c);
    using (var context = new ClientContext("https://sharepoint.partners.extranet.adlabs.com/sites/UniTest"))
    context.Credentials = new SharePointOnlineCredentials(userName, password);
    context.Load(context.Web, w => w.Title);
    context.ExecuteQuery();
    Krrishna

    Hi Krrishna,
    You code is used to access SharePoint Online, if you are use SharePoint 2007, we can use SharePoint web service or custom web service to achieve your requirement. 
    Lists Web Service
    http://msdn.microsoft.com/en-us/library/lists(v=office.12).aspx
    Creating a Custom Web Service
    http://msdn.microsoft.com/en-us/library/ms464040(v=office.12).aspx
    About SharePoint 2007(MOSS 2007), you can also post it to the forum below, you will get more help and confirmed answers there.
    https://social.technet.microsoft.com/Forums/en-US/home?forum=sharepointdevelopmentlegacy
    Thanks,
    Dennis Guo
    TechNet Community Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Dennis Guo
    TechNet Community Support

Maybe you are looking for