One of both Sites nodes is unable to work standalone when clustering CAS (Doc ID 1506863.1)

Last updated on APRIL 24, 2023

Applies to:

Goal

I am running a clustered WebCenter Sites application with members Node1 and Node2
Each node has its own CAS deployed and each WebCenter Sites has casURL and casInternalURL in SSOConfig.xml pointing at the CAS instance deployed in the same node.
Node1: WCS1 CAS1. SSOConfig.xml casUrl:CAS1URL casInternalUrl: CAS1InternalUrl
Node2: WCS2 CAS2. SSOConfig.xml casUrl:CAS2URL casInternalUrl: CAS2InternalUrl

This should make each instance to work standalone. Node1 is able to work standalone, however Node2 is not.
I am getting the following error in the Sites.log when I try to start it.
SEVERE: The RuntimeException could not be mapped to a response, re-throwing to the HTTP container
java.lang.RuntimeException: java.net.ConnectException: Connection refused
       at com.fatwire.wem.sso.cas.plugin.CSAuthenticationHandler.authenticateUsernamePasswordInternal(CSAuthenticationHandler.java:165)
       at org.jasig.cas.authentication.handler.support.AbstractUsernamePasswordAuthenticationHandler.doAuthentication(AbstractUsernamePasswordAuthenticationHandler.java:56)
       at org.jasig.cas.authentication.handler.support.AbstractPreAndPostProcessingAuthenticationHandler.authenticate(AbstractPreAndPostProcessingAuthenticationHandler.java:71)
       at org.jasig.cas.authentication.AuthenticationManagerImpl.authenticate(AuthenticationManagerImpl.java:88)
       at org.jasig.cas.CentralAuthenticationServiceImpl.createTicketGrantingTicket(CentralAuthenticationServiceImpl.java:417)
       at com.fatwire.wem.sso.cas.integration.rest.TicketResource.tickets(TicketResource.java:62)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:597)
       at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:175)
       at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:67)
       at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:208)

Why is this happening? Is there any other place where CAS references WCS or vice-versa?

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.