[JBoss JIRA] (WFLY-10014) Unable to configure comma delimited enabled-protocols in remote-connector
by Nagaraju Chitimilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-10014?page=com.atlassian.jira.plugin... ]
Nagaraju Chitimilla edited comment on WFLY-10014 at 3/14/18 7:00 AM:
---------------------------------------------------------------------
I have tried escaping the with the following options, but its always giving exception:
<param name="enabled-protocols" value="TLSv1.1\\,TLSv1.2"/>
*Error:* java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1\\,TLSv1.2
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
*Error:*
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
^^^^ Unexpected character '\' (code 92) excepted space, or '>' or "/>"
at [row,col {unknown-source}]: [656,53]
Can you let me know the exact behavior?
Thanks in advance
-Nagaraju
was (Author: n_nagraj321):
I have tried escaping the with the following options, but its always giving exception:
<param name="enabled-protocols" value="TLSv1.1\\\,TLSv1.2"/>
*Error:* java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1\\,TLSv1.2
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
*Error:*
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
^^^^ Unexpected character '\' (code 92) excepted space, or '>' or "/>"
at [row,col {unknown-source}]: [656,53]
Can you let me know the exact behavior?
Thanks in advance
-Nagaraju
> Unable to configure comma delimited enabled-protocols in remote-connector
> -------------------------------------------------------------------------
>
> Key: WFLY-10014
> URL: https://issues.jboss.org/browse/WFLY-10014
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 12.0.0.Final
> Reporter: Nagaraju Chitimilla
> Assignee: Jeff Mesnil
> Priority: Critical
>
> When I want to configure enabled SSL protocols, Netty requires to use comma delimited list to be passed into enabled-protocols param in remote-connector
> {noformat}
> <param name="enabled-protocols" value="TLSv1.1,TLSv1.2"/>
> {noformat}
> But when comma is used in value in configuration string passed into ActiveMQRaUtils.parseConfig, parsing fails:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1,TLSv1.2;trustStorePassword=N0tall0wed;keyStorePassword=N0tall0wed;port=61616;localAddress=0.0.0.0;sslEnabled=true;host=localhost;trustStorePath=C:/ActiveMQ/conf/keystore.p12;keyStorePath=C:/ActiveMQ/conf/keystore.p12
> at org.apache.activemq.artemis.ra.ActiveMQRaUtils.parseConfig(ActiveMQRaUtils.java:205)
> at org.apache.activemq.artemis.ra.ActiveMQResourceAdapter.setConnectionParameters(ActiveMQResourceAdapter.java:342)
> ... 18 more
> {code}
> I set this as critical as it prevent setting more then one allowed SSLContext protocol.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-9969) JDK9 + FIPS BC, unable to configure
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-9969?page=com.atlassian.jira.plugin.... ]
Martin Choma edited comment on WFLY-9969 at 3/14/18 7:00 AM:
-------------------------------------------------------------
[~dmlloyd] how do you mean
??you could add a resource root like this (in the module.xml):
<resource-root path="content"/>
then create a "content" directory in the same directory as the module.xml
and add a "META-INF/services/java.security.Provider" file there??
Where should I put jar?
{{├── content
│ ├── bc-fips-1.0.0.jar
│ └── META-INF
│ └── services
│ └── java.security.Provider
└── module.xml}}
was (Author: mchoma):
[~dmlloyd] how do you mean
??
you could add a resource root like this (in the module.xml):
<resource-root path="content"/>
then create a "content" directory in the same directory as the module.xml
and add a "META-INF/services/java.security.Provider" file there
??
Where should I put jar?
{{
├── content
│ ├── bc-fips-1.0.0.jar
│ └── META-INF
│ └── services
│ └── java.security.Provider
└── module.xml
}}
> JDK9 + FIPS BC, unable to configure
> -----------------------------------
>
> Key: WFLY-9969
> URL: https://issues.jboss.org/browse/WFLY-9969
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 12.0.0.Final
> Reporter: Martin Choma
>
> * Configure BouncyCastleFipsProvider in java
> {code:title=$\{jdk9_home\}/conf/security/java.security}
> security.provider.1=org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider
> security.provider.2=SUN
> security.provider.3=SunRsaSign
> security.provider.4=SunEC
> security.provider.5=SunJSSE BCFIPS
> security.provider.6=SunJCE
> security.provider.7=SunJGSS
> security.provider.8=SunSASL
> security.provider.9=XMLDSig
> security.provider.10=SunPCSC
> security.provider.11=JdkLDAP
> security.provider.12=JdkSASL
> security.provider.13=SunPKCS11
> {code}
> * configure -cp of java process based on https://docs.oracle.com/javase/9/security/howtoimplaprovider.htm#JSSEC-GU.... It means in $\{jboss_home\}/bin/standalone.conf put -cp option with bcfips jar
> {{JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -cp /home/mchoma/.m2/repository/org/bouncycastle/fips/bc-fips/1.0.0/bc-fips-1.0.0.jar"}}
> * Configure additional logging
> {code}
> /subsystem=logging/console-handler=CONSOLE:write-attribute(name=level, value=ALL)
> /subsystem=logging/logger=org.wildfly.extension.elytron:add(level=ALL)
> {code}
> * Run CLI command usink BCFKS key store type
> {{/subsystem=elytron/key-store=bcfks_keystore:add(path=keystore.bcfks,relative-to=jboss.server.config.dir, type="BCFKS", credential-reference=\{clear-text=password\})}}
> * For some reason BouncyCastleFipsProvider is not listed among providers returned by Security.getProviders() and therefore BCFKS can't be resolved
> {code}
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/mchoma/eap/7.2.0.EL12.CR1/jboss-eap-7.2
> JAVA: /opt/java/jdk-9.0.1_bcfips/bin/java
> JAVA_OPTS: -server -Xms1303m -Xmx1303m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -cp /home/mchoma/.m2/repository/org/bouncycastle/fips/bc-fips/1.0.0/bc-fips-1.0.0.jar -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n
> =========================================================================
> ...
> 09:20:16,630 TRACE [org.wildfly.extension.elytron] (MSC service thread 1-3) No provider identified for name [null] and algorithm [BCFKS] between [SUN version 9, ApacheXMLDSig version 2.11, SunRsaSign version 9, SunEC version 9, SunJSSE version 9, SunJCE version 9, SunJGSS version 9, SunSASL version 9, XMLDSig version 9, SunPCSC version 9, JdkLDAP version 9, JdkSASL version 9, SunPKCS11 version 9, SunDeploy-MozillaJSS version 1.5, WildFlyElytron version 1.0, TLSP version 1.0, openssl version 1.0]
> 09:20:16,632 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service org.wildfly.security.key-store.bcfks_keystore: org.jboss.msc.service.StartException in service org.wildfly.security.key-store.bcfks_keystore: WFLYELY00004: Unable to start the service.
> at org.wildfly.extension.elytron@4.0.0.CR1-redhat-1-20180228//org.wildfly.extension.elytron.KeyStoreService.start(KeyStoreService.java:148)
> at org.jboss.msc@1.3.2.Final-redhat-1//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714)
> at org.jboss.msc@1.3.2.Final-redhat-1//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693)
> at org.jboss.msc@1.3.2.Final-redhat-1//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540)
> at org.jboss.threads@2.3.1.Final-redhat-1//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.1.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads@2.3.1.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads@2.3.1.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.base/java.lang.Thread.run(Thread.java:844)
> Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYELY00012: No suitable provider found for type 'BCFKS'
> at org.wildfly.extension.elytron@4.0.0.CR1-redhat-1-20180228//org.wildfly.extension.elytron.KeyStoreService.resolveProvider(KeyStoreService.java:156)
> at org.wildfly.extension.elytron@4.0.0.CR1-redhat-1-20180228//org.wildfly.extension.elytron.KeyStoreService.start(KeyStoreService.java:110)
> ... 8 more
> {code}
> * With same java I can run succesfully this java code
> {code:java|title=TestBCLoaded.java}
> import java.security.*;
> public class TestBCLoaded {
> public static void main(String[] args) {
> Provider p = Security.getProvider("org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider");
> if (p==null){
> System.out.println("Not Loaded: org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider");
> }
> p = Security.getProvider("BouncyCastleFipsProvider");
> if (p==null){
> System.out.println("Not Loaded: BouncyCastleFipsProvider");
> }
> p = Security.getProvider("BCFIPS");
> if (p==null){
> System.out.println("Not Loaded: BCFIPS");
> } else {
> System.out.println("Provider name is " + p.getName());
> System.out.println("Provider version # is " + p.getVersion());
> System.out.println("Provider info is " + p.getInfo());
> }
> }
> }
> {code}
> {code}
> [mchoma@localhost jdk9Test]$ java -cp .:/home/mchoma/.m2/repository/org/bouncycastle/fips/bc-fips/1.0.0/bc-fips-1.0.0.jar TestBCLoaded
> Not Loaded: org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider
> Not Loaded: BouncyCastleFipsProvider
> Provider name is BCFIPS
> Provider version # is 0.9
> Provider info is BouncyCastle Security Provider (FIPS edition) v0.90
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10014) Unable to configure comma delimited enabled-protocols in remote-connector
by Nagaraju Chitimilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-10014?page=com.atlassian.jira.plugin... ]
Nagaraju Chitimilla edited comment on WFLY-10014 at 3/14/18 7:00 AM:
---------------------------------------------------------------------
I have tried escaping the with the following options, but its always giving exception:
<param name="enabled-protocols" value="TLSv1.1\\,TLSv1.2"/>
*Error:* java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1\\,TLSv1.2
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
*Error:*
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
^^^^ Unexpected character '\' (code 92) excepted space, or '>' or "/>"
at [row,col {unknown-source}]: [656,53]
Can you let me know the exact behavior?
Thanks in advance
-Nagaraju
was (Author: n_nagraj321):
I have tried escaping the with the following options, but its always giving exception:
<param name="enabled-protocols" value="TLSv1.1\\,TLSv1.2"/>
*Error:* java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1\\,TLSv1.2
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
*Error:*
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
^^^^ Unexpected character '\' (code 92) excepted space, or '>' or "/>"
at [row,col {unknown-source}]: [656,53]
Can you let me know the exact behavior?
Thanks in advance
-Nagaraju
> Unable to configure comma delimited enabled-protocols in remote-connector
> -------------------------------------------------------------------------
>
> Key: WFLY-10014
> URL: https://issues.jboss.org/browse/WFLY-10014
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 12.0.0.Final
> Reporter: Nagaraju Chitimilla
> Assignee: Jeff Mesnil
> Priority: Critical
>
> When I want to configure enabled SSL protocols, Netty requires to use comma delimited list to be passed into enabled-protocols param in remote-connector
> {noformat}
> <param name="enabled-protocols" value="TLSv1.1,TLSv1.2"/>
> {noformat}
> But when comma is used in value in configuration string passed into ActiveMQRaUtils.parseConfig, parsing fails:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1,TLSv1.2;trustStorePassword=N0tall0wed;keyStorePassword=N0tall0wed;port=61616;localAddress=0.0.0.0;sslEnabled=true;host=localhost;trustStorePath=C:/ActiveMQ/conf/keystore.p12;keyStorePath=C:/ActiveMQ/conf/keystore.p12
> at org.apache.activemq.artemis.ra.ActiveMQRaUtils.parseConfig(ActiveMQRaUtils.java:205)
> at org.apache.activemq.artemis.ra.ActiveMQResourceAdapter.setConnectionParameters(ActiveMQResourceAdapter.java:342)
> ... 18 more
> {code}
> I set this as critical as it prevent setting more then one allowed SSLContext protocol.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10014) Unable to configure comma delimited enabled-protocols in remote-connector
by Nagaraju Chitimilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-10014?page=com.atlassian.jira.plugin... ]
Nagaraju Chitimilla edited comment on WFLY-10014 at 3/14/18 6:59 AM:
---------------------------------------------------------------------
I have tried escaping the with the following options, but its always giving exception:
<param name="enabled-protocols" value="TLSv1.1\\\\,TLSv1.2"/>
*Error:* java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1\\,TLSv1.2
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
*Error:*
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
^^^^ Unexpected character '\' (code 92) excepted space, or '>' or "/>"
at [row,col {unknown-source}]: [656,53]
Can you let me know the exact behavior?
Thanks in advance
-Nagaraju
was (Author: n_nagraj321):
I have tried escaping the with the following options, but its always giving exception:
<param name="enabled-protocols" value="TLSv1.1\\,TLSv1.2"/>
*Error:* java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1\\,TLSv1.2
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
*Error:*
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
^^^^ Unexpected character '\' (code 92) excepted space, or '>' or "/>"
at [row,col {unknown-source}]: [656,53]
Can you let me know the exact behavior?
Thanks in advance
-Nagaraju
> Unable to configure comma delimited enabled-protocols in remote-connector
> -------------------------------------------------------------------------
>
> Key: WFLY-10014
> URL: https://issues.jboss.org/browse/WFLY-10014
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 12.0.0.Final
> Reporter: Nagaraju Chitimilla
> Assignee: Jeff Mesnil
> Priority: Critical
>
> When I want to configure enabled SSL protocols, Netty requires to use comma delimited list to be passed into enabled-protocols param in remote-connector
> {noformat}
> <param name="enabled-protocols" value="TLSv1.1,TLSv1.2"/>
> {noformat}
> But when comma is used in value in configuration string passed into ActiveMQRaUtils.parseConfig, parsing fails:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1,TLSv1.2;trustStorePassword=N0tall0wed;keyStorePassword=N0tall0wed;port=61616;localAddress=0.0.0.0;sslEnabled=true;host=localhost;trustStorePath=C:/ActiveMQ/conf/keystore.p12;keyStorePath=C:/ActiveMQ/conf/keystore.p12
> at org.apache.activemq.artemis.ra.ActiveMQRaUtils.parseConfig(ActiveMQRaUtils.java:205)
> at org.apache.activemq.artemis.ra.ActiveMQResourceAdapter.setConnectionParameters(ActiveMQResourceAdapter.java:342)
> ... 18 more
> {code}
> I set this as critical as it prevent setting more then one allowed SSLContext protocol.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10014) Unable to configure comma delimited enabled-protocols in remote-connector
by Nagaraju Chitimilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-10014?page=com.atlassian.jira.plugin... ]
Nagaraju Chitimilla edited comment on WFLY-10014 at 3/14/18 6:59 AM:
---------------------------------------------------------------------
I have tried escaping the with the following options, but its always giving exception:
<param name="enabled-protocols" value="TLSv1.1\\,TLSv1.2"/>
*Error:* java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1\\,TLSv1.2
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
*Error:*
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
^^^^ Unexpected character '\' (code 92) excepted space, or '>' or "/>"
at [row,col {unknown-source}]: [656,53]
Can you let me know the exact behavior?
Thanks in advance
-Nagaraju
was (Author: n_nagraj321):
I have tried escaping the with the following options, but its always giving exception:
<param name="enabled-protocols" value="TLSv1.1\\\\,TLSv1.2"/>
*Error:* java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1\\,TLSv1.2
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
*Error:*
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
^^^^ Unexpected character '\' (code 92) excepted space, or '>' or "/>"
at [row,col {unknown-source}]: [656,53]
Can you let me know the exact behavior?
Thanks in advance
-Nagaraju
> Unable to configure comma delimited enabled-protocols in remote-connector
> -------------------------------------------------------------------------
>
> Key: WFLY-10014
> URL: https://issues.jboss.org/browse/WFLY-10014
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 12.0.0.Final
> Reporter: Nagaraju Chitimilla
> Assignee: Jeff Mesnil
> Priority: Critical
>
> When I want to configure enabled SSL protocols, Netty requires to use comma delimited list to be passed into enabled-protocols param in remote-connector
> {noformat}
> <param name="enabled-protocols" value="TLSv1.1,TLSv1.2"/>
> {noformat}
> But when comma is used in value in configuration string passed into ActiveMQRaUtils.parseConfig, parsing fails:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1,TLSv1.2;trustStorePassword=N0tall0wed;keyStorePassword=N0tall0wed;port=61616;localAddress=0.0.0.0;sslEnabled=true;host=localhost;trustStorePath=C:/ActiveMQ/conf/keystore.p12;keyStorePath=C:/ActiveMQ/conf/keystore.p12
> at org.apache.activemq.artemis.ra.ActiveMQRaUtils.parseConfig(ActiveMQRaUtils.java:205)
> at org.apache.activemq.artemis.ra.ActiveMQResourceAdapter.setConnectionParameters(ActiveMQResourceAdapter.java:342)
> ... 18 more
> {code}
> I set this as critical as it prevent setting more then one allowed SSLContext protocol.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10014) Unable to configure comma delimited enabled-protocols in remote-connector
by Nagaraju Chitimilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-10014?page=com.atlassian.jira.plugin... ]
Nagaraju Chitimilla edited comment on WFLY-10014 at 3/14/18 6:59 AM:
---------------------------------------------------------------------
I have tried escaping the with the following options, but its always giving exception:
<param name="enabled-protocols" value="TLSv1.1\\\,TLSv1.2"/>
*Error:* java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1\\,TLSv1.2
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
*Error:*
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
^^^^ Unexpected character '\' (code 92) excepted space, or '>' or "/>"
at [row,col {unknown-source}]: [656,53]
Can you let me know the exact behavior?
Thanks in advance
-Nagaraju
was (Author: n_nagraj321):
I have tried escaping the with the following options, but its always giving exception:
<param name="enabled-protocols" value="TLSv1.1\\,TLSv1.2"/>
*Error:* java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1\\,TLSv1.2
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
*Error:*
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
^^^^ Unexpected character '\' (code 92) excepted space, or '>' or "/>"
at [row,col {unknown-source}]: [656,53]
Can you let me know the exact behavior?
Thanks in advance
-Nagaraju
> Unable to configure comma delimited enabled-protocols in remote-connector
> -------------------------------------------------------------------------
>
> Key: WFLY-10014
> URL: https://issues.jboss.org/browse/WFLY-10014
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 12.0.0.Final
> Reporter: Nagaraju Chitimilla
> Assignee: Jeff Mesnil
> Priority: Critical
>
> When I want to configure enabled SSL protocols, Netty requires to use comma delimited list to be passed into enabled-protocols param in remote-connector
> {noformat}
> <param name="enabled-protocols" value="TLSv1.1,TLSv1.2"/>
> {noformat}
> But when comma is used in value in configuration string passed into ActiveMQRaUtils.parseConfig, parsing fails:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1,TLSv1.2;trustStorePassword=N0tall0wed;keyStorePassword=N0tall0wed;port=61616;localAddress=0.0.0.0;sslEnabled=true;host=localhost;trustStorePath=C:/ActiveMQ/conf/keystore.p12;keyStorePath=C:/ActiveMQ/conf/keystore.p12
> at org.apache.activemq.artemis.ra.ActiveMQRaUtils.parseConfig(ActiveMQRaUtils.java:205)
> at org.apache.activemq.artemis.ra.ActiveMQResourceAdapter.setConnectionParameters(ActiveMQResourceAdapter.java:342)
> ... 18 more
> {code}
> I set this as critical as it prevent setting more then one allowed SSLContext protocol.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10014) Unable to configure comma delimited enabled-protocols in remote-connector
by Nagaraju Chitimilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-10014?page=com.atlassian.jira.plugin... ]
Nagaraju Chitimilla commented on WFLY-10014:
--------------------------------------------
I have tried escaping the with the following options, but its always giving exception:
<param name="enabled-protocols" value="TLSv1.1\\,TLSv1.2"/>
*Error:* java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1\\,TLSv1.2
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
*Error:*
<param name="enabled-protocols" value="TLSv1.1"\\,"TLSv1.2"/>
^^^^ Unexpected character '\' (code 92) excepted space, or '>' or "/>"
at [row,col {unknown-source}]: [656,53]
Can you let me know the exact behavior?
Thanks in advance
-Nagaraju
> Unable to configure comma delimited enabled-protocols in remote-connector
> -------------------------------------------------------------------------
>
> Key: WFLY-10014
> URL: https://issues.jboss.org/browse/WFLY-10014
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 12.0.0.Final
> Reporter: Nagaraju Chitimilla
> Assignee: Jeff Mesnil
> Priority: Critical
>
> When I want to configure enabled SSL protocols, Netty requires to use comma delimited list to be passed into enabled-protocols param in remote-connector
> {noformat}
> <param name="enabled-protocols" value="TLSv1.1,TLSv1.2"/>
> {noformat}
> But when comma is used in value in configuration string passed into ActiveMQRaUtils.parseConfig, parsing fails:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1,TLSv1.2;trustStorePassword=N0tall0wed;keyStorePassword=N0tall0wed;port=61616;localAddress=0.0.0.0;sslEnabled=true;host=localhost;trustStorePath=C:/ActiveMQ/conf/keystore.p12;keyStorePath=C:/ActiveMQ/conf/keystore.p12
> at org.apache.activemq.artemis.ra.ActiveMQRaUtils.parseConfig(ActiveMQRaUtils.java:205)
> at org.apache.activemq.artemis.ra.ActiveMQResourceAdapter.setConnectionParameters(ActiveMQResourceAdapter.java:342)
> ... 18 more
> {code}
> I set this as critical as it prevent setting more then one allowed SSLContext protocol.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10014) Unable to configure comma delimited enabled-protocols in remote-connector
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-10014?page=com.atlassian.jira.plugin... ]
Jeff Mesnil resolved WFLY-10014.
--------------------------------
Resolution: Rejected
According to the Artemis code, if the parameters contains a comma, it must be escaped ("\\,") https://github.com/apache/activemq-artemis/blob/master/artemis-ra/src/mai...
> Unable to configure comma delimited enabled-protocols in remote-connector
> -------------------------------------------------------------------------
>
> Key: WFLY-10014
> URL: https://issues.jboss.org/browse/WFLY-10014
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 12.0.0.Final
> Reporter: Nagaraju Chitimilla
> Assignee: Jeff Mesnil
> Priority: Critical
>
> When I want to configure enabled SSL protocols, Netty requires to use comma delimited list to be passed into enabled-protocols param in remote-connector
> {noformat}
> <param name="enabled-protocols" value="TLSv1.1,TLSv1.2"/>
> {noformat}
> But when comma is used in value in configuration string passed into ActiveMQRaUtils.parseConfig, parsing fails:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1,TLSv1.2;trustStorePassword=N0tall0wed;keyStorePassword=N0tall0wed;port=61616;localAddress=0.0.0.0;sslEnabled=true;host=localhost;trustStorePath=C:/ActiveMQ/conf/keystore.p12;keyStorePath=C:/ActiveMQ/conf/keystore.p12
> at org.apache.activemq.artemis.ra.ActiveMQRaUtils.parseConfig(ActiveMQRaUtils.java:205)
> at org.apache.activemq.artemis.ra.ActiveMQResourceAdapter.setConnectionParameters(ActiveMQResourceAdapter.java:342)
> ... 18 more
> {code}
> I set this as critical as it prevent setting more then one allowed SSLContext protocol.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFCORE-3666) Provide Elytron alternative to RoleMappingLoginModule
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3666?page=com.atlassian.jira.plugi... ]
Martin Choma updated WFCORE-3666:
---------------------------------
Description:
In picketbox there is RoleMappingLoginModule [1], which takes role as returned from authorization process and maps to different role. I thought something similar should be configurable with some of Elytron role-mappers. But looking into model/code, it is not obvious to me which of them can be used. I know custom role mapper can be still used, but I wonder if we really do not provide this common funcionality out of the box with Elytron.
Another workaround is to use direct roles from realm (e.g. LDAP ) in target (e.g. web.xml). But seems users tend to map IDM Roles to applicaiton roles.
[1] https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap...
was:
In picketbox there is RoleMappingLoginModule [1], which takes role as returned from authorization process and maps to different role. I thought something similar should be configurable with some of Elytron role-mappers. But looking into model/code, it is not obvious to me which of them can be used. I know custom role mapper can be still used, but I wonder if we really do not provide this common funcionality out of the box with Elytron.
[1] https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap...
> Provide Elytron alternative to RoleMappingLoginModule
> -----------------------------------------------------
>
> Key: WFCORE-3666
> URL: https://issues.jboss.org/browse/WFCORE-3666
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 4.0.0.Final
> Reporter: Martin Choma
>
> In picketbox there is RoleMappingLoginModule [1], which takes role as returned from authorization process and maps to different role. I thought something similar should be configurable with some of Elytron role-mappers. But looking into model/code, it is not obvious to me which of them can be used. I know custom role mapper can be still used, but I wonder if we really do not provide this common funcionality out of the box with Elytron.
> Another workaround is to use direct roles from realm (e.g. LDAP ) in target (e.g. web.xml). But seems users tend to map IDM Roles to applicaiton roles.
> [1] https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10021) org.infinispan.persistence.spi.PersistenceException: org.infinispan.commons.marshall.NotSerializableException: com.rlogistics.rest.FormFillerUtil
by Anand Kumar (JIRA)
[ https://issues.jboss.org/browse/WFLY-10021?page=com.atlassian.jira.plugin... ]
Anand Kumar commented on WFLY-10021:
------------------------------------
Server gets frequent stuck and have to Restart to move on. No other issue observed in the server log.
> org.infinispan.persistence.spi.PersistenceException: org.infinispan.commons.marshall.NotSerializableException: com.rlogistics.rest.FormFillerUtil
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10021
> URL: https://issues.jboss.org/browse/WFLY-10021
> Project: WildFly
> Issue Type: Feature Request
> Environment: Server getting stuck and works after restarting the server.
> Reporter: Anand Kumar
> Assignee: Jason Greene
>
> 05:49:20.273 [Thread-2] INFO org.jboss.as.server - WFLYSRV0220: Server shutdown has been requested.
> 05:49:20.280 [MSC service thread 1-1] INFO o.j.a.c.subsystems.datasources - WFLYJCA0010: Unbound data source [java:jboss/datasources/activitiDB]
> 05:49:20.282 [MSC service thread 1-3] INFO o.jboss.as.connector.deployers.jdbc - WFLYJCA0019: Stopped Driver service with driver-name = rlogistics-execution.war_org.h2.Driver_1_3
> 05:49:20.286 [ServerService Thread Pool -- 69] INFO org.wildfly.extension.undertow - WFLYUT0022: Unregistered web context: /rlogistics-execution
> 05:49:20.316 [MSC service thread 1-1] INFO o.jboss.as.connector.deployers.jdbc - WFLYJCA0019: Stopped Driver service with driver-name = mysql
> 05:49:20.350 [MSC service thread 1-3] INFO org.wildfly.extension.undertow - WFLYUT0019: Host default-host stopping
> 05:49:20.352 [MSC service thread 1-3] INFO o.j.a.c.subsystems.datasources - WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
> 05:49:20.353 [ServerService Thread Pool -- 71] INFO o.i.e.impl.PassivationManagerImpl - ISPN000029: Passivating all entries to disk
> 05:49:20.367 [MSC service thread 1-1] INFO o.jboss.as.connector.deployers.jdbc - WFLYJCA0019: Stopped Driver service with driver-name = h2
> 05:49:20.368 [MSC service thread 1-1] INFO com.arjuna.ats.jbossatx - ARJUNA032018: Destroying TransactionManagerService
> 05:49:20.369 [MSC service thread 1-1] INFO com.arjuna.ats.jbossatx - ARJUNA032014: Stopping transaction recovery manager
> 05:49:20.396 [ServerService Thread Pool -- 71] WARN o.i.factories.ComponentRegistry - ISPN000189: While stopping a cache or cache manager, one of its components failed to stop
> org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.eviction.impl.PassivationManagerImpl.passivateAll() throws org.infinispan.persistence.spi.PersistenceException on object of type PassivationManagerImpl
> at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:171) ~[infinispan-commons-7.2.3.Final.jar!/:7.2.3.Final]
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:869) ~[infinispan-core-7.2.3.Final.jar!/:7.2.3.Final]
> at org.infinispan.factories.AbstractComponentRegistry.internalStop(AbstractComponentRegistry.java:674) ~[na:na]
> at org.infinispan.factories.AbstractComponentRegistry.stop(AbstractComponentRegistry.java:552) ~[na:na]
> at org.infinispan.factories.ComponentRegistry.stop(ComponentRegistry.java:243) ~[na:na]
> at org.infinispan.cache.impl.CacheImpl.stop(CacheImpl.java:872) [infinispan-core-7.2.3.Final.jar!/:7.2.3.Final]
> at org.infinispan.cache.impl.CacheImpl.stop(CacheImpl.java:867) [infinispan-core-7.2.3.Final.jar!/:7.2.3.Final]
> at org.infinispan.cache.impl.AbstractDelegatingCache.stop(AbstractDelegatingCache.java:332) [infinispan-core-7.2.3.Final.jar!/:7.2.3.Final]
> at org.wildfly.clustering.infinispan.spi.service.CacheBuilder.stop(CacheBuilder.java:87) [wildfly-clustering-infinispan-spi-9.0.2.Final.jar!/:9.0.2.Final]
> at org.wildfly.clustering.service.AsynchronousServiceBuilder$2.run(AsynchronousServiceBuilder.java:130) [wildfly-clustering-service-9.0.2.Final.jar!/:9.0.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_102]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_102]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_102]
> at org.jboss.threads.JBossThread.run(JBossThread.java:320) [jboss-threads-2.2.0.Final.jar!/:2.2.0.Final]
> Caused by: org.infinispan.persistence.spi.PersistenceException: org.infinispan.persistence.spi.PersistenceException: org.infinispan.commons.marshall.NotSerializableException: com.rlogistics.rest.FormFillerUtil
> at org.infinispan.persistence.file.SingleFileStore.write(SingleFileStore.java:370) ~[infinispan-core-7.2.3.Final.jar!/:7.2.3.Final]
> at org.infinispan.persistence.manager.PersistenceManagerImpl.writeToAllStores(PersistenceManagerImpl.java:462) ~[infinispan-core-7.2.3.Final.jar!/:7.2.3.Final]
> at org.infinispan.eviction.impl.PassivationManagerImpl.passivateAll(PassivationManagerImpl.java:104) ~[infinispan-core-7.2.3.Final.jar!/:7.2.3.Final]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_102]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_102]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_102]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_102]
> at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:168) ~[infinispan-commons-7.2.3.Final.jar!/:7.2.3.Final]
> ... 13 common frames omitted
> Caused by: org.infinispan.persistence.spi.PersistenceException: org.infinispan.commons.marshall.NotSerializableException: com.rlogistics.rest.FormFillerUtil
> at org.infinispan.marshall.core.MarshalledEntryImpl.marshall(MarshalledEntryImpl.java:107) ~[infinispan-core-7.2.3.Final.jar!/:7.2.3.Final]
> at org.infinispan.marshall.core.MarshalledEntryImpl.getValueBytes(MarshalledEntryImpl.java:88) ~[infinispan-core-7.2.3.Final.jar!/:7.2.3.Final]
> at org.infinispan.persistence.file.SingleFileStore.write(SingleFileStore.java:327) ~[infinispan-core-7.2.3.Final.jar!/:7.2.3.Final]
> ... 20 common frames omitted
> Caused by: org.infinispan.commons.marshall.NotSerializableException: com.rlogistics.rest.FormFillerUtil
> Caused by: org.jboss.marshalling.TraceInformation: null
> 05:49:20.400 [ServerService Thread Pool -- 71] INFO org.jboss.as.clustering.infinispan - WFLYCLINF0003: Stopped rlogistics-execution.war cache from web container
> 05:49:20.415 [MSC service thread 1-4] INFO org.wildfly.extension.undertow - WFLYUT0008: Undertow HTTP listener default suspending
> 05:49:20.416 [MSC service thread 1-4] INFO org.wildfly.extension.undertow - WFLYUT0007: Undertow HTTP listener default stopped, was bound to /0.0.0.0:9080
> 05:49:20.418 [MSC service thread 1-4] INFO org.wildfly.extension.undertow - WFLYUT0004: Undertow 1.2.9.Final stopping
> 05:49:20.464 [MSC service thread 1-2] INFO org.jboss.as.server.deployment - WFLYSRV0028: Stopped deployment rlogistics-execution.war (runtime-name: rlogistics-execution.war) in 171ms
> 05:49:20.469 [MSC service thread 1-2] INFO org.jboss.as - WFLYSRV0050: WildFly Full 9.0.2.Final (WildFly Core 1.0.2.Final) stopped in 175ms
> JBoss Modules version 1.4.3.Final
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months