November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1943) Remove the 'urn:jboss:domain:remoting:5.0' schame and corresponding model versions.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1943?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-1943: ------------------------------------- Labels: affects_elytron (was: ) > Remove the 'urn:jboss:domain:remoting:5.0' schame and corresponding model versions. > ----------------------------------------------------------------------------------- > > Key: WFCORE-1943 > URL: https://issues.jboss.org/browse/WFCORE-1943 > Project: WildFly Core > Issue Type: Bug > Components: Remoting > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Labels: affects_elytron > Fix For: 3.0.0.Alpha12 > > > When working on the management models we first need to check the last final release so that we can identify if we do need to increment the versions or not. > I had already added a clean version 4 ready for ongoing development. > Also on a related point it would be better if we can add the new version in one commit and then make changes in a subsequent commit - this way we can use various git tools to see the changes made otherwise the first set of changes are never visible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1943) Remove the 'urn:jboss:domain:remoting:5.0' schame and corresponding model versions.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-1943: ---------------------------------------- Summary: Remove the 'urn:jboss:domain:remoting:5.0' schame and corresponding model versions. Key: WFCORE-1943 URL: https://issues.jboss.org/browse/WFCORE-1943 Project: WildFly Core Issue Type: Bug Components: Remoting Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Blocker Fix For: 3.0.0.Alpha12 When working on the management models we first need to check the last final release so that we can identify if we do need to increment the versions or not. I had already added a clean version 4 ready for ongoing development. Also on a related point it would be better if we can add the new version in one commit and then make changes in a subsequent commit - this way we can use various git tools to see the changes made otherwise the first set of changes are never visible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1942) Remove the $local use from the default mgmt-users.properties

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-1942: ---------------------------------------- Summary: Remove the $local use from the default mgmt-users.properties Key: WFCORE-1942 URL: https://issues.jboss.org/browse/WFCORE-1942 Project: WildFly Core Issue Type: Enhancement Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Critical Fix For: 3.0.0.Alpha12 The subsystem will be enhanced so that an identity-security-realm can be defined with some hard coded identities, once defined we can remove the $local user from the properties file(s) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7436) Some attributes in Elytron ldap-realm are nillable=false but have set default values

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7436?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7436: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > Some attributes in Elytron ldap-realm are nillable=false but have set default values > ------------------------------------------------------------------------------------ > > Key: WFLY-7436 > URL: https://issues.jboss.org/browse/WFLY-7436 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > Labels: user_experience > Fix For: 11.0.0.Alpha1 > > > Following attributes Elytron ldap-realm are nillable=false but have set default values: > * {{identity-mapping.use-recursive-search}} > * {{identity-mapping.user-password-mapper.writable}} > * {{identity-mapping.user-password-mapper.verifiable}} > Using nillable=false with set default value can be confused (because default value should be used in case when none value is set and nillable=false says that any value must by used). > Suggestion: > Since none of these mentioned attributes is required by CLI commands set nillable for these attributes to true. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7436) Some attributes in Elytron ldap-realm are nillable=false but have set default values

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7436?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7436: ----------------------------------- Priority: Major (was: Optional) > Some attributes in Elytron ldap-realm are nillable=false but have set default values > ------------------------------------------------------------------------------------ > > Key: WFLY-7436 > URL: https://issues.jboss.org/browse/WFLY-7436 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > Labels: user_experience > Fix For: 11.0.0.Alpha1 > > > Following attributes Elytron ldap-realm are nillable=false but have set default values: > * {{identity-mapping.use-recursive-search}} > * {{identity-mapping.user-password-mapper.writable}} > * {{identity-mapping.user-password-mapper.verifiable}} > Using nillable=false with set default value can be confused (because default value should be used in case when none value is set and nillable=false says that any value must by used). > Suggestion: > Since none of these mentioned attributes is required by CLI commands set nillable for these attributes to true. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7436) Some attributes in Elytron ldap-realm are nillable=false but have set default values

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7436?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7436: ----------------------------------- Affects Version/s: (was: 11.0.0.Alpha1) > Some attributes in Elytron ldap-realm are nillable=false but have set default values > ------------------------------------------------------------------------------------ > > Key: WFLY-7436 > URL: https://issues.jboss.org/browse/WFLY-7436 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > Labels: user_experience > Fix For: 11.0.0.Alpha1 > > > Following attributes Elytron ldap-realm are nillable=false but have set default values: > * {{identity-mapping.use-recursive-search}} > * {{identity-mapping.user-password-mapper.writable}} > * {{identity-mapping.user-password-mapper.verifiable}} > Using nillable=false with set default value can be confused (because default value should be used in case when none value is set and nillable=false says that any value must by used). > Suggestion: > Since none of these mentioned attributes is required by CLI commands set nillable for these attributes to true. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7286) Elytron - inconsistency between DMR and XSD representation of mechanism-provider-filtering-sasl-server-factory

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7286?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7286: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > Elytron - inconsistency between DMR and XSD representation of mechanism-provider-filtering-sasl-server-factory > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7286 > URL: https://issues.jboss.org/browse/WFLY-7286 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > Labels: user_experience > Fix For: 11.0.0.Alpha1 > > > There is an inconsistency between DMR and XSD representation of {{mechanism-provider-filtering-sasl-server-factory}}. > According to XSD [1] {{filters}} may not occur in {{mechanism-provider-filtering-sasl-server-factory}}. According to DMR {{filters}} is {{"nillable" => false}}. This should be unified. > [1] https://github.com/wildfly-security/elytron-subsystem/blob/82a3cfb2c1c7c8... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7286) Elytron - inconsistency between DMR and XSD representation of mechanism-provider-filtering-sasl-server-factory

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7286?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7286: ----------------------------------- Priority: Major (was: Optional) > Elytron - inconsistency between DMR and XSD representation of mechanism-provider-filtering-sasl-server-factory > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7286 > URL: https://issues.jboss.org/browse/WFLY-7286 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > Labels: user_experience > Fix For: 11.0.0.Alpha1 > > > There is an inconsistency between DMR and XSD representation of {{mechanism-provider-filtering-sasl-server-factory}}. > According to XSD [1] {{filters}} may not occur in {{mechanism-provider-filtering-sasl-server-factory}}. According to DMR {{filters}} is {{"nillable" => false}}. This should be unified. > [1] https://github.com/wildfly-security/elytron-subsystem/blob/82a3cfb2c1c7c8... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7286) Elytron - inconsistency between DMR and XSD representation of mechanism-provider-filtering-sasl-server-factory

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7286?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7286: ----------------------------------- Affects Version/s: (was: 11.0.0.Alpha1) > Elytron - inconsistency between DMR and XSD representation of mechanism-provider-filtering-sasl-server-factory > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7286 > URL: https://issues.jboss.org/browse/WFLY-7286 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > Labels: user_experience > Fix For: 11.0.0.Alpha1 > > > There is an inconsistency between DMR and XSD representation of {{mechanism-provider-filtering-sasl-server-factory}}. > According to XSD [1] {{filters}} may not occur in {{mechanism-provider-filtering-sasl-server-factory}}. According to DMR {{filters}} is {{"nillable" => false}}. This should be unified. > [1] https://github.com/wildfly-security/elytron-subsystem/blob/82a3cfb2c1c7c8... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7288) Elytron - inconsistency between DMR and XSD representation of ldap-realm

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7288?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7288: ----------------------------------- Affects Version/s: (was: 11.0.0.Alpha1) > Elytron - inconsistency between DMR and XSD representation of ldap-realm > ------------------------------------------------------------------------ > > Key: WFLY-7288 > URL: https://issues.jboss.org/browse/WFLY-7288 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > Priority: Optional > Labels: user_experience > Fix For: 11.0.0.Alpha1 > > > There are inconsistencies between DMR and XSD representation of ldap-realm. > * According to XSD [1] {{from}} attribute from user-password-mapper is required in ldap-realm. According to DMR {{from}} attribute is {{"nillable" => true}}. > * According to XSD [2] every attribute ({{algorithm-from}}, {{hash-from}}, {{seed-from}}, {{sequence-from}}) from otp-credential-mapper is required in ldap-realm. According to DMR all these attributes are {{"nillable" => true}}. > * According to XSD [3] {{name}} of {{attribute}} from new-identity-attributes is required in ldap-realm. According to DMR {{name}} of {{attribute}} is {{"nillable" => true}}. > These inconsistencies should be unified. > [1] https://github.com/wildfly-security/elytron-subsystem/blob/82a3cfb2c1c7c8... > [2] https://github.com/wildfly-security/elytron-subsystem/blob/82a3cfb2c1c7c8... > [3] https://github.com/wildfly-security/elytron-subsystem/blob/82a3cfb2c1c7c8... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 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 November 2016