[JBoss JIRA] (WFLY-7436) Some attributes in Elytron ldap-realm are nillable=false but have set default values
by Ondrej Lukas (JIRA)
Ondrej Lukas created WFLY-7436:
----------------------------------
Summary: 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: Darran Lofthouse
Priority: Optional
Some attributes in Elytron ldap-realm are nillable=false but have set default values
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.2#72004)
7 years, 6 months
[JBoss JIRA] (WFLY-7436) Some attributes in Elytron ldap-realm are nillable=false but have set default values
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFLY-7436?page=com.atlassian.jira.plugin.... ]
Ondrej Lukas updated WFLY-7436:
-------------------------------
Labels: user_experience (was: )
> 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
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Optional
> Labels: user_experience
>
> Some attributes in Elytron ldap-realm are nillable=false but have set default values
> 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.2#72004)
7 years, 6 months
[JBoss JIRA] (WFLY-7436) Some attributes in Elytron ldap-realm are nillable=false but have set default values
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFLY-7436?page=com.atlassian.jira.plugin.... ]
Ondrej Lukas updated WFLY-7436:
-------------------------------
Affects 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
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Optional
> Labels: user_experience
>
> Some attributes in Elytron ldap-realm are nillable=false but have set default values
> 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.2#72004)
7 years, 6 months
[JBoss JIRA] (WFLY-7431) Convert stats-enabled metric into proper statistics-enabled attribute
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-7431?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-7431:
---------------------------------
Description:
{code}
/subsystem=jgroups/channel=ee:read-attribute(name=stats-enabled)
{code}
Other subsystems usually use attribute name {{statistics-enabled}}, we should deprecate the current attribute name and support the unified attribute name. This is the case in the transaction subsystem. This issue is similar to JBEAP-6501.
was:
{code}
/subsystem=jgroups/channel=ee:read-attribute(name=stats-enabled)
{code}
Other subsystems usually use attribute name {{statistics-enabled}}, we should deprecate the current attribute name and support the this unified attribute name. This is the case in the transaction subsystem. This issue is similar to JBEAP-6501.
> Convert stats-enabled metric into proper statistics-enabled attribute
> ---------------------------------------------------------------------
>
> Key: WFLY-7431
> URL: https://issues.jboss.org/browse/WFLY-7431
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.1.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Minor
>
> {code}
> /subsystem=jgroups/channel=ee:read-attribute(name=stats-enabled)
> {code}
> Other subsystems usually use attribute name {{statistics-enabled}}, we should deprecate the current attribute name and support the unified attribute name. This is the case in the transaction subsystem. This issue is similar to JBEAP-6501.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
7 years, 6 months