June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (HAWKULARQE-132) [QE] - JMAN4-114 - Discovery and Instrumentation of EAP installations on VMs managed by CloudForms

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-132?page=com.atlassian.jira.pl... ] Hayk Hovsepyan updated HAWKULARQE-132: -------------------------------------- Description: See [JMAN4-114|https://issues.jboss.org/browse/JMAN4-114] Requirement's Test Plan Document: https://mojo.redhat.com/docs/DOC-1141225 was:See [JMAN4-114|https://issues.jboss.org/browse/JMAN4-114] > [QE] - JMAN4-114 - Discovery and Instrumentation of EAP installations on VMs managed by CloudForms > -------------------------------------------------------------------------------------------------- > > Key: HAWKULARQE-132 > URL: https://issues.jboss.org/browse/HAWKULARQE-132 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Michael Foley > Priority: Critical > Labels: 5.0, mm-integration-hawkular-qe > > See [JMAN4-114|https://issues.jboss.org/browse/JMAN4-114] > Requirement's Test Plan Document: https://mojo.redhat.com/docs/DOC-1141225 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-14) [QE] - JMAN4-117 - Specify the middleware metrics to collect

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-14?page=com.atlassian.jira.plu... ] Hayk Hovsepyan updated HAWKULARQE-14: ------------------------------------- Labels: (was: mm-integration-hawkular-qe) > [QE] - JMAN4-117 - Specify the middleware metrics to collect > ------------------------------------------------------------ > > Key: HAWKULARQE-14 > URL: https://issues.jboss.org/browse/HAWKULARQE-14 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Matt Mahoney > Priority: Minor > > See [JMAN4-117|https://issues.jboss.org/browse/JMAN4-117] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1254) Elytron client configuration file throws ConfigXMLParseException when credential key-store-reference is used

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-1254?page=com.atlassian.jira.plugin.s... ] Ondrej Lukas updated ELY-1254: ------------------------------ Affects Version/s: 1.1.0.Beta52 > Elytron client configuration file throws ConfigXMLParseException when credential key-store-reference is used > ------------------------------------------------------------------------------------------------------------ > > Key: ELY-1254 > URL: https://issues.jboss.org/browse/ELY-1254 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta52 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Blocker > > When Elytron client configuration file includes configuration.authentication-client.authentication-configurations.configuration.credentials.key-store-reference element then ConfigXMLParseException is thrown during parsing of configuration file. This issue can be caused by JBEAP-11691. > For following configuration file: > {code} > <configuration> > <authentication-client xmlns="urn:elytron:1.0"> > <authentication-rules> > <rule use-configuration="default"/> > </authentication-rules> > <authentication-configurations> > <configuration name="default"> > <sasl-mechanism-selector selector="PLAIN"/> > <credentials> > <key-store-reference key-store-name="clientKeyStore"> > <key-store-clear-password password="secret"/> > </key-store-reference> > </credentials> > <providers> > <use-service-loader/> > </providers> > </configuration> > </authentication-configurations> > <key-stores> > <key-store name="clientKeyStore" type="JKS"> > <file name="/path/to/some/client.keystore"/> > <key-store-clear-password password="secretKeyStore"/> > </key-store> > </key-stores> > </authentication-client> > </configuration> > {code} > following exception is thrown: > {code} > org.wildfly.client.config.ConfigXMLParseException: ELY01135: Failed to load keystore data > at file:/path/to/some/wildfly-config.xml:10:74 > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseKeyStoreRefType$41(ElytronXmlParser.java:1448) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseCredentialsType$25(ElytronXmlParser.java:932) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$andThenOp$23(ElytronXmlParser.java:919) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseCredentialsType$35(ElytronXmlParser.java:986) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationConfigurationType$18(ElytronXmlParser.java:715) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$andThenOp$23(ElytronXmlParser.java:919) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationConfigurationType$22(ElytronXmlParser.java:763) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationRuleType$7(ElytronXmlParser.java:599) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseRulesType$8(ElytronXmlParser.java:623) > at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:323) > at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:185) > at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:146) > at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:38) > ... 18 more > Caused by: java.security.NoSuchAlgorithmException: ELY08028: Invalid algorithm "clear" > at org.wildfly.security.password.PasswordFactory.getInstance(PasswordFactory.java:121) > at org.wildfly.security.password.PasswordFactory.getInstance(PasswordFactory.java:75) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseKeyStoreRefType$41(ElytronXmlParser.java:1423) > ... 30 more > {code} > It seems that mentioned configuration file does not result to ConfigXMLParseException in EAP 7.1.0.DR19. > We request blocker flag since using key-store-reference as credentials in configuration is not possible in Elytron client configuration file which breaks feature in RFE EAP7-567 Client Side Security (Elytron Client). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1254) Elytron client configuration file throws ConfigXMLParseException when credential key-store-reference is used

