Certain AFX Connector types fail to deploy after patching or upgrading RSA Identity Governance & Lifecycle. The connectors remain in a
Not Deployed status in RSA Identity Governance & Lifecycle under
AFX >
Connectors. It is not known at this time how many connector types are affected. We have seen this problem with the following connector types:
- Generic SSH Connectors
- Office365 Connectors
For example, below is the state of an Office365 Connector after patching to 7.2.0 P01:
The following error message is displayed in the user interface when using the Test Connector Settings button.
java.io.IOException: Auth cancel
at net.sf.commons.ssh.jsch.JschConnectionFactory.connectUsingPassword(JschConnectionFactory.java:82)
The following error is logged to the aveksaServer.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log):
06/15/2020 17:19:26.641 ERROR (default task-2) [com.aveksa.afx.server.service.handler.AFXPrimaryRequestHandler]
Exception putting together connector deployment for <Connector name>
java.lang.NullPointerException
at java.lang.String.replace(String.java:2240)
at com.aveksa.afx.server.service.handler.flow.EndpointSubstitutor.substituteCodes(EndpointSubstitutor.java:233)
at com.aveksa.afx.server.service.handler.flow.EndpointSubstitutor.substitute(EndpointSubstitutor.java:106)
at com.aveksa.afx.server.service.handler.AFXPrimaryRequestHandler.processConnectors(AFXPrimaryRequestHandler.java:284)
at com.aveksa.afx.server.service.handler.AFXPrimaryRequestHandler.processRequest(AFXPrimaryRequestHandler.java:42)
at com.aveksa.afx.plugin.integration.service.AFXRequestDispatcherProvider.dispatchRequest(AFXRequestDispatcherProvider.java:51)
at com.aveksa.afx.AFXServlet.doPost(AFXServlet.java:24)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
Please refer to RSA Knowledge Base Article
000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the
aveksaServer.log for your specific deployment, if you are on a WildFly cluster or a non-WildFly platform. The
aveksaServer.log may also be downloaded from the RSA Identity Governance & Lifecycle user interface (
Admin >
System >
Server Nodes tab > under
Logs.)