Cipher parameter missing from NIDP connector when installing NAM Identity Server on Windows

  • 7016279
  • 10-Mar-2015
  • 31-Mar-2015

Environment

NetIQ Access Manager 4.0
NetIQ Access Manager 3.2
Using Windows as OS for all NAM components

Situation

When installing Access Manager components e.g. Identity Server on Linux, we pre-configure our tomcat connectors following our best practice and include only secure ciphers. The following shows the NIDP connector on my Linux server.xml file

<Connector NIDP_Name="connector" SSLEnabled="true" URIEncoding="utf-8" acceptCount="100" address="147.2.16.135" ciphers="SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, TLS_KRB5_WITH_3DES_EDE_CBC_SHA, TLS_KRB5_WITH_RC4_128_SHA" clientAuth="false" disableUploadTimeout="true" enableLookups="false" keystoreFile="/opt/novell/devman/jcc/certs/idp/connector.keystore" keystorePass="bxE7fPME2YK0d8T" maxThreads="600" minSpareThreads="5" port="8443" scheme="https" secure="true" sslImplementationName="com.novell.nidp.common.util.net.server.NIDPSSLImplementation" sslProtocol="TLS"/>

When installing the Identity Server on Windows, we do not set any of the cipher information.

Resolution

Fixed in NAM 4.1. Can  manually add the following to the server.xml file under Tomcat\conf\ in the meantime:

a) locate the connector starting with <Connector NIDP_Name="connector" .... >
b) add ciphers="SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, TLS_KRB5_WITH_3DES_EDE_CBC_SHA, TLS_KRB5_WITH_RC4_128_SHA" secure="true"

followed by tomcat restart.