May 2018 - jboss-jira - Jboss List Archives

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

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3542?page=com.atlassian.jira.plugi... ] Jan Kalina updated WFCORE-3542: ------------------------------- Description: 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. was: 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. > 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 > > 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.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3787) JMX audit logging should support all the handlers supported by core audit logging

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3787?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-3787: --------------------------------------- My main concern is we the same handlers in different subsystems with different attributes/child resources. I just think the resources need to be consistent. I do agree with smaller subsystems gives better slimming opportunities. That's the main reason I thought using known categories would be nice. For example if the logging subsystem is removed and a different log manager is used it would be easy for the user to turn on/off audit logging. That said I do understand that security restrictions is an issue there. > JMX audit logging should support all the handlers supported by core audit logging > --------------------------------------------------------------------------------- > > Key: WFCORE-3787 > URL: https://issues.jboss.org/browse/WFCORE-3787 > Project: WildFly Core > Issue Type: Feature Request > Components: JMX > Affects Versions: 5.0.0.Alpha5 > Reporter: Yeray Borges > Assignee: Yeray Borges > > Users can enable audit logging for the management interfaces, which will log all operations performed using the management console, management CLI, or custom application that uses the Management API. > JMX subsystem can use the handlers defined for audit logging, but at this moment, only {{file-handler}} and {{syslog-handler}} can be used in JMX subsystem. > This issue will extend the list of supported handlers for JMX subsystem to all handlers supported by core audit logging. > The handlers supported by core audit logging are: > * file-handler > * in-memory-handler > * periodic-rotating-file-handler > * size-rotating-file-handler > * syslog-handler -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-81) Change license name

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-81?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro updated AG-81: ---------------------------- Summary: Change license name (was: Change licence name) > Change license name > ------------------- > > Key: AG-81 > URL: https://issues.jboss.org/browse/AG-81 > Project: Agroal > Issue Type: Bug > Components: build > Affects Versions: 0.5 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Minor > Fix For: 0.6 > > > The license name must be one from https://spdx.org/licenses/ ... therefore the right name should be "Apache License 2.0". > Note that this is not a re-licence of the code. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-81) Change license name

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-81?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro updated AG-81: ---------------------------- Description: The license name must be one from https://spdx.org/licenses/ ... therefore the right name should be "Apache License 2.0". Note that this is not a re-licensing of the code. was: The license name must be one from https://spdx.org/licenses/ ... therefore the right name should be "Apache License 2.0". Note that this is not a re-licence of the code. > Change license name > ------------------- > > Key: AG-81 > URL: https://issues.jboss.org/browse/AG-81 > Project: Agroal > Issue Type: Bug > Components: build > Affects Versions: 0.5 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Minor > Fix For: 0.6 > > > The license name must be one from https://spdx.org/licenses/ ... therefore the right name should be "Apache License 2.0". > Note that this is not a re-licensing of the code. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-81) Change license name

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-81?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro updated AG-81: ---------------------------- Fix Version/s: 0.6 > Change license name > ------------------- > > Key: AG-81 > URL: https://issues.jboss.org/browse/AG-81 > Project: Agroal > Issue Type: Bug > Components: build > Affects Versions: 0.5 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Minor > Fix For: 0.6 > > > The license name must be one from https://spdx.org/licenses/ ... therefore the right name should be "Apache License 2.0". > Note that this is not a re-licensing of the code. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-81) Change license name

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-81?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-81. ----------------------------- Resolution: Done > Change license name > ------------------- > > Key: AG-81 > URL: https://issues.jboss.org/browse/AG-81 > Project: Agroal > Issue Type: Bug > Components: build > Affects Versions: 0.5 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Minor > Fix For: 0.6 > > > The license name must be one from https://spdx.org/licenses/ ... therefore the right name should be "Apache License 2.0". > Note that this is not a re-licensing of the code. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-81) Change licence name

by Luis Barreiro (JIRA)

Luis Barreiro created AG-81: ------------------------------- Summary: Change licence name Key: AG-81 URL: https://issues.jboss.org/browse/AG-81 Project: Agroal Issue Type: Bug Components: build Affects Versions: 0.5 Reporter: Luis Barreiro Assignee: Luis Barreiro Priority: Minor The license name must be one from https://spdx.org/licenses/ ... therefore the right name should be "Apache License 2.0". Note that this is not a re-licence of the code. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1581) Release WildFly Elytron 1.3.2.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1581: ------------------------------------- Summary: Release WildFly Elytron 1.3.2.Final Key: ELY-1581 URL: https://issues.jboss.org/browse/ELY-1581 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.3.2.CR1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3836) Add operation to read the identities of a realm

by Claudio Miranda (JIRA)

Claudio Miranda created WFCORE-3836: --------------------------------------- Summary: Add operation to read the identities of a realm Key: WFCORE-3836 URL: https://issues.jboss.org/browse/WFCORE-3836 Project: WildFly Core Issue Type: Feature Request Components: Security Reporter: Claudio Miranda Assignee: Darran Lofthouse The following realm resources contains operations to add, read, remove identity, but there is no operation to read all or a partial list of identities of a realm. It would improve usability on HAL to list all or a partial list of identities. The realm resources are: custom-modifiable-realm, filesystem-realm, properties-realm -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3722) WFCORE POM contains duplicate version properties after component-matrix version revert

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3722?page=com.atlassian.jira.plugi... ] Chao Wang commented on WFCORE-3722: ----------------------------------- Actually, it was revealed by WFCORE-3803. It was "WildFly Build Tools version properties is set in two different POMs" before the component-matrix, Now it's "WFCORE POM contains duplicate version properties ..." > WFCORE POM contains duplicate version properties after component-matrix version revert > -------------------------------------------------------------------------------------- > > Key: WFCORE-3722 > URL: https://issues.jboss.org/browse/WFCORE-3722 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 5.0.0.Alpha7 > Reporter: David Lloyd > Assignee: Chao Wang > > {noformat} > $ grep "<version.org.wildfly.build-tools>" `find . -name pom.xml` > ./pom.xml: <version.org.wildfly.build-tools>1.2.10.Final</version.org.wildfly.build-tools> > ./pom.xml: <version.org.wildfly.build-tools>1.2.10.Final</version.org.wildfly.build-tools> > {noformat} > {noformat} > $ grep "<version.org.wildfly.checkstyle-config>" `find . -name pom.xml` > ./pom.xml: <version.org.wildfly.checkstyle-config>1.0.5.Final</version.org.wildfly.checkstyle-config> > ./pom.xml: <version.org.wildfly.checkstyle-config>1.0.5.Final</version.org.wildfly.checkstyle-config> > {noformat} > {noformat} > $ grep "<version.org.wildfly.plugin>" `find . -name pom.xml` > ./pom.xml: <version.org.wildfly.plugin>1.2.0.Final</version.org.wildfly.plugin> > ./pom.xml: <version.org.wildfly.plugin>1.2.0.Final</version.org.wildfly.plugin> > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 May 2018