000033111 - RSA Connector Framework 2.7.0 and older and Archer SaaS (hosted)

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000033111
Applies ToRSA Product Set: Security Management
RSA Product/Service Type: SecOps
RSA Version/Condition: 1.2 and older
 
IssueIf you are running SecOps version 1.2, 1.1 P1, 1.1 or other older iteration it quits functioning with an Archer SaaS (hosted) environment.  The following errors are listed in the "rsa_connector_0.log" file:
 
May 5, 2016 3:19:26 PM com.rsa.connector.framework.components.datastore.archer.ArcherWSHelper
WARNING: Can not communicate with Archer. Please check Archer host details, credentials and account permissions. This could be also because of invalid session.
May 5, 2016 3:19:26 PM com.rsa.connector.framework.components.datastore.archer.ArcherWSHelper
WARNING: Request is set for retry. Archer Datastore will try again.
May 5, 2016 3:19:26 PM org.apache.cxf.phase.PhaseInterceptorChain doDefaultLogging
WARNING: Interceptor for {http://archer-tech.com/webservices/}general#{http://archer-tech.com/webservices/}CreateUserSessionFromInstance has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: Could not send Message.
 at org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(MessageSenderInterceptor.java:48)
 at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
 at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:487)
 at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
 at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265)
 at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
 at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
 at $Proxy43.createUserSessionFromInstance(Unknown Source)
 at com.rsa.connector.framework.components.datastore.archer.ArcherWSHelper.login(ArcherWSHelper.java:499)
 at com.rsa.connector.framework.components.datastore.archer.ArcherWSHelper.getSessionToken(ArcherWSHelper.java:483)
 at com.rsa.connector.framework.components.datastore.archer.ArcherWSHelper.callArcher(ArcherWSHelper.java:397)
 at com.rsa.connector.framework.components.datastore.archer.ArcherDataStore.findApplicationID(ArcherDataStore.java:1299)
 at com.rsa.connector.framework.components.datastore.archer.ArcherDataStore.putData(ArcherDataStore.java:441)
 at com.rsa.connector.framework.components.datastore.archer.ArcherDataStore.handleData(ArcherDataStore.java:386)
 at com.rsa.connector.plugin.soc.SOCManagementService.onApplicationDataReceived(SOCManagementService.java:67)
 at com.rsa.connector.plugin.service.AbstractRsaConnectorService.processDataHandlingRequest(AbstractRsaConnectorService.java:99)
 at com.rsa.connector.framework.plugin.ApplicationRequestHandler.execute(ApplicationRequestHandler.java:177)
 at com.rsa.connector.framework.plugin.ApplicationRequestHandler.access$400(ApplicationRequestHandler.java:30)
 at com.rsa.connector.framework.plugin.ApplicationRequestHandler$QueueWorker.run(ApplicationRequestHandler.java:249)
Caused by: java.net.MalformedURLException: Unknown protocol: httpss
 at java.net.URL.<init>(URL.java:601)
 at java.net.URL.<init>(URL.java:464)
 at java.net.URL.<init>(URL.java:413)
 at org.apache.cxf.transport.http.HTTPConduit.setupURL(HTTPConduit.java:756)
 at org.apache.cxf.transport.http.HTTPConduit.prepare(HTTPConduit.java:496)
 at org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(MessageSenderInterceptor.java:46)
 ... 18 more

 
CauseThis is a combination of issues. RSA Connector Framework (RCF) version 2.7.0 and older had a "bug" (SOC-1261) that was fixed in SecOps release 1.2.0.1.
The other side of the issue was the SaaS team changed how it was handling HTTPS based traffic. Once this change in behavior occurred it caused RCF versions 2.7.0 and older to not be able to communicate with a SaaS (hosted) environment.
ResolutionUpgrade to RCF version 2.7.1 or newer version of middleware.

Attachments

    Outcomes