[JBoss JIRA] (WFCORE-3953) JBoss CLI doesn't work on OpenShift
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3953?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise commented on WFCORE-3953:
----------------------------------------------
Thank-you for the steps. Actually the version of aesh-readline 1.5 doesn't contain the fix for AESH-460 that seems to cause this problem. We had a report with a different symptom but root cause was the same. A patched aesh-readline 1.5 is attached to https://issues.jboss.org/browse/WFCORE-3667.
> JBoss CLI doesn't work on OpenShift
> -----------------------------------
>
> Key: WFCORE-3953
> URL: https://issues.jboss.org/browse/WFCORE-3953
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Environment: OpenShift/MiniShift
> * minishift v1.15.1+f19ac09
> * CDK v3.4.0-2
> EAP CD12
> * Registry registry.access.redhat.com
> * Namespace/Repository jboss-eap-7-tech-preview/eap-cd-openshift
> * Tag 12.0-14
> Reporter: Martin Styk
> Assignee: Jean-Francois Denise
> Priority: Critical
>
> I am unable to access JBoss CLI console running EAP CD12 on OpenShift.
> On OS webconsole terminal:
> {code}
> cd $JBOSS_HOME/bin
> sh jboss-cli.sh
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> {code}
> No new line appears and I am not able to enter any character, thus I can not connect. I can only exit JBoss CLI console with Ctrl + C.
> With CD12 it doesn't work neither with terminal session on web console, nor with {{oc rsh <pod>}} from local terminal.
> This doesn't happen with EAP 7.0 and EAP 7.1 openshift images. EAP CD12 distribution (not the OpenShift image) is also not affected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (ELY-1605) ELY05016: Unrecognized token for CCM mode cipher suites.
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/ELY-1605?page=com.atlassian.jira.plugin.s... ]
Martin Choma updated ELY-1605:
------------------------------
Description:
{code}
/subsystem=elytron/server-ssl-context=a:add(cipher-suite-filter="TLS_RSA_WITH_AES_256_CCM,TLS_RSA_WITH_AES_128_CCM")
{
"outcome" => "failed",
"failure-description" => "WFLYELY01017: Invalid value for cipher-suite-filter. ELY05016: Unrecognized token \"TLS_RSA_WITH_AES_256_CCM\" in mechanism selection string \"TLS_RSA_WITH_AES_256_CCM,TLS_RSA_WITH_AES_128_CCM\"",
"rolled-back" => true
}
{code}
This is probably simply because MechanismDatabase.properties does not know CCM cipher suites.
Marking as Critical because both of ciphersuites from reproducer are listed as FIPS cipher suites for FIPS BC TLS [1]
These two ciphersuites (TLS_RSA_WITH_AES_256_CCM,TLS_RSA_WITH_AES_128_CCM) are introduced in [rfc6655|https://tools.ietf.org/html/rfc6655].
[1] https://downloads.bouncycastle.org/fips-java/BC-FJA-(D)TLSUserGuide-1.0.5...
[2] https://tools.ietf.org/html/rfc6655
was:
{code}
/subsystem=elytron/server-ssl-context=a:add(cipher-suite-filter="TLS_RSA_WITH_AES_256_CCM,TLS_RSA_WITH_AES_128_CCM")
{
"outcome" => "failed",
"failure-description" => "WFLYELY01017: Invalid value for cipher-suite-filter. ELY05016: Unrecognized token \"TLS_RSA_WITH_AES_256_CCM\" in mechanism selection string \"TLS_RSA_WITH_AES_256_CCM,TLS_RSA_WITH_AES_128_CCM\"",
"rolled-back" => true
}
{code}
This is probably simply because MechanismDatabase.properties does not know CCM cipher suites.
Marking as Critical because both of ciphersuites from reproducer are listed as FIPS cipher suites for FIPS BC TLS [1]
[1] https://downloads.bouncycastle.org/fips-java/BC-FJA-(D)TLSUserGuide-1.0.5...
> ELY05016: Unrecognized token for CCM mode cipher suites.
> --------------------------------------------------------
>
> Key: ELY-1605
> URL: https://issues.jboss.org/browse/ELY-1605
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.3.3.Final
> Reporter: Martin Choma
> Priority: Critical
>
> {code}
> /subsystem=elytron/server-ssl-context=a:add(cipher-suite-filter="TLS_RSA_WITH_AES_256_CCM,TLS_RSA_WITH_AES_128_CCM")
> {
> "outcome" => "failed",
> "failure-description" => "WFLYELY01017: Invalid value for cipher-suite-filter. ELY05016: Unrecognized token \"TLS_RSA_WITH_AES_256_CCM\" in mechanism selection string \"TLS_RSA_WITH_AES_256_CCM,TLS_RSA_WITH_AES_128_CCM\"",
> "rolled-back" => true
> }
> {code}
> This is probably simply because MechanismDatabase.properties does not know CCM cipher suites.
> Marking as Critical because both of ciphersuites from reproducer are listed as FIPS cipher suites for FIPS BC TLS [1]
> These two ciphersuites (TLS_RSA_WITH_AES_256_CCM,TLS_RSA_WITH_AES_128_CCM) are introduced in [rfc6655|https://tools.ietf.org/html/rfc6655].
> [1] https://downloads.bouncycastle.org/fips-java/BC-FJA-(D)TLSUserGuide-1.0.5...
> [2] https://tools.ietf.org/html/rfc6655
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFCORE-3953) JBoss CLI doesn't work on OpenShift
by Martin Styk (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3953?page=com.atlassian.jira.plugi... ]
Martin Styk updated WFCORE-3953:
--------------------------------
Steps to Reproduce:
Steps to reproduce using OS web console
* Prepare minishift (https://developers.redhat.com/products/cdk/download/)
* minishift start
* minishift console
* Open one of your projects on the right side panel
* On top right corner (under logged user info) click on "Add to project"
* Select deploy image
* Search by Image Name registry.access.redhat.com/jboss-eap-7-tech-preview/eap-cd-openshift and hit deploy button
* OS application eap-cd-openshift is created
* Go to Application -> Pods and open the created pod with CD12 instance running
* Open Terminal section -> sh $JBOSS_HOME/bin/jboss-cli.sh
> JBoss CLI doesn't work on OpenShift
> -----------------------------------
>
> Key: WFCORE-3953
> URL: https://issues.jboss.org/browse/WFCORE-3953
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Environment: OpenShift/MiniShift
> * minishift v1.15.1+f19ac09
> * CDK v3.4.0-2
> EAP CD12
> * Registry registry.access.redhat.com
> * Namespace/Repository jboss-eap-7-tech-preview/eap-cd-openshift
> * Tag 12.0-14
> Reporter: Martin Styk
> Assignee: Jean-Francois Denise
> Priority: Critical
>
> I am unable to access JBoss CLI console running EAP CD12 on OpenShift.
> On OS webconsole terminal:
> {code}
> cd $JBOSS_HOME/bin
> sh jboss-cli.sh
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> {code}
> No new line appears and I am not able to enter any character, thus I can not connect. I can only exit JBoss CLI console with Ctrl + C.
> With CD12 it doesn't work neither with terminal session on web console, nor with {{oc rsh <pod>}} from local terminal.
> This doesn't happen with EAP 7.0 and EAP 7.1 openshift images. EAP CD12 distribution (not the OpenShift image) is also not affected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years