July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-812) Kiali - Create TP12 Polarion PQI reports

by Sunil Kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-812?page=com.atlassian.jira.plugin.... ] Sunil Kondkar resolved SWSQE-812. --------------------------------- Resolution: Done > Kiali - Create TP12 Polarion PQI reports > ---------------------------------------- > > Key: SWSQE-812 > URL: https://issues.jboss.org/browse/SWSQE-812 > Project: Kiali QE > Issue Type: QE Task > Reporter: Sunil Kondkar > Assignee: Sunil Kondkar > Priority: Major > Labels: pqi > > Get PQI reports for Kiali: > 1) Check Test case Quality Audit report(No missing data) > 2) PQI reports - Create TP12 test iteration, link this iteration to Kiali TP12 test runs -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-811) Jaeger - Create TP12 Polarion PQI reports

by Sunil Kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-811?page=com.atlassian.jira.plugin.... ] Sunil Kondkar commented on SWSQE-811: ------------------------------------- Linked two more test runs and corrected audit report for no automation script: https://polarion.engineering.redhat.com/polarion/#/project/Jaeger/testrun... https://polarion.engineering.redhat.com/polarion/#/project/Jaeger/testrun... > Jaeger - Create TP12 Polarion PQI reports > ----------------------------------------- > > Key: SWSQE-811 > URL: https://issues.jboss.org/browse/SWSQE-811 > Project: Kiali QE > Issue Type: QE Task > Reporter: Sunil Kondkar > Assignee: Sunil Kondkar > Priority: Major > Labels: pqi > > Get PQI reports for Jaeger: > 1) Check Test case Quality Audit report(No missing data) > 2) PQI reports - Create TP12 test iteration, link this iteration to Jaeger TP12 test runs -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-811) Jaeger - Create TP12 Polarion PQI reports

by Sunil Kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-811?page=com.atlassian.jira.plugin.... ] Sunil Kondkar resolved SWSQE-811. --------------------------------- Resolution: Done > Jaeger - Create TP12 Polarion PQI reports > ----------------------------------------- > > Key: SWSQE-811 > URL: https://issues.jboss.org/browse/SWSQE-811 > Project: Kiali QE > Issue Type: QE Task > Reporter: Sunil Kondkar > Assignee: Sunil Kondkar > Priority: Major > Labels: pqi > > Get PQI reports for Jaeger: > 1) Check Test case Quality Audit report(No missing data) > 2) PQI reports - Create TP12 test iteration, link this iteration to Jaeger TP12 test runs -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12296) Upgrade WildFly Core 10.0.0.Beta2

by Jeff Mesnil (Jira)

