The following cipher suites allowed by the App Connect Professional when using the SSL protocol
SSL_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
SSL_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
SSL_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
SSL_RSA_WITH_AES_256_GCM_SHA384,
SSL_ECDH_ECDSA_WITH_AES_256_GCM_SHA384,
SSL_ECDH_RSA_WITH_AES_256_GCM_SHA384,
SSL_DHE_DSS_WITH_AES_256_GCM_SHA384,
SSL_DHE_RSA_WITH_AES_256_GCM_SHA384,
SSL_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
SSL_RSA_WITH_AES_128_GCM_SHA256,
SSL_ECDH_ECDSA_WITH_AES_128_GCM_SHA256,
SSL_ECDH_RSA_WITH_AES_128_GCM_SHA256,
SSL_DHE_RSA_WITH_AES_128_GCM_SHA256,
SSL_DHE_DSS_WITH_AES_128_GCM_SHA256
During SSL Configuration you can either use SSL_* or TLS_* and specify one or multiple cipher specifications, such as SSL_RSA_WITH_AES_128_GCM_SHA256 or SSL_DHE_RSA_WITH_AES_128_GCM_SHA256 or SSL_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 but any of the client cipher suite should be available on server side. If multiple cipher suites configuring, they must be separated by a comma (,) with no space either before or after the comma.
During SSL handshake, if null or multiple values are specified, the client and the server negotiate and find the most secure cipher suites to use. If no compatible cipher suites is found, the connection fails. You cannot prioritise the cipher suites by specifying one before the another.
#AppConnectProfessional(ACP)#Support#SupportMigration