by Ondrej Lukas (JIRA)

Ondrej Lukas created ELY-1254: --------------------------------- Summary: Elytron client configuration file throws ConfigXMLParseException when credential key-store-reference is used Key: ELY-1254 URL: https://issues.jboss.org/browse/ELY-1254 Project: WildFly Elytron Issue Type: Bug Reporter: Ondrej Lukas Assignee: Darran Lofthouse Priority: Blocker When Elytron client configuration file includes configuration.authentication-client.authentication-configurations.configuration.credentials.key-store-reference element then ConfigXMLParseException is thrown during parsing of configuration file. This issue can be caused by JBEAP-11691. For following configuration file: {code} <configuration> <authentication-client xmlns="urn:elytron:1.0"> <authentication-rules> <rule use-configuration="default"/> </authentication-rules> <authentication-configurations> <configuration name="default"> <sasl-mechanism-selector selector="PLAIN"/> <credentials> <key-store-reference key-store-name="clientKeyStore"> <key-store-clear-password password="secret"/> </key-store-reference> </credentials> <providers> <use-service-loader/> </providers> </configuration> </authentication-configurations> <key-stores> <key-store name="clientKeyStore" type="JKS"> <file name="/path/to/some/client.keystore"/> <key-store-clear-password password="secretKeyStore"/> </key-store> </key-stores> </authentication-client> </configuration> {code} following exception is thrown: {code} org.wildfly.client.config.ConfigXMLParseException: ELY01135: Failed to load keystore data at file:/path/to/some/wildfly-config.xml:10:74 at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseKeyStoreRefType$41(ElytronXmlParser.java:1448) at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseCredentialsType$25(ElytronXmlParser.java:932) at org.wildfly.security.auth.client.ElytronXmlParser.lambda$andThenOp$23(ElytronXmlParser.java:919) at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseCredentialsType$35(ElytronXmlParser.java:986) at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationConfigurationType$18(ElytronXmlParser.java:715) at org.wildfly.security.auth.client.ElytronXmlParser.lambda$andThenOp$23(ElytronXmlParser.java:919) at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationConfigurationType$22(ElytronXmlParser.java:763) at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationRuleType$7(ElytronXmlParser.java:599) at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseRulesType$8(ElytronXmlParser.java:623) at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:323) at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:185) at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:146) at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:38) ... 18 more Caused by: java.security.NoSuchAlgorithmException: ELY08028: Invalid algorithm "clear" at org.wildfly.security.password.PasswordFactory.getInstance(PasswordFactory.java:121) at org.wildfly.security.password.PasswordFactory.getInstance(PasswordFactory.java:75) at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseKeyStoreRefType$41(ElytronXmlParser.java:1423) ... 30 more {code} It seems that mentioned configuration file does not result to ConfigXMLParseException in EAP 7.1.0.DR19. We request blocker flag since using key-store-reference as credentials in configuration is not possible in Elytron client configuration file which breaks feature in RFE EAP7-567 Client Side Security (Elytron Client). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-36) IPV6

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-36?page=com.atlassian.jira.plu... ] Hayk Hovsepyan updated HAWKULARQE-36: ------------------------------------- Labels: (was: 5.0) > IPV6 > ---- > > Key: HAWKULARQE-36 > URL: https://issues.jboss.org/browse/HAWKULARQE-36 > Project: Hawkular QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Hayk Hovsepyan > > See: [HAWKULAR-1193|https://issues.jboss.org/browse/HAWKULAR-1193] > Create IPv6 testing environment and run smoke tests on it. > Automate via jenkins job running CFME smoke tests. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-14) [QE] - JMAN4-117 - Specify the middleware metrics to collect

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-14?page=com.atlassian.jira.plu... ] Hayk Hovsepyan updated HAWKULARQE-14: ------------------------------------- Labels: mm-integration-hawkular-qe (was: 5.0 mm-integration-hawkular-qe) > [QE] - JMAN4-117 - Specify the middleware metrics to collect > ------------------------------------------------------------ > > Key: HAWKULARQE-14 > URL: https://issues.jboss.org/browse/HAWKULARQE-14 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Matt Mahoney > Priority: Minor > Labels: mm-integration-hawkular-qe > > See [JMAN4-117|https://issues.jboss.org/browse/JMAN4-117] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1252) Revisit hashed-password and crypt-password credentials in Elytron client configuration file

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1252?page=com.atlassian.jira.plugin.s... ] Jan Kalina reassigned ELY-1252: ------------------------------- Assignee: Jan Kalina (was: Darran Lofthouse) > Revisit hashed-password and crypt-password credentials in Elytron client configuration file > ------------------------------------------------------------------------------------------- > > Key: ELY-1252 > URL: https://issues.jboss.org/browse/ELY-1252 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta52 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Priority: Blocker > > Elytron client configuration file can include {{hashed-password}} or {{crypt-password}} as credentials for configuration. Internally this value is parsed in {{ElytronXmlParser}} and results to instance of {{PasswordSpec}}. However we do not see any SASL mechanism supported by Elytron which is able to work with it. > In case when {{hashed-password}} or {{crypt-password}} seems that cannot be actually used with Elytron then we suggest to remove elements {{hashed-password}} or {{crypt-password}} from Elytron client configuration file. Remove them also from elytron-1_0.xsd file. Otherwise please provide configuration which is able to work with {{hashed-password}} or {{crypt-password}} as credentials for configuration on client side. > We request blocker flag since configuration should not include elements which actually do nothing. Once we release them it can be hard to remove them in later application server version. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2984) HTTP Mechanisms from http-authentication-factory should be sorted in config order, or a default order if not config.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2984?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved JBEAP-11690 to WFCORE-2984: -------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2984 (was: JBEAP-11690) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) > HTTP Mechanisms from http-authentication-factory should be sorted in config order, or a default order if not config. > -------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2984 > URL: https://issues.jboss.org/browse/WFCORE-2984 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.0.Beta27 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2984) HTTP Mechanisms from http-authentication-factory should be sorted in config order, or a default order if not config.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2984?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2984: ------------------------------------- Fix Version/s: 3.0.0.Beta27 > HTTP Mechanisms from http-authentication-factory should be sorted in config order, or a default order if not config. > -------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2984 > URL: https://issues.jboss.org/browse/WFCORE-2984 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.0.Beta27 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2983) Upgrade Elytron Web to 1.0.0.Beta16

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2983?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2983: ------------------------------------- Summary: Upgrade Elytron Web to 1.0.0.Beta16 (was: Upgrade Elytron Web to 1.1.0.Beta16) > Upgrade Elytron Web to 1.0.0.Beta16 > ----------------------------------- > > Key: WFCORE-2983 > URL: https://issues.jboss.org/browse/WFCORE-2983 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Beta27 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2017