January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-234) Scalability Testing on Configurations (Number of Services on Mesh)

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-234?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-234: ------------------------------------------ Sprint: Kiali QE Sprint 7, Kiali Sprint #16 (was: Kiali QE Sprint 7) > Scalability Testing on Configurations (Number of Services on Mesh) > ------------------------------------------------------------------ > > Key: SWSQE-234 > URL: https://issues.jboss.org/browse/SWSQE-234 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > As an administrator, I want to know what is "theoretical" limit of test meshes configurations (number of services, versions) that can be displayed on Kiali UI. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11577) Upgrade WildFly Core 8.0.0.Beta2

by Jeff Mesnil (Jira)

Jeff Mesnil created WFLY-11577: ---------------------------------- Summary: Upgrade WildFly Core 8.0.0.Beta2 Key: WFLY-11577 URL: https://issues.jboss.org/browse/WFLY-11577 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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-629) Enabled automatic encryption of passwords stored in configuration

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-629?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFCORE-629: ------------------------------- Fix Version/s: 8.0.0.Beta3 (was: 8.0.0.Beta2) > Enabled automatic encryption of passwords stored in configuration > ----------------------------------------------------------------- > > Key: WFCORE-629 > URL: https://issues.jboss.org/browse/WFCORE-629 > Project: WildFly Core > Issue Type: Feature Request > Components: Management, Security > Environment: Wildfly 9 > Reporter: Jason Shepherd > Assignee: Darran Lofthouse > Priority: Major > Fix For: 8.0.0.Beta3 > > > Currently encrypting passwords such as Datasource passwords can only be done 'after the fact'. You have to create the datasource first, then retrospectively store the password in the vault and dereference it in the configuration. > It would be great if could turn on automatic storage of passwords in the vault so that when you create a Datasource password, or add a resource adapter which specifies a remote resource password, those passwords were automatically added to the vault, and deferenced in the configuration file. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3832) Support hex encoding in jdbc-realm for elytron

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-3832?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3832: -------------------------------- Fix Version/s: 8.0.0.Beta3 (was: 8.0.0.Beta2) > Support hex encoding in jdbc-realm for elytron > ---------------------------------------------- > > Key: WFCORE-3832 > URL: https://issues.jboss.org/browse/WFCORE-3832 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Affects Versions: 5.0.0.Alpha7 > Reporter: Jan Kalina > Assignee: Darran Lofthouse > Priority: Major > Labels: elytron > Fix For: 8.0.0.Beta3 > > > Old database login-module can be configured passing the attribute {{hashEncoding}}, for example: > {code:xml} > <login-module code="Database" flag="required"> > <module-option name="dsJndiName" value="java:jboss/datasources/ExampleDS"/> > <module-option name="principalsQuery" value="SELECT password FROM User WHERE username = ?"/> > <module-option name="rolesQuery" value="SELECT role, 'Roles' FROM User WHERE username = ?"/> > <module-option name="hashAlgorithm" value="SHA-1"/> > <module-option name="hashEncoding" value="hex"/> > <module-option name="hashCharset" value="UTF-8"/> > </login-module> > {code} > Currently jdbc-realm in elytron only uses base64 encoding if hash is stored in a text column. This way the migration is more complicated cos the password hash is not valid changing from old security system to elytron. > Think also about the charset attribute. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3542) Elytron JDBC realm password mapping is not consistent with underlying implementation

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-3542?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3542: -------------------------------- Fix Version/s: 8.0.0.Beta3 (was: 8.0.0.Beta2) > Elytron JDBC realm password mapping is not consistent with underlying implementation > ------------------------------------------------------------------------------------ > > Key: WFCORE-3542 > URL: https://issues.jboss.org/browse/WFCORE-3542 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: David Lloyd > Assignee: Darran Lofthouse > Priority: Major > Fix For: 8.0.0.Beta3 > > > There is no way to configure the JDBC realm to use modular crypt in WildFly, even though the underlying realm does support it. > The problem is that the *{{salt-index}} and {{itereration-count-index}} attributes should be optional*, and if they not given, a value of {{-1}} should be passed to the mapper. By omitting both of these values, the database column values will then be recognized as modular-crypt strings. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

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: 8.0.0.Beta3 (was: 8.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: Darran Lofthouse > Priority: Major > Fix For: 8.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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4150) Support automatically adding / updating credentials in the CredentialStore

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4150?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4150: -------------------------------- Fix Version/s: 8.0.0.Beta3 (was: 8.0.0.Beta2) > Support automatically adding / updating credentials in the CredentialStore > -------------------------------------------------------------------------- > > Key: WFCORE-4150 > URL: https://issues.jboss.org/browse/WFCORE-4150 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 8.0.0.Beta3 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4089) Update subsystem and core-model tests to use EAP 7.2.0 rather than WF14

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4089?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4089: -------------------------------- Fix Version/s: 8.0.0.Beta3 (was: 8.0.0.Beta2) > Update subsystem and core-model tests to use EAP 7.2.0 rather than WF14 > ----------------------------------------------------------------------- > > Key: WFCORE-4089 > URL: https://issues.jboss.org/browse/WFCORE-4089 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Kabir Khan > Assignee: Jeff Mesnil > Priority: Blocker > Labels: blocker-WF16 > Fix For: 8.0.0.Beta3 > > > Once EAP 7.2.0 is out, remove ModelTestControllerVersion.EAP_7_2_0_TMP and add EAP_7_2_0 proper, and go through and adjust all the tests using the tmp version. I think this is ok, as there are some more advances subsystem tests which specify additional maven artifacts. Those maven artifacts will need to be updated to use the proper EAP 7.2.0 artifacts once it is released, and having to do this replacement will serve as a reminder. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3997) Add HostExcludeResourceDefinition.KnownRelease items for EAP 7.2

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-3997?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3997: -------------------------------- Fix Version/s: 8.0.0.Beta3 (was: 8.0.0.Beta2) > Add HostExcludeResourceDefinition.KnownRelease items for EAP 7.2 > ---------------------------------------------------------------- > > Key: WFCORE-3997 > URL: https://issues.jboss.org/browse/WFCORE-3997 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Martin Simka > Assignee: Jeff Mesnil > Priority: Blocker > Labels: blocker-WF15 > Fix For: 8.0.0.Beta3 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3983) Update the WildFly Elytron Subsystem to use the new MSC Service API

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-3983?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3983: -------------------------------- Fix Version/s: 8.0.0.Beta3 (was: 8.0.0.Beta2) > Update the WildFly Elytron Subsystem to use the new MSC Service API > ------------------------------------------------------------------- > > Key: WFCORE-3983 > URL: https://issues.jboss.org/browse/WFCORE-3983 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Priority: Major > Fix For: 8.0.0.Beta3 > > > At some point we want to consider breaking the subsystem into smaller chunks to allow a more selective subset of functionality to be selected - before we do that it would be good to clean up the general approach in the subsystem. We have trivial resources and services within the subsystem but the new MSC APIs may simpify a lot of this. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 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 January 2019