Jeff Mesnil created WFLY-12296: ---------------------------------- Summary: Upgrade WildFly Core 10.0.0.Beta2 Key: WFLY-12296 URL: https://issues.jboss.org/browse/WFLY-12296 Project: WildFly Issue Type: Component Upgrade Components: Management Reporter: Jeff Mesnil Assignee: Jeff Mesnil -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3747) Enhance credential-store description related to location and type attributes

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-3747?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3747: -------------------------------- Fix Version/s: 10.0.0.Beta3 (was: 10.0.0.Beta2) > Enhance credential-store description related to location and type attributes > ---------------------------------------------------------------------------- > > Key: WFCORE-3747 > URL: https://issues.jboss.org/browse/WFCORE-3747 > Project: WildFly Core > Issue Type: Enhancement > Components: Security > Reporter: Claudio Miranda > Assignee: Darran Lofthouse > Priority: Major > Fix For: 10.0.0.Beta3 > > > The description for "location" and "type" for credential-store resource is displayed below. > Following discussion of WFCORE-3458, the "location" attribute is required only when the "type" is file based, but the description doesn't says that, the description may be improved to reflect this behavior and list the possible file based types. > When the user doesn't set the "type" attribute it defaults to "JCEKS", but there is no "default" value on resource description for "type" attribute. > {code} > "location" => { > "type" => STRING, > "description" => "File name of credential store storage.", > "attribute-group" => "implementation", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "all-services" > }, > "type" => { > "type" => STRING, > "description" => "The credential store type, e.g. KeyStoreCredentialStore.", > "attribute-group" => "implementation", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "all-services" > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2496) Functionality in WildFly to encrypt database passwords

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-2496?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-2496: -------------------------------- Fix Version/s: 10.0.0.Beta3 (was: 10.0.0.Beta2) > Functionality in WildFly to encrypt database passwords > ------------------------------------------------------ > > Key: WFCORE-2496 > URL: https://issues.jboss.org/browse/WFCORE-2496 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Affects Versions: 3.0.0.Beta7 > Reporter: Carlton Zachary > Assignee: Farah Juma > Priority: Major > Fix For: 10.0.0.Beta3 > > > Is it possible to add functionality to WildFly to encrypt a data source password when the data source is being created? Currently WildFly/EAP stores the password as plain text in the domain.xml/standalone.xml. > Thanks -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-944) truststore path is ignored if provider is not JKS

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-944?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFCORE-944: ------------------------------- Fix Version/s: 10.0.0.Beta3 (was: 10.0.0.Beta2) > truststore path is ignored if provider is not JKS > ------------------------------------------------- > > Key: WFCORE-944 > URL: https://issues.jboss.org/browse/WFCORE-944 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Arto Huusko > Priority: Major > Fix For: 10.0.0.Beta3 > > > truststore configuration ignores the path and relative-to parameters if the truststore provider is anything else than JKS. > This works as documented, but it is not correct. There can be and are truststore implementations that need to load parameters or whatever data from a file, and the current implementation prevents these truststore providers from working. > We have a custom truststore that is loaded from database, and database access parameters are read from a properties file. When trying to use this with Wildfly 9, the keystore engineLoad parameter is passed in as null, even though path and relative-to are configured. > Even standard java supports PKCS12 truststores, where the same problem would occur. > So I would suggest that > - if provider is JKS, path is mandatory > - if provider is not JKS, but path is specified, it is passed to the provider -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4360) Support encrypted expression resolution using a CredentialStore

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4360?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4360: -------------------------------- Fix Version/s: 10.0.0.Beta3 (was: 10.0.0.Beta2) > Support encrypted expression resolution using a CredentialStore > --------------------------------------------------------------- > > Key: WFCORE-4360 > URL: https://issues.jboss.org/browse/WFCORE-4360 > Project: WildFly Core > Issue Type: Feature Request > Components: Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 10.0.0.Beta3 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4314) Enchance keystore CLI commands

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4314?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4314: -------------------------------- Fix Version/s: 10.0.0.Beta3 (was: 10.0.0.Beta2) > Enchance keystore CLI commands > ------------------------------ > > Key: WFCORE-4314 > URL: https://issues.jboss.org/browse/WFCORE-4314 > Project: WildFly Core > Issue Type: Enhancement > Components: Security > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Major > Fix For: 10.0.0.Beta3 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4227) Add the ability for the CLI SSL security commands to be able to obtain a server certificate from Let's Encrypt

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4227?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4227: -------------------------------- Fix Version/s: 10.0.0.Beta3 (was: 10.0.0.Beta2) > Add the ability for the CLI SSL security commands to be able to obtain a server certificate from Let's Encrypt > -------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4227 > URL: https://issues.jboss.org/browse/WFCORE-4227 > Project: WildFly Core > Issue Type: Feature Request > Reporter: Marek Marusic > Assignee: Marek Marusic > Priority: Major > Fix For: 10.0.0.Beta3 > > > WFCORE-3447 introduced high-level security commands (ssl enable-ssl-management and ssl enable-ssl-http-server) for enabling one-way and two-way SSL easily. To generate the server certificate, these high-level security commands made use of key-store management operations to generate a self-signed certificate. Since it is now possible to obtain certificates from the Let's Encrypt certificate authority using the CLI, the high-level security commands should be updated so that in addition to being able to generate a self-signed server certificate, they can also obtain a server certificate from Let's Encrypt. Details on the new management operations for obtaining and managing certificates from Let's Encrypt can be found in the analysis document and in this blog post. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

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 July 2019