November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7586) Wrong options for auto-completion in realms of Elytron security-domain in CLI

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFLY-7586: ---------------------------------- Summary: Wrong options for auto-completion in realms of Elytron security-domain in CLI Key: WFLY-7586 URL: https://issues.jboss.org/browse/WFLY-7586 Project: WildFly Issue Type: Bug Components: Security Reporter: Ondrej Lukas Assignee: Darran Lofthouse Auto-completion for realm in realms of security-domain provides wrong options. In case when ldap-realm with name ldapName is defined in configuration then also option {{rity-realm.ldapName}} occurs in auto-completion options. I am not able to reproduce this issue with properties-realm. Take a look at Steps to Reproduce for more details. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7585) Auto-completion does not work for default-realm of Elytron security-domain in CLI

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7585?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-7585: ------------------------------- Labels: user_experience (was: ) > Auto-completion does not work for default-realm of Elytron security-domain in CLI > --------------------------------------------------------------------------------- > > Key: WFLY-7585 > URL: https://issues.jboss.org/browse/WFLY-7585 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Labels: user_experience > > Auto-completion does not work for default-realm of Elytron security-domain in CLI. All attributes of security-domain support auto-completion through {{<TAB>}} button. The only one which does not support it is default-realm. It is probably caused by missing capability-reference. > Example: > {code} > /subsystem=elytron/security-domain=domain:add(default-realm=<TAB> > {code} > Does not show any security realms. However: > {code} > /subsystem=elytron/security-domain=domain:add(permission-mapper=<TAB> > {code} > Shows possible permission mappers. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7585) Auto-completion does not work for default-realm of Elytron security-domain in CLI

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFLY-7585: ---------------------------------- Summary: Auto-completion does not work for default-realm of Elytron security-domain in CLI Key: WFLY-7585 URL: https://issues.jboss.org/browse/WFLY-7585 Project: WildFly Issue Type: Bug Components: Security Reporter: Ondrej Lukas Assignee: Darran Lofthouse Auto-completion does not work for default-realm of Elytron security-domain in CLI. All attributes of security-domain support auto-completion through {{<TAB>}} button. The only one which does not support it is default-realm. It is probably caused by missing capability-reference. Example: {code} /subsystem=elytron/security-domain=domain:add(default-realm=<TAB> {code} Does not show any security realms. However: {code} /subsystem=elytron/security-domain=domain:add(permission-mapper=<TAB> {code} Shows possible permission mappers. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7585) Auto-completion does not work for default-realm of Elytron security-domain in CLI

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7585?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-7585: ------------------------------- Affects Version/s: 11.0.0.Alpha1 > Auto-completion does not work for default-realm of Elytron security-domain in CLI > --------------------------------------------------------------------------------- > > Key: WFLY-7585 > URL: https://issues.jboss.org/browse/WFLY-7585 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Labels: user_experience > > Auto-completion does not work for default-realm of Elytron security-domain in CLI. All attributes of security-domain support auto-completion through {{<TAB>}} button. The only one which does not support it is default-realm. It is probably caused by missing capability-reference. > Example: > {code} > /subsystem=elytron/security-domain=domain:add(default-realm=<TAB> > {code} > Does not show any security realms. However: > {code} > /subsystem=elytron/security-domain=domain:add(permission-mapper=<TAB> > {code} > Shows possible permission mappers. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7584) User should be able to specify only one password type for Elytron filesystem-realm identity

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFLY-7584: ---------------------------------- Summary: User should be able to specify only one password type for Elytron filesystem-realm identity Key: WFLY-7584 URL: https://issues.jboss.org/browse/WFLY-7584 Project: WildFly Issue Type: Bug Components: Security Reporter: Ondrej Lukas Assignee: Darran Lofthouse It is possible to specify more types of password encryption/hash mechanism in {{set-password}} operation of filesystem-realm identity. When this happens then first password encryption/hash mechanism is correctly used, but the rest of them is discarded. However it make sense to have set only one password encryption/hash mechanism for identity. It can be confusing to allow CLI command with more types of password encryption/hash mechanism specified. Suggestion for improvement: Disallow to use set-password operation with more than one password encryption/hash mechanism. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7584) User should be able to specify only one password type for Elytron filesystem-realm identity

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7584?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-7584: ------------------------------- Affects Version/s: 11.0.0.Alpha1 > User should be able to specify only one password type for Elytron filesystem-realm identity > ------------------------------------------------------------------------------------------- > > Key: WFLY-7584 > URL: https://issues.jboss.org/browse/WFLY-7584 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Labels: user_experience > > It is possible to specify more types of password encryption/hash mechanism in {{set-password}} operation of filesystem-realm identity. When this happens then first password encryption/hash mechanism is correctly used, but the rest of them is discarded. However it make sense to have set only one password encryption/hash mechanism for identity. It can be confusing to allow CLI command with more types of password encryption/hash mechanism specified. > Suggestion for improvement: > Disallow to use set-password operation with more than one password encryption/hash mechanism. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7584) User should be able to specify only one password type for Elytron filesystem-realm identity

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7584?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-7584: ------------------------------- Labels: user_experience (was: ) > User should be able to specify only one password type for Elytron filesystem-realm identity > ------------------------------------------------------------------------------------------- > > Key: WFLY-7584 > URL: https://issues.jboss.org/browse/WFLY-7584 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Labels: user_experience > > It is possible to specify more types of password encryption/hash mechanism in {{set-password}} operation of filesystem-realm identity. When this happens then first password encryption/hash mechanism is correctly used, but the rest of them is discarded. However it make sense to have set only one password encryption/hash mechanism for identity. It can be confusing to allow CLI command with more types of password encryption/hash mechanism specified. > Suggestion for improvement: > Disallow to use set-password operation with more than one password encryption/hash mechanism. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7583) Salted password cannot be set through CLI for Elytron filesystem-realm identity

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7583?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-7583: ------------------------------- Affects Version/s: 11.0.0.Alpha1 > Salted password cannot be set through CLI for Elytron filesystem-realm identity > ------------------------------------------------------------------------------- > > Key: WFLY-7583 > URL: https://issues.jboss.org/browse/WFLY-7583 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > > Password encryption/hash mechanisms which contain {{salt}} attribute for filesystem-realm identity cannot be added through CLI. {{set-password}} operation fails and finishes with failure-description "WFLYCTL0155: password may not be null" even if password was set. It seems when {{salt}} attribute with {{bytes}} value is used then {{password}} attribute is ignored by CLI. > Following password encryption/hash mechanisms from filesystem-realm identity are affected by issue: > - {{bcrypt}} > - {{salted-simple-digest}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7583) Salted password cannot be set through CLI for Elytron filesystem-realm identity

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFLY-7583: ---------------------------------- Summary: Salted password cannot be set through CLI for Elytron filesystem-realm identity Key: WFLY-7583 URL: https://issues.jboss.org/browse/WFLY-7583 Project: WildFly Issue Type: Bug Components: Security Reporter: Ondrej Lukas Assignee: Darran Lofthouse Password encryption/hash mechanisms which contain {{salt}} attribute for filesystem-realm identity cannot be added through CLI. {{set-password}} operation fails and finishes with failure-description "WFLYCTL0155: password may not be null" even if password was set. It seems when {{salt}} attribute with {{bytes}} value is used then {{password}} attribute is ignored by CLI. Following password encryption/hash mechanisms from filesystem-realm identity are affected by issue: - {{bcrypt}} - {{salted-simple-digest}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7582) Wrong resource and operation descriptions for Elytron filesystem-realm in CLI and XSD

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7582?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-7582: ------------------------------- Labels: user_experience (was: ) > Wrong resource and operation descriptions for Elytron filesystem-realm in CLI and XSD > ------------------------------------------------------------------------------------- > > Key: WFLY-7582 > URL: https://issues.jboss.org/browse/WFLY-7582 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Labels: user_experience > > There are some wrong or insufficient resource and operation description for Elytron filesystem-realm in CLI: > * attribute {{levels}} for filesystem-realm - description says "The number of levels of directory hashing to apply.", but created directory structure does not use any hashing. Example how it works: when levels is set to 3 then for user admin following directory structure and file a/d/m/admin.xml is used. Description of levels should be fixed. This should be also fixed in XSD. > * description of {{digest}} password encryption/hash mechanisms in {{set-password}} operation for identity of filesystem-realm says "A password using a salted digest." which is wrong. It seems it is copy-pasted from {{salted-simple-digest}}. -- 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