Status 403: Forbidden in ESB

Hi All,
We are invoking one REST POST service in ESB and it was working fine and suddenly it stopped working and we are getting the below error
ESB Dispatch failed with error An unhandled exception has been thrown in the ESB system. The exception reported is: "org.collaxa.thirdparty.apache.wsif.WSIFException: [email protected] : Could not invoke 'POSTServicePlan'; nested exception is:
java.lang.Exception: Error in HTTP Post: Status 403: Forbidden: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
Any help is highlt is appreciated.
Thanks,
Nagaraju D

HTTP code 403 is returned from the server hosting your REST service. There should be a reason for that in server logs or somewhere.

Similar Messages

  • I'm trying to upgrade to Mountain Lion and I get an error message that says "server error during download; 403 forbidden. What does this mean, what can I do? I had no problem downloading Lion.

    Trying to upgrad to Mountail Lion and got an error message : 403 Forbidden. What does this mean? What can I do? I had no problem when I upgraded to Lion.

    403 Forbidden HTTP status code in response to a request from a client for a web page or resource to indicate that the server refuses to allow the requested action. In other words, the server can be reached, but the server declined to allow the requested access.
    http://en.wikipedia.org/wiki/HTTP_403
    Could you be using a different Apple ID oe such?

  • Error 403-forbidden from IE5 while authenticating a user through NT Realm

    Hi,
    Before posting this request, I checked the forum until Sep.18 to see if nobody
    else experienced my problem, but in vain.
    I am using WLS6.1Sp1 under NT4
    I would like that NT users for defined NT Primary Domain Controller authenticate
    themselves before accessing a web app. For that, I followed thoroughly the BEA
    Doc to get the config.xml, web.xml, weblogic.xml and filerealm.properties correctly
    configured.
    The <auth-method> is set to FORM. The <security-role> and <security-role-assignment>
    are also set with business roles and principals from the NT PDC. the <security-constraint>
    with all the sub-tags are also defined. etc.etc. When I use the WL console, to
    check users and groups lists, it works fine although it takes a lot of time before
    being displayed (15 to 20 minutes !!!).
    Through a Login.jsp, the user enters his/her login name and password. The result
    is that I get the following message :
    "Error 403--Forbidden
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.4 403 Forbidden
    The server understood the request, but is refusing to fulfill it. Authorization
    will not help and the request SHOULD NOT be repeated. If the request method was
    not HEAD and the server wishes to make public why the request has not been fulfilled,
    it SHOULD describe the reason for the refusal in the entity. This status code
    is commonly used when the server does not wish to reveal exactly why the request
    has been refused, or when no other response is applicable."
    No trace in the log files. No warning . Nothing.
    My questions are:
    1- Has somebody already experienced this?
    2- Could you then help me ?
    By advance , thank you very much.
    Athmani H.
    Note : I can provide you through email the config.xml, web.xml, weblogic.xml and
    filerealm.properties and the concerned .jsp files on demand

    Hi Jerry,
    Many thanks for your interest and your help.
    weblogic.properties file for WLS 6.1 SP1? There is none... I do have a filerealm.properties. I didn't state that I was using a weblogic.properties
    file.
    I checked the URL you proposed. I changed the <Auth-method> from FORM into BASIC.
    A pop-up window is displayed requesting the user to enter username and password.
    The result is that I get a web page displaying an Error 404 --not found.
    Here is the complete error message :"Error 404--Not Found
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.5 404 Not Found
    The server has not found anything matching the Request-URI. No indication is given
    of whether the condition is temporary or permanent.If the server does not wish
    to make this information available to the client, the status code 403 (Forbidden)
    can be used instead. The 410 (Gone) status code SHOULD be used if the server knows,
    through some internally configurable mechanism, that an old resource is permanently
    unavailable and has no forwarding address."
    The message is displayed when the browser tries to resolve the following URL :http://localhost:7001/examplesWebApp/j_security_check
    Having said that, I had already configured the <security-role-assignement> with
    role-name and principals in weblogic.xml, as well as the <security-role> tag in
    web.xml.
    Thanks for your help
    Cheers
    Habib
    Jerry <[email protected]> wrote:
    Hi Athmani,
    weblogic.properties file for WLS 6.1 SP1? There is none... weblogic.properties
    is in WebLogic
    5.1 and lower -- it was changed to config.xml for WLS 6.0 .. what are
    you using your
    weblogic.properties file for?
    Anyways,
    I have gotten NTRealms to successfully work with WLS 6.1, with security
    on a web app, allowing
    NT users to access certain resources. This stuff works.
    Since you can see your users and groups through the console (even though
    it takes a while) I
    think that your NTRealm setup is okay.
    I would guess that you have a problem with your deployment descriptors
    in your web
    application.
    There are quite a few posts in this newsgroup that illustrate how to
    set up security
    constraints on resources in your web app with the deployment descriptors.
    For example, check out
    http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.security&item=6244&utag=
    Let me know how it goes, okay?
    Cheers,
    Joe Jerry
    "Athmani H." wrote:
    Hi,
    Before posting this request, I checked the forum until Sep.18 to seeif nobody
    else experienced my problem, but in vain.
    I am using WLS6.1Sp1 under NT4
    I would like that NT users for defined NT Primary Domain Controllerauthenticate
    themselves before accessing a web app. For that, I followed thoroughlythe BEA
    Doc to get the config.xml, web.xml, weblogic.xml and filerealm.propertiescorrectly
    configured.
    The <auth-method> is set to FORM. The <security-role> and <security-role-assignment>
    are also set with business roles and principals from the NT PDC. the<security-constraint>
    with all the sub-tags are also defined. etc.etc. When I use the WLconsole, to
    check users and groups lists, it works fine although it takes a lotof time before
    being displayed (15 to 20 minutes !!!).
    Through a Login.jsp, the user enters his/her login name and password.The result
    is that I get the following message :
    "Error 403--Forbidden
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.4 403 Forbidden
    The server understood the request, but is refusing to fulfill it. Authorization
    will not help and the request SHOULD NOT be repeated. If the requestmethod was
    not HEAD and the server wishes to make public why the request has notbeen fulfilled,
    it SHOULD describe the reason for the refusal in the entity. This statuscode
    is commonly used when the server does not wish to reveal exactly whythe request
    has been refused, or when no other response is applicable."
    No trace in the log files. No warning . Nothing.
    My questions are:
    1- Has somebody already experienced this?
    2- Could you then help me ?
    By advance , thank you very much.
    Athmani H.
    Note : I can provide you through email the config.xml, web.xml, weblogic.xmland
    filerealm.properties and the concerned .jsp files on demand

  • Error 403--Forbidden- From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1

    I am getting the following error
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.4 403 Forbidden
    The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
    It throws an error when I click on a button which in turn calls form authentication[edit.do] and it fails. LDAP server is configured for group- My Admin. We are using AMAgentFilter
    Its currently working in PRODUCTION WL8 with given configurations, please be noted that we have not changed anything in config files[web.xml/weblogic.xml]
    WEBLOGIC is configured for LDAP Server , i used same credetials to login , i am able to login to welcome screen, but when there is FORM AUTHENTICATION [edit.do], it fails.
    This edit button calls [edit.do]. It fails there. What we need to check for making it working . We are upgarding from WL 8 to WL 10. its working fine in WL8.
    Do we need to provide anything in WEBLOGIC server to configure the group name My Admin
    WEB.XML
         <!-- AM filter used for SSO -->
         <filter>
         <filter-name>Agent</filter-name>
         <display-name>Agent</display-name>
         <filter-class>com.sun.identity.agents.filter.AmAgentFilter</filter-class>
         </filter>
         <filter-mapping>
         <filter-name>Agent</filter-name>
         <url-pattern>/*</url-pattern>
         </filter-mapping>
    <security-constraint>
         <web-resource-collection>
         <web-resource-name>saveAction</web-resource-name>
         <url-pattern>edit.do</url-pattern>
         <url-pattern>update.do</url-pattern>     
         <http-method>POST</http-method>
         <http-method>GET</http-method>
         </web-resource-collection>     
         <auth-constraint>
         <role-name>Admin</role-name>
         </auth-constraint>
    </security-constraint>
    <security-role>
    <description>Admin</description>
    <role-name>Admin</role-name>
    </security-role>
    WEBLOGIC.XML
    <security-role-assignment>
    <role-name>Admin</role-name>
    <principal-name>My Admin</principal-name>
    </security-role-assignment>
    please provide me the checklist to find out the reason for this error.
    1, weblogic server configuration checklist
    2. LDAP Server configuration checklist
    Thanks

    Hi Sandeep M.
    Thanks for your replay,
    Another place means Purchase order standard page is there in that "orders" and " aggriments"  two  tab's are there  under orders Tab  when user click on submitt button
    ex :Go
    when user click on Go button Destination URI=OA.jsp?page=/xxiff/oracle/apps/icx/webui/XXIFFUcmPG&pgType=OrderPG&param={@PoHeaderId}
    same as under aggriments tab
    when user click on  Go button
    Destination URI=OA.jsp?page=/xxiff/oracle/apps/icx/webui/XXIFFUcmPG&pgType=BlanketPG&param={@PoHeaderId}
    This custom page is being called using absolute page path and name not AOL funcation name

  • Error 403--Forbidden - From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.

    Hi, I have a problem with WebLogic Server: 10.3.5.0.
    I need to set that anyone who sees my enterprise application can view the website but not how. I always displays an error.
    The error is:
    Error 403--Forbidden
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.4 403 Forbidden
    The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
    Can you help me?

    When I'm working with web servers, and I've not worked with weblogic for quite a while, it has always been rights that have been the gotcha for the 403 error. You need to make sure that if you want everyone to be able to brouse the given folder, you need public read and execute rights on the contents.

  • WebServices over SSL - 403 Forbidden error

    Hello all,
    I am able to successfully communicate with a SSL enabled .NET webservice using apache-axis in my java code. however, when i
    try the same with weblogic based libs [%bea_home%\server\lib\webserviceclient+ssl.jar] - assume the other jars are ok, i get
    the following exception stack trace:
    Disabling strict checking on adapter weblogic.webservice.client.WLSSLAdapter@55a338
    Set TrustManager to weblogic.webservice.client.BaseWLSSLAdapter$NullTrustManager@fdb00d
    Set HostnameVerifier to weblogic.webservice.client.WLSSLAdapter$NullVerifier@131303f
    Disabling strict checking on adapter weblogic.webservice.client.WLSSLAdapter@6b9c84
    Set TrustManager to weblogic.webservice.client.BaseWLSSLAdapter$NullTrustManager@e1eea8
    Set HostnameVerifier to weblogic.webservice.client.WLSSLAdapter$NullVerifier@131303f
    Got new socketfactory javax.net.ssl.impl.SSLSocketFactoryImpl@18f51f
    Connecting to:www.abc.com port:443
    socket:Socket[addr=www.abc.com/12.345.67.89,port=443,localport=4802]com.certicom.tls.interfaceimpl.TLSConnectionImpl@e35bb7
    Warning: cert chain incomplete
    Warning: cert chain untrusted
    Warning: subject (www.abc.com, OU=Terms of use at www.verisign.com/rpa (c)00, OU=ABC 1, O=ABC inc, L=abc, ST=abc, C=abc) does
    not match server name (null)
    <Jul 27, 2004 10:52:49 AM GMT+05:30> <Info> <WebService> <BEA-220025> <Handler weblogic.webservice.core.handler.ClientHandler
    threw an exception from its handleResponse method. The exception was:
    javax.xml.rpc.JAXRPCException: weblogic.webservice.util.AccessException: The server at
    https://www.abc.com/abcdef/ABCWebService.asmx?WSDL returned a 403 error code (Forbidden). Please ensure that your URL is
    correct and that the correct protocol is in use..>
    A RemoteException has been thrown
    java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: The server at
    https://www.abc.com/abcdef/ABCWebService.asmx?WSDL returned a 403 error code (Forbidden). Please ensure that your URL is
    correct and that the correct protocol is in use.
    Detail:
    <detail>
    <bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">
    </bea_fault:stacktrace>weblogic.webservice.util.AccessException: The server at
    https://www.abc.com/abcdef/ABCWebService.asmx?WSDL returned a 403 error code (Forbidden). Please ensure that your URL is
    correct and that the correct protocol is in use.
         at weblogic.webservice.binding.soap.HttpClientBinding.handleErrorResponse(HttpClientBinding.java:371)
         at weblogic.webservice.binding.soap.HttpClientBinding.receive(HttpClientBinding.java:233)
         at weblogic.webservice.core.handler.ClientHandler.handleResponse(ClientHandler.java:63)
         at weblogic.webservice.core.HandlerChainImpl.handleResponse(HandlerChainImpl.java:230)
         at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:229)
         at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
         at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:444)
         at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:430)
         at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:270)
         at com.webservice.abc.client.proxy.ABCWebserviceSoap_Stub.getABC(ABCWebserviceSoap_Stub.java:113)
         at com.webservice.abc.client.ABC_WS_Client.main(ABC_WS_Client.java:158)
    </detail>; nested exception is:
         javax.xml.rpc.soap.SOAPFaultException: The server at https://www.abc.com/abcdef/ABCWebService.asmx?WSDL returned a
    403 error code (Forbidden). Please ensure that your URL is correct and that the correct protocol is in use.
         at com.webservice.abc.client.proxy.ABCWebserviceSoap_Stub.getABC(ABCWebserviceSoap_Stub.java:118)
         at com.webservice.abc.client.ABC_WS_Client.main(ABC_WS_Client.java:158)
    Caused by: javax.xml.rpc.soap.SOAPFaultException: The server at https://www.abc.com/abcdef/ABCWebService.asmx?WSDL returned a
    403 error code (Forbidden). Please ensure that your URL is correct and that the correct protocol is in use.
         at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:285)
         at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
         at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:444)
         at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:430)END
         at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:270)
         at com.webservice.abc.client.proxy.ABCWebserviceSoap_Stub.getABC(ABCWebserviceSoap_Stub.java:113)
         ... 1 more

    Hi All,
    I am new to webservice programming. I am trying to consume webservice over https. I am using weblogic 8.1 sp2. I am getting http 403 forbidden error. from the log it seems that ssl handshaking is completing.
    Algorithm: [MD2withRSA]
    Signature:
    0000: BB 4C 12 2B CF 2C 26 00 4F 14 13 DD A6 FB FC 0A .L.+.,&.O.......
    0010: 11 84 8C F3 28 1C 67 92 2F 7C B6 C5 FA DF F0 E8 ....(.g./.......
    0020: 95 BC 1D 8F 6C 2C A8 51 CC 73 D8 A4 C0 53 F0 4E ....l,.Q.s...S.N
    0030: D6 26 C0 76 01 57 81 92 5E 21 F1 D1 B1 FF E7 D0 .&.v.W..^!......
    0040: 21 58 CD 69 17 E3 44 1C 9C 19 44 39 89 5C DC 9C !X.i..D...D9.\..
    0050: 00 0F 56 8D 02 99 ED A2 90 45 4C E4 BB 10 A4 3D ..V......EL....=
    0060: F0 32 03 0E F1 CE F8 E8 C9 51 8C E6 62 9F E6 9F .2.......Q..b...
    0070: C0 7D B7 72 9C C9 36 3A 6B 9F 4E A8 FF 64 0D 64 ...r..6:k.N..d.d
    ]>
    <Jan 30, 2006 11:39:29 AM GMT+05:30> <Debug> <TLS> <000000> <SSLTrustValidator r
    eturns: 0>
    <Jan 30, 2006 11:39:29 AM GMT+05:30> <Debug> <TLS> <000000> <Trust status (0): N
    ONE>
    <Jan 30, 2006 11:39:29 AM GMT+05:30> <Debug> <TLS> <000000> <HANDSHAKEMESSAGE: S
    erverHelloDone>
    <Jan 30, 2006 11:39:29 AM GMT+05:30> <Debug> <TLS> <000000> <write HANDSHAKE off
    set = 0 length = 134>
    <Jan 30, 2006 11:39:29 AM GMT+05:30> <Debug> <TLS> <000000> <write CHANGE_CIPHER
    _SPEC offset = 0 length = 1>
    <Jan 30, 2006 11:39:29 AM GMT+05:30> <Debug> <TLS> <000000> <write HANDSHAKE off
    set = 0 length = 16>
    <Jan 30, 2006 11:39:29 AM GMT+05:30> <Debug> <TLS> <000000> <SSLFilter.isActivat
    ed: false>
    <Jan 30, 2006 11:39:29 AM GMT+05:30> <Debug> <TLS> <000000> <isMuxerActivated: f
    alse>
    <Jan 30, 2006 11:39:29 AM GMT+05:30> <Debug> <TLS> <000000> <SSLFilter.isActivat
    ed: false>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 readRecord(
    )>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 SSL3/TLS MA
    C>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 received CH
    ANGE_CIPHER_SPEC>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <SSLFilter.isActivat
    ed: false>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <isMuxerActivated: f
    alse>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <SSLFilter.isActivat
    ed: false>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 readRecord(
    )>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 SSL3/TLS MA
    C>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 received HA
    NDSHAKE>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <HANDSHAKEMESSAGE: F
    inished>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <write APPLICATION_D
    ATA offset = 0 length = 304>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <write APPLICATION_D
    ATA offset = 0 length = 558>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 read( offse
    t: 0 length: 2048 )>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <SSLFilter.isActivat
    ed: false>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <isMuxerActivated: f
    alse>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <SSLFilter.isActivat
    ed: false>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 readRecord(
    )>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 SSL3/TLS MA
    C>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 received AP
    PLICATION_DATA>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 APPDATA dat
    abufferLen 0>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 APPDATA con
    tentLength 1907>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 read databu
    fferLen 1907>
    <Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 read A retu
    rns 1907>
    javax.xml.soap.SOAPException: Failed to send message: weblogic.webservice.util.A
    ccessException: The server at https://www.3pv.net/3PVWebServices/3PVWebServices.
    asmx?wsdl returned a 403 error code (Forbidden). Please ensure that your URL is
    correct and that the correct protocol is in use.
    at weblogic.webservice.core.soap.SOAPConnectionImpl.call(SOAPConnectionI
    mpl.java:61)
    at com.ceon.pencor.threepv.ThreePVUtils.sendOrderRequest(ThreePVUtils.ja
    va:350)
    at com.ceon.pencor.threepv.ThreePVAdapterImpl.sendThreePVRequest(ThreePV
    AdapterImpl.java:119)
    at com.ceon.pencor.threepv.ThreePVAdapterImpl_ydsnbq_EOImpl.sendThreePVR
    equest(ThreePVAdapterImpl_ydsnbq_EOImpl.java:46)
    at com.ceon.pencor.threepv.ThreePVAdapterImpl_ydsnbq_EOImpl_WLSkel.invok
    e(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
    ef.java:108)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:353)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    144)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
    a:415)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
    .java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    Caused by: weblogic.webservice.util.AccessException: The server at https://www.3
    pv.net/3PVWebServices/3PVWebServices.asmx?wsdl returned a 403 error code (Forbid
    den). Please ensure that your URL is correct and that the correct protocol is i
    n use.
    at weblogic.webservice.binding.http11.Http11ClientBinding.handleErrorRes
    ponse(Http11ClientBinding.java:136)
    at weblogic.webservice.binding.http11.Http11ClientBinding.receive(Http11
    ClientBinding.java:220)
    at weblogic.webservice.core.soap.SOAPConnectionImpl.call(SOAPConnectionI
    mpl.java:57)
    ... 13 more
    javax.xml.soap.SOAPException: Failed to send message: weblogic.webservice.util.A
    ccessException: The server at https://www.3pv.net/3PVWebServices/3PVWebServices.
    asmx?wsdl returned a 403 error code (Forbidden). Please ensure that your URL is
    correct and that the correct protocol is in use.
    at weblogic.webservice.core.soap.SOAPConnectionImpl.call(SOAPConnectionI
    mpl.java:61)
    at com.ceon.pencor.threepv.ThreePVUtils.sendOrderRequest(ThreePVUtils.ja
    va:350)
    at com.ceon.pencor.threepv.ThreePVAdapterImpl.sendThreePVRequest(ThreePV
    AdapterImpl.java:119)
    at com.ceon.pencor.threepv.ThreePVAdapterImpl_ydsnbq_EOImpl.sendThreePVR
    equest(ThreePVAdapterImpl_ydsnbq_EOImpl.java:46)
    at com.ceon.pencor.threepv.ThreePVAdapterImpl_ydsnbq_EOImpl_WLSkel.invok
    e(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
    ef.java:108)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:353)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    144)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
    a:415)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
    .java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    Caused by: weblogic.webservice.util.AccessException: The server at https://www.3
    pv.net/3PVWebServices/3PVWebServices.asmx?wsdl returned a 403 error code (Forbid
    den). Please ensure that your URL is correct and that the correct protocol is i
    n use.
    at weblogic.webservice.binding.http11.Http11ClientBinding.handleErrorRes
    ponse(Http11ClientBinding.java:136)
    at weblogic.webservice.binding.http11.Http11ClientBinding.receive(Http11
    ClientBinding.java:220)
    at weblogic.webservice.core.soap.SOAPConnectionImpl.call(SOAPConnectionI
    mpl.java:57)
    ... 13 more
    ERROR : Exception is occurred during connecting url:https://www.3pv.net/3PVWebS
    ervices/3PVWebServices.asmx?wsdl
    Please help...
    Cordially
    Sandip

  • Non ssl - gives 403 forbidden

    I can access the EM 12c with the ssl address https://server:7799/em
    but I would like to use the non-ssl side of it... I can access http://server:7788 and get the welcome index page.. but if I use http://server:7788/em I get Error 403 Forbidden...

    It sounds like your console is Locked. You can check the status with the command 'emctl status oms -details'.
    To unlock the console use 'emctl secure unlock -console'
    If you also want to unlock agent/OMS communication use 'emctl secure unlock -upload'
    See the Administrators Guide for further details.

  • Error 403 Forbidden, while publishing a WS

    Hi all,
    i have defined a web-service in SAP Workbench. now i'm trying to publish it and it simply doesn't work, whatever i try.
    after i defined a binding in the SOAMANAGER and want the WSDL for it to be shown, i get
    Error 403: Forbidden. Anyone ideas?
    im pretty fresh around web services in SAP, so i tried another scenario taken from help-sites.  in tr-cd WSPUBLISH i get proxy instantiation error. (i created the Service registry also by myself in tr-cd WSPARAM).
    thnx 4 ur help in advance!!!
    regards
    vasyl

              Hi Bijan,
              thats to less info. We need a little bit more to help you.
              Try looking at the console and tell us what you see.
              Which Version of WLS are you running ??
              fear
              Bijan Mohanty <[email protected]> wrote:
              >Hi,
              >
              >I have deployed a webapp(the war file)by placing it in the config/mydomain/applications
              >dir. The web app is deployed successfully and can be seen in the weblogic
              >console. But while accessing the servlet I am getting the following
              >error. Could somebody please tell me what needs to be done to fix this.
              >
              >Thanks a lot.
              >
              >Bijan.
              >
              >Error 403--Forbidden
              >From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
              >10.4.4 403 Forbidden
              >The server understood the request, but is refusing to fulfill it. Authorization
              >will not help and the request SHOULD NOT be repeated. If the request
              >method was not HEAD and the server wishes to make public why the request
              >has not been fulfilled, it SHOULD describe the reason for the refusal
              >in the entity. This status code is commonly used when the server does
              >not wish to reveal exactly why the request has been refused, or when
              >no other response is applicable
              

  • HTTP Status 403 - Trust Token failure.

    I was trying to make some changes in the CMC to an Access Level I created and when I hit ok I got this error. Does anyone know what I can do from here? All I wanted to do was add some refresh rights to the Crystal Reports.
    HTTP Status 403 - Trust Token failure. URI[/BOE/CMC/1409050957/CmcAppActions/jsp/common/effectiveRights.faces] Value [] Message[Required SAP BusinessObjects Business Intelligence Platform Trust Token is missing]
    type Status report
    message Trust Token failure. URI[/BOE/CMC/1409050957/CmcAppActions/jsp/common/effectiveRights.faces] Value [] Message[Required SAP BusinessObjects Business Intelligence Platform Trust Token is missing]
    description Access to the specified resource (Trust Token failure. URI[/BOE/CMC/1409050957/CmcAppActions/jsp/common/effectiveRights.faces] Value [] Message[Required SAP BusinessObjects Business Intelligence Platform Trust Token is missing]) has been forbidden.
    Apache Tomcat/6.0.35
    Message was edited by: Erin Shaw
    You can see the status is listed as Granted to refresh the Crystal Reports so I am not sure why my user keeps getting denied access to refresh the shortcut of the report.

    Hi
    1. In which Browser version detail?
    2. Check this SAP KBA 1451000 - Error when trying to schedule a report on InfoView and CMC
    BR
    SS

  • AS2 Error 403 Forbidden

    Hello,
    We have a change in IP at our end and hence asked our partners to adjust the same at their end.
    They have confirmed that they are using the new IP now (URL is same) and it is activated on their firewall.(Only one partner has this problem,others can send messages to us using new IP)
    Still,they are not able to send anything to us and get 403 forbidden error.
    They are able to receive messages from us.
    We have confirmed,there is no change in AS2 IDs,Message subjects at their end and XI configuration(sender agreement,etc) at our end.
    This scenario used to work fine till we had this IP change at our end.
    Kindly let me know what could be wrong ?
    Thanks.
    Regards,
    Shweta

    Hello Prateek,
    Please find below the reply from them:
    Yesterday we received a mail from you asking us to change your IP address
    abc.com  123.45.67.89   to the new address 123.45.67.87
    We changed this IP address in our system but we were not able to connect to your AS2 system via this IP
    After that we received a mail from you that we are still sending via the old IP address.
    We checked our system again and tried to send with the new IP address.
    We received an error from the your AS2 system.
    Error sending document over http to host [http://abc.com/SeeburgerAS2/AS2Server], status code [403], reason [Forbidden], response from server [<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US">
    *<head>                *
    After checking our firewall and  trying to send the data again we received the same error
    We decided to switch back to the old situation but we received the same error again.
    So currently we are not able to sent any data to you
    However we are able to receive data from you
    What can we check further?
    Thanks.
    Regards,
    Shweta

  • APEX on XE OC4J - 403 Forbidden

    I am trying to login to http://localhost:8888/apex and I get a 403 forbidden error ( http://localhost:8888/apex/wwv_flow.accept is not allowed).
    Application.log says "apex: An established connection was aborted by the software in your host machine".
    Error on the Apex Listener Admin says: HTTP Status Code: 403 Requested url http://localhost:8888/apex/wwv_flow.accept is not allowed.
    Please help.
    Thanks,
    Rajeev

    The current one does not work on XE. A fix is queued up just not quite out yet.
    -kris

  • 403 forbidden and 404 not found on dispatcher

    Hi people,
    As I'm viewing pages on my dispatcher server I get 403/404 on some resources:
    Failed to load resource: the server responded with a status of 404 (Not Found)
    http://our.dispatcher.server/libs/cq/i18n/dict.en.json
    Failed to load resource: the server responded with a status of 404 (Not Found)
    http://our.dispatcher.server/libs/cq/security/userinfo.json?cq_ck=1373462597320
    Failed to load resource: the server responded with a status of 403 (Forbidden)
    http://our.dispatcher.server/libs/cq/ui/rte.js
    Although I understand the 404s (I can let them pass in the .any file), I was wondering why would I need those on the dispatcher server?
    As for the 403s, same remark: why do I need rte (rich text editor?) on the publish/dispatcher site? 
    Thanks for any help.
    JS.

    Failed to load resource: the server responded with a status of 404 (Not Found)
    http://our.dispatcher.server/libs/cq/i18n/dict.en.json
    Failed to load resource: the server responded with a status of 404 (Not Found)
    http://our.dispatcher.server/libs/cq/security/userinfo.json?cq_ck=1373 462597320
    Those 2 seem to have been pinpointed here:  /libs/cq 404 error

  • Error 403--Forbidden while trying to access servlet

              Hi All,
              I am very new to Weblogic server. I have downloaded the 6.1 version of Weblogic
              application server. I tried a simple example in which I have an HTML which calls
              a servlet. I have deployed it on weblogic server using auto deployment feature.
              But when I try to access the html form, it gives me the following error.
              Please can anybody suggest a solution to this problem?
              Thanks,
              Vani
              Error 403--Forbidden
              From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
              10.4.4 403 Forbidden
              The server understood the request, but is refusing to fulfill it. Authorization
              will not help and the request SHOULD NOT be repeated. If the request method was
              not HEAD and the server wishes to make public why the request has not been fulfilled,
              it SHOULD describe the reason for the refusal in the entity. This status code
              is commonly used when the server does not wish to reveal exactly why the request
              has been refused, or when no other response is applicable.
              

    The demo license limits access from browsers to three unique IP addresses.
              When accessed by a fourth IP address, WLS returns '403'. You should see a
              message in the log file about the demo license.
              Mike
              "Vani" <[email protected]> wrote in message
              news:[email protected]...
              >
              > Hi All,
              > I am very new to Weblogic server. I have downloaded the 6.1 version of
              Weblogic
              > application server. I tried a simple example in which I have an HTML which
              calls
              > a servlet. I have deployed it on weblogic server using auto deployment
              feature.
              > But when I try to access the html form, it gives me the following error.
              >
              > Please can anybody suggest a solution to this problem?
              > Thanks,
              > Vani
              >
              > -----------------------------------------------------------------
              >
              > Error 403--Forbidden
              > From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
              > 10.4.4 403 Forbidden
              > The server understood the request, but is refusing to fulfill it.
              Authorization
              > will not help and the request SHOULD NOT be repeated. If the request
              method was
              > not HEAD and the server wishes to make public why the request has not been
              fulfilled,
              > it SHOULD describe the reason for the refusal in the entity. This status
              code
              > is commonly used when the server does not wish to reveal exactly why the
              request
              > has been refused, or when no other response is applicable.
              >
              > -----------------------------------------------------------------
              

  • Error 403--Forbidden

    Hi all ,
    I create a simple stateless ejb named LoginSession to manage the login task
    , package it to a ejb jar file named login.jar , and then I want to explode
    it as a wls7.0 webservice , the build.xml like this :
    <project name="buildWebservice" default="ear">
    <target name="ear">
    <servicegen destEar="login.ear" contextURI="login">
    <service ejbJar="login.jar" includeEJBs="LoginSession"
    targetNamespace="http://www.ricobest.com/webservice/login"
    serviceName="LoginSession" serviceURI="/LoginSession" generateTypes="True"
    expandMethods="True"/>
    </servicegen>
    </target>
    </project>
    When after ant running successfully , ant generated login.ear file for me ,
    but I find some ploblems :
    1 , the ear file contains login jar and web-service.war file , similar with
    wls6.1 webservice , but the web.xml file in web-service.war is different
    from wls6.1 , the 7.0 file is black ! only the following 3 lines :
    #1 <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
    2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
    #2 <web-app>
    #3 </web-app>
    2 , I can not file the wsdl.jsp file in the ear file , whick will contained
    in 6.1 webservice .
    3 , when I want to request http://localhost:7001/login/ , error message
    list in my browser :
    Error 403--Forbidden
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.4 403 Forbidden
    The server understood the request, but is refusing to fulfill it.
    Authorization will not help and the request SHOULD NOT be repeated. If the
    request method was not HEAD and the server wishes to make public why the
    request has not been fulfilled, it SHOULD describe the reason for the
    refusal in the entity. This status code is commonly used when the server
    does not wish to reveal exactly why the request has been refused, or when no
    other response is applicable.
    ps , I do need client jar , so in build.xml , does not include client
    element , and when I insert it to the xml file , result is the same.
    Any response will be appreciated .
    Thank you.
    lcl

    Thank you ,Manoj
    "manoj cheenath" <[email protected]> :[email protected]...
    see comments inline:
    regards,
    -manoj
    "lcl" <[email protected]> wrote in message news:[email protected]...
    Hi all ,
    I create a simple stateless ejb named LoginSession to manage the login task
    , package it to a ejb jar file named login.jar , and then I want to explode
    it as a wls7.0 webservice , the build.xml like this :
    <project name="buildWebservice" default="ear">
    <target name="ear">
    <servicegen destEar="login.ear" contextURI="login">
    <service ejbJar="login.jar" includeEJBs="LoginSession"
    targetNamespace="http://www.ricobest.com/webservice/login"
    serviceName="LoginSession" serviceURI="/LoginSession" generateTypes="True"
    expandMethods="True"/>
    </servicegen>
    </target>
    </project>
    When after ant running successfully , ant generated login.ear file for me ,
    but I find some ploblems :
    1 , the ear file contains login jar and web-service.war file , similar with
    wls6.1 webservice , but the web.xml file in web-service.war is different
    from wls6.1 , the 7.0 file is black ! only the following 3 lines :
    #1 <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
    2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
    #2 <web-app>
    #3 </web-app>
    In WLS 7.0 there is a new DD file for Web Service. Look for
    web-services.xml file inside the WEB-INF dir. There is no
    change needed to the web.xml file.
    2 , I can not file the wsdl.jsp file in the ear file , whick will contained
    in 6.1 webservice .
    The WSDL is generated from the deployment information at
    runtime.
    3 , when I want to request http://localhost:7001/login/ , error message
    list in my browser :
    Error 403--Forbidden
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.4 403 Forbidden
    The server understood the request, but is refusing to fulfill it.
    Authorization will not help and the request SHOULD NOT be repeated. If the
    request method was not HEAD and the server wishes to make public why the
    request has not been fulfilled, it SHOULD describe the reason for the
    refusal in the entity. This status code is commonly used when the server
    does not wish to reveal exactly why the request has been refused, or when no
    other response is applicable.
    <servicegen destEar="login.ear" contextURI="login">
    <service ejbJar="login.jar" includeEJBs="LoginSession"
    targetNamespace="http://www.ricobest.com/webservice/login"
    serviceName="LoginSession" serviceURI="/LoginSession" generateTypes="True"
    expandMethods="True"/>
    I think the URL you need to hit is:
    http://localhost:7001/login/LoginSession
    ps , I do need client jar , so in build.xml , does not include client
    element , and when I insert it to the xml file , result is the same.
    You can use clientgen to generate the client.jar file
    by pointing to the deployed WSDL.
    Any response will be appreciated .
    Thank you.
    lcl
    [att1.html]

  • Error 403--Forbidden using eclipse and weblogic

    hi,
    i am new here on j2ee
    I am using eclipse3.4 and weblogic 9.1.2 on xp. I am trying to make simple hello world servlet
    here is what i did
    on the eclipse click New and click on Dynamic project
    click on Servlet and write following code for the servlet
    import java.io.IOException;
    import java.io.PrintWriter;
    import javax.servlet.ServletException;
    import javax.servlet.http.HttpServlet;
    import javax.servlet.http.HttpServletRequest;
    import javax.servlet.http.HttpServletResponse;
    * Servlet implementation class SecondServlet
    public class SecondServlet extends HttpServlet {
         public void service (HttpServletRequest req, HttpServletResponse res)
         throws IOException
              res.setContentType("text'html");
              PrintWriter out = res.getWriter();
              out.println("<html><head>" + "<title> Hello World </title></head>" +
                        "<h1>Hello Worldasd </h1></body></html>");
    folder structure and file web.xml is created by eclipse itself.
    then i started weblogic from the eclipse
    and i have following error
    http://localhost:7001/SecondServlet/
    Error 403--Forbidden
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.4 403 Forbidden
    The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.

    I do connect with router/modem
    eclipse did create weblogic.xml. here it is
    <?xml version="1.0" encoding="UTF-8"?>
    <wls:weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
    <wls:jsp-descriptor>
    <wls:keepgenerated>true</wls:keepgenerated>
    <wls:working-dir>C:\Documents and Settings\Owner\My Documents\jj\java-files\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\work\SecondServlet</wls:working-dir>
    <wls:debug>true</wls:debug>
    </wls:jsp-descriptor>
    <wls:context-root>SecondServlet</wls:context-root>
    </wls:weblogic-web-app>
    i did create a user proejct domain in weblogic.
    I did try by login through localhost:7001/console. but it didn't work. following is the problem
    Error 503--Service Unavailable
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.5.4 503 Service Unavailable
    The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay may be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
    Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
    any more suggestion will be helpful.
    this is just a start so please i need to solve this problem so that i can move ahead
    thanks
    Edited by: chitochez on Dec 18, 2008 5:45 AM

Maybe you are looking for