This content has been marked as final.
Show 3 replies
-
1. Re: Switching from Wildfly 8 to Wildfly 9, error using jboss CLI to add enabled-cipher-suites
jaikiran Jun 16, 2015 4:42 AM (in response to spittel)I'm not aware what changed and whether that change was expected to result in this behaviour which breaks existing scripts. If the change was a bug fix, then it probably makes sense. Anyway, maybe aloubyansky knows?
-
2. Re: Switching from Wildfly 8 to Wildfly 9, error using jboss CLI to add enabled-cipher-suites
jaikiran Jun 16, 2015 5:38 AM (in response to jaikiran)FWIW - I was able to successfully added those cipher suites by getting rid of the backslashes in your command and instead wrapping the entire comma separate value in double quotes:
/subsystem=undertow/server=default-server/https-listener=default-https:add(enabled-cipher-suites="TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384,TLS_DHE_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_3DES_EDE_CBC_SHA",security-realm=ApplicationRealm,socket-binding=https)
-
3. Re: Switching from Wildfly 8 to Wildfly 9, error using jboss CLI to add enabled-cipher-suites
spittel Jun 16, 2015 11:56 AM (in response to jaikiran)Thanks jaikiran, that worked!