May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4395) The single mapper validation added via WFCORE-2364 happens at Runtime, this should be a Model time check.

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4395?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-4395: ------------------------------------- Fix Version/s: (was: 9.0.0.Beta8) > The single mapper validation added via WFCORE-2364 happens at Runtime, this should be a Model time check. > --------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4395 > URL: https://issues.jboss.org/browse/WFCORE-4395 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Priority: Major > > If possible the mappers should be flagged as being mutually exclusive, however failing that the validation should happen during Stage.MODEL. > Presently this leads to an unsatisifed dependency: - > {noformat} > 14:21:59,055 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("security-domain" => "demon-domain") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.security-realm.demo-realm"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.security-domain.demon-domain.initial is missing [org.wildfly.security.security-realm.demo-realm]"] > } > {noformat} > Despite this error the underlying cause is not logged at any level. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10803) WildFly Single Sign On Documentation

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-10803?page=com.atlassian.jira.plugin... ] Darran Lofthouse reassigned WFLY-10803: --------------------------------------- Assignee: (was: Darran Lofthouse) > WildFly Single Sign On Documentation > ------------------------------------ > > Key: WFLY-10803 > URL: https://issues.jboss.org/browse/WFLY-10803 > Project: WildFly > Issue Type: Task > Components: Documentation, Security > Environment: * > Reporter: Darran Lofthouse > Priority: Major > > Presently there are a lot of options for single sign on that can be used with the application server, it could be useful to pull all of these into a single document. > * WildFly Clustering SSO > * Kerberos > * SAML > * KeyCloak > * OpenID Connect > For anyone tasked with implementing "SSO" this should give enough information to select between the available options. > From that point we should document how to implement each of these options possibly with further sub options identified. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10803) WildFly Single Sign On Documentation

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-10803?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFLY-10803: ------------------------------------ Fix Version/s: (was: 17.0.0.Final) > WildFly Single Sign On Documentation > ------------------------------------ > > Key: WFLY-10803 > URL: https://issues.jboss.org/browse/WFLY-10803 > Project: WildFly > Issue Type: Task > Components: Documentation, Security > Environment: * > Reporter: Darran Lofthouse > Priority: Major > > Presently there are a lot of options for single sign on that can be used with the application server, it could be useful to pull all of these into a single document. > * WildFly Clustering SSO > * Kerberos > * SAML > * KeyCloak > * OpenID Connect > For anyone tasked with implementing "SSO" this should give enough information to select between the available options. > From that point we should document how to implement each of these options possibly with further sub options identified. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

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

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-3983?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-3983: ------------------------------------- Fix Version/s: (was: 9.0.0.Beta8) > 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 > > 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, 1 month

1
0
0 / 0

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

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-2496?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2496: ------------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 9.0.0.Beta8) > 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: 10.0.0.Beta1 > > > 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 month

1
0
0 / 0

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

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4150?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-4150: ------------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 9.0.0.Beta8) > 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: 10.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4261) Update Maven dependencies to reference individual Elytron modules.

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4261?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-4261: ---------------------------------------- Assignee: (was: Darran Lofthouse) > Update Maven dependencies to reference individual Elytron modules. > ------------------------------------------------------------------ > > Key: WFCORE-4261 > URL: https://issues.jboss.org/browse/WFCORE-4261 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Priority: Major > > Additionally remove the root 'wildfly-elytron' dependency. > This should also review the classes the application server users as we will likely want to start considering these public API. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4261) Update Maven dependencies to reference individual Elytron modules.

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4261?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-4261: ------------------------------------- Fix Version/s: (was: 9.0.0.Beta8) > Update Maven dependencies to reference individual Elytron modules. > ------------------------------------------------------------------ > > Key: WFCORE-4261 > URL: https://issues.jboss.org/browse/WFCORE-4261 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Priority: Major > > Additionally remove the root 'wildfly-elytron' dependency. > This should also review the classes the application server users as we will likely want to start considering these public API. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4501) Provide XML schema for credential-reference

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4501?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved WFLY-10052 to WFCORE-4501: ------------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4501 (was: WFLY-10052) Component/s: Management Security (was: JCA) (was: JMS) (was: Mail) (was: Management) (was: Security) Target Release: (was: 7.2.0.GA) > Provide XML schema for credential-reference > ------------------------------------------- > > Key: WFCORE-4501 > URL: https://issues.jboss.org/browse/WFCORE-4501 > Project: WildFly Core > Issue Type: Enhancement > Components: Management, Security > Reporter: Jeff Mesnil > Priority: Major > Labels: credential-reference, eap72 > Fix For: 10.0.0.Beta1 > > > With https://issues.jboss.org/browse/EAP7-538, all passwords references in the subsystems must support credential references. > The model attribute is provided by wildlfy-controller module (including its XML parser and marshaller) but the corresponding XML element has been added directly to the subsystems XML schemas. This will become a maintenance issue when/if the credential references has to be updated and all the subsystems schema risk to be out of sync with the actual code reading/writing the credential reference. > We should follow the same design than for threads attributes (provided by the willdfly-threads module): the wildlfy-controller module provides a XML schema for the credential-references with its own versioned namespace and any subsystem that requires it will just refer to it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4501) Provide XML schema for credential-reference

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4501?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-4501: ------------------------------------- Fix Version/s: 10.0.0.Beta1 > Provide XML schema for credential-reference > ------------------------------------------- > > Key: WFCORE-4501 > URL: https://issues.jboss.org/browse/WFCORE-4501 > Project: WildFly Core > Issue Type: Enhancement > Components: Management, Security > Reporter: Jeff Mesnil > Priority: Major > Labels: credential-reference, eap72 > Fix For: 10.0.0.Beta1 > > > With https://issues.jboss.org/browse/EAP7-538, all passwords references in the subsystems must support credential references. > The model attribute is provided by wildlfy-controller module (including its XML parser and marshaller) but the corresponding XML element has been added directly to the subsystems XML schemas. This will become a maintenance issue when/if the credential references has to be updated and all the subsystems schema risk to be out of sync with the actual code reading/writing the credential reference. > We should follow the same design than for threads attributes (provided by the willdfly-threads module): the wildlfy-controller module provides a XML schema for the credential-references with its own versioned namespace and any subsystem that requires it will just refer to it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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 2019