This discussion is archived
5 Replies Latest reply: Sep 5, 2013 8:17 PM by f769f13d-8dfe-4799-a027-1a4ea78fc684 RSS

Publication failed

Nelash Jindal Newbie
Currently Being Moderated

Hi,

 

I am trying to publish my site from one server to other but it failing and in the logs I can see:-

[2013-08-19 18:14:28,645 IST] [ERROR] [http-bio-9780-exec-35] [wem.sso.cas.CASProvider] Failed to acquire ticket

java.io.IOException: Server returned HTTP response code: 403 for URL: http://localhost:9780/cas/v1/tickets/TGT-100-CsuYjEZHq9nbpiuFI3fQflVVxmSKdUejjXD1hhwbbWbhQeYtK4-cas-localhost-1

    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1436)

    at com.fatwire.wem.sso.cas.CASProvider.getST(CASProvider.java:309)

    at com.fatwire.wem.sso.cas.CASProvider.getTicket(CASProvider.java:159)

    at COM.FutureTense.Security.SecureLogin.SecureLoginFilter.doFilter(SecureLoginFilter.java:314)

    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)

    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)

    at COM.FutureTense.Servlet.URLRewriteFilter.doFilter(URLRewriteFilter.java:81)

    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)

    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)

    at com.fatwire.wem.sso.cas.filter.CASFilter.doFilter(CASFilter.java:701)

    at com.fatwire.wem.sso.SSOFilter.doFilter(SSOFilter.java:51)

    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)

    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)

    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)

    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)

    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)

    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)

    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)

    at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:929)

    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)

    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)

    at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1002)

    at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)

    at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)

    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

    at java.lang.Thread.run(Thread.java:662)

[2013-08-19 18:14:28,645 IST] [WARN ] [http-bio-9780-exec-35] [fatwire.logging.security.context] Unable to obtain authentication provider ticket, defaulting to internal authentication.

 

 

Can anybody help me in fixing this issue.

 

Thanks,

Nelash Jindal

  • 1. Re: Publication failed
    Mike - Oracle Explorer
    Currently Being Moderated

    check the casUrl in SSOConfig.xml

     

    It appears that it is set to localhost.  It needs to be set with an address that the source can reach the destination cas at

  • 2. Re: Publication failed
    Nelash Jindal Newbie
    Currently Being Moderated

    Hi Mike,

     

    Thanks for replying.

     

    I have changed casUrl from localhost to IP but it still giving me same error. Here how casUrl in SSOConfig.xml looks:-

     

    <!-- CAS server URL prefix. In case of cluster, it must point to the Load Balancer. -->
    <property name="casUrl" value="http://10.180.57.81:9780/cas" />

        <!-- Used for ticket validation. In case of cluster with cas server behind firewall, it must point to the cas server. -->

        <property name="casInternalURL" value="http://10.180.57.81:9780/cas" />

     

    And error logs are:-

    [2013-08-20 11:18:32,991 IST] [ERROR] [http-bio-9780-exec-15] [wem.sso.cas.CASProvider] Failed to acquire ticket

    java.io.IOException: Server returned HTTP response code: 403 for URL: http://10.180.57.81:9780/cas/v1/tickets/TGT-25-guYrckevYRaG7gpOzwOoiyjOc5PGe6fNNbevb9i0ucY9dUkMhg-cas-localhost-1

        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1436)

        at com.fatwire.wem.sso.cas.CASProvider.getST(CASProvider.java:309)

        at com.fatwire.wem.sso.cas.CASProvider.getTicket(CASProvider.java:159)

        at COM.FutureTense.Security.SecureLogin.SecureLoginFilter.doFilter(SecureLoginFilter.java:314)

        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)

        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)

        at COM.FutureTense.Servlet.URLRewriteFilter.doFilter(URLRewriteFilter.java:81)

        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)

        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)

        at com.fatwire.wem.sso.cas.filter.CASFilter.doFilter(CASFilter.java:701)

        at com.fatwire.wem.sso.SSOFilter.doFilter(SSOFilter.java:51)

        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)

        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)

        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)

        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)

        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)

        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)

        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)

        at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:929)

        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)

        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)

        at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1002)

        at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)

        at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)

        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

        at java.lang.Thread.run(Thread.java:662)

    [2013-08-20 11:18:32,991 IST] [WARN ] [http-bio-9780-exec-15] [fatwire.logging.security.context] Unable to obtain authentication provider ticket, defaulting to internal authentication

     

    Do I have to make any other change to make it working?

     

    Thanks,

    Nelash Jindal

  • 3. Re: Publication failed
    Mike - Oracle Explorer
    Currently Being Moderated

    Have a look at the cas.log file on the destination to see if there is any clue.

  • 4. Re: Publication failed
    Nelash Jindal Newbie
    Currently Being Moderated

    Hi Mike,

     

    Thanks for your help.

     

    I am able to track the exact issue. Issue was that their were two recommendations with the same name in my current sites. So when I try to publish it fails saying unique key constraint violated. Renaming one recommendation fixed this issue.

     

    But I am still wondering that as sites does not allow same name for two asset of same flex family how come it allowed me on my current sites. Not only for recommendation, but also for my own flex family, where I have same name for two parent definition.

     

    Also, I am able to publish successfully and it is giving success as status on UI, but it still giving me same above mentioned error in logs.

     

    Their is no clue about it in cas.log of destination.

     

    Thanks,

    Nelash jindal

  • 5. Re: Publication failed
    f769f13d-8dfe-4799-a027-1a4ea78fc684 Newbie
    Currently Being Moderated

    Hi Nelash

     

    I have the same issue in 11.1.1.8. But it happen when I publish the avisports sample site to target. The publish proccess is failed. Which version you use? I never see the issue in 11.1.1.6. Thanks.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points