November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7685) Elytron mapped-regex-realm-mapper "name" attribute has wrong description.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFLY-7685?page=com.atlassian.jira.plugin.... ] Hynek Švábek reassigned WFLY-7685: ---------------------------------- Assignee: Dmitrii Tikhomirov (was: Jason Greene) > Elytron mapped-regex-realm-mapper "name" attribute has wrong description. > ------------------------------------------------------------------------- > > Key: WFLY-7685 > URL: https://issues.jboss.org/browse/WFLY-7685 > Project: WildFly > Issue Type: Bug > Reporter: Hynek Švábek > Assignee: Dmitrii Tikhomirov > > Elytron mapped-regex-realm-mapper "name" attribute has wrong description. > {code} > https://github.com/wildfly-security/elytron-subsystem/blob/580569d17cb6c3... > {code} > *Actual description* > {code} > The unique name for the RealmMapper, note names used for NameRewriters must be unique > across the whole context. > {code} > *Expected description* > {code} > The unique name for the RealmMapper, note names used for RealmMappers must be unique > across the whole context. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7685) Elytron mapped-regex-realm-mapper "name" attribute has wrong description.

by Hynek Švábek (JIRA)

Hynek Švábek created WFLY-7685: ---------------------------------- Summary: Elytron mapped-regex-realm-mapper "name" attribute has wrong description. Key: WFLY-7685 URL: https://issues.jboss.org/browse/WFLY-7685 Project: WildFly Issue Type: Bug Reporter: Hynek Švábek Assignee: Jason Greene Elytron mapped-regex-realm-mapper "name" attribute has wrong description. {code} https://github.com/wildfly-security/elytron-subsystem/blob/580569d17cb6c3... {code} *Actual description* {code} The unique name for the RealmMapper, note names used for NameRewriters must be unique across the whole context. {code} *Expected description* {code} The unique name for the RealmMapper, note names used for RealmMappers must be unique across the whole context. {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7501) Security domain can have itself in "trusted-security-domains"

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7501?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7501: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > Security domain can have itself in "trusted-security-domains" > ------------------------------------------------------------- > > Key: WFLY-7501 > URL: https://issues.jboss.org/browse/WFLY-7501 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Jan Kalina > Fix For: 11.0.0.Alpha1 > > > Security-domain trusted-security-domains attribute has confusing behaviour. I can define there security domain which doesn't exist yet (It is being created right now). > *Steps to reproduce* > {code} > /subsystem=elytron/filesystem-realm=realm1:add(relative-to=jboss.server.config.dir, path=tmp.prop) > {code} > {code} > /subsystem=elytron/security-domain=secDomain888:add(realms=[{realm=realm1}], default-realm=realm1, trusted-security-domains=[secDomain888]) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-793) Using @STRENGTH keyword in CipherSuiteSelector.fromString should cause descending sorting

by Ondrej Kotek (JIRA)

[ https://issues.jboss.org/browse/ELY-793?page=com.atlassian.jira.plugin.sy... ] Ondrej Kotek commented on ELY-793: ---------------------------------- Tests: https://github.com/wildfly-security/wildfly-elytron/pull/581/files#diff-a... > Using @STRENGTH keyword in CipherSuiteSelector.fromString should cause descending sorting > ----------------------------------------------------------------------------------------- > > Key: ELY-793 > URL: https://issues.jboss.org/browse/ELY-793 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.1.0.Beta14 > Reporter: Ondrej Kotek > Assignee: Darran Lofthouse > > Using {{@STRENGTH}} keyword in {{CipherSuiteSelector.fromString}} should cause descending sorting of cipher suites, like OpenSSL does, e.g. {{openssl ciphers -v 'ALL:!ADH:@STRENGTH'}}. There is comparator in {{SortByAlgorithmKeyLengthCipherSuiteSelector}} [1]. > Or, am I wrong? Are cipher suites in {{javax.net.ssl.SSLParameters}} expected in ascending order? (Does it matter?) Will the OpenSSL provider expect ascending order? (Or will it parse cipher string itself?) > The JavaDoc [2] should mention whether the sorting is ascending or descending. > [1] https://github.com/wildfly-security/wildfly-elytron/blob/7666231fa76b95c3... > [2] https://github.com/wildfly-security/wildfly-elytron/blob/7666231fa76b95c3... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2049) Redirection (<, <<) do not work in CLI

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-2049: -------------------------------------------- Summary: Redirection (<, <<) do not work in CLI Key: WFCORE-2049 URL: https://issues.jboss.org/browse/WFCORE-2049 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise Priority: Blocker -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7589) Wrong description for injecting the same realm to Elytron security-domain in CLI

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7589?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7589: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > Wrong description for injecting the same realm to Elytron security-domain in CLI > -------------------------------------------------------------------------------- > > Key: WFLY-7589 > URL: https://issues.jboss.org/browse/WFLY-7589 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > Labels: user_experience > Fix For: 11.0.0.Alpha1 > > > Adding the same realms to one Elytron security-domain is denied in CLI. However failure-description is wrong. See: > {code} > /subsystem=elytron/security-domain=securityDomain:add(realms=[{realm=ApplicationRealm},{realm=ApplicationRealm}],default-realm=ApplicationRealm) > { > "outcome" => "failed", > "failure-description" => "WFLYELY00002: Can not inject the same realm 'securityDomain' in a single security domain 'ApplicationRealm'.", > "rolled-back" => true > } > {code} > It should says: "WFLYELY00002: Can not inject the same realm 'ApplicationRealm' in a single security domain 'securityDomain'.". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7589) Wrong description for injecting the same realm to Elytron security-domain in CLI

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7589?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7589: ----------------------------------- Affects Version/s: (was: 11.0.0.Alpha1) > Wrong description for injecting the same realm to Elytron security-domain in CLI > -------------------------------------------------------------------------------- > > Key: WFLY-7589 > URL: https://issues.jboss.org/browse/WFLY-7589 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > Labels: user_experience > Fix For: 11.0.0.Alpha1 > > > Adding the same realms to one Elytron security-domain is denied in CLI. However failure-description is wrong. See: > {code} > /subsystem=elytron/security-domain=securityDomain:add(realms=[{realm=ApplicationRealm},{realm=ApplicationRealm}],default-realm=ApplicationRealm) > { > "outcome" => "failed", > "failure-description" => "WFLYELY00002: Can not inject the same realm 'securityDomain' in a single security domain 'ApplicationRealm'.", > "rolled-back" => true > } > {code} > It should says: "WFLYELY00002: Can not inject the same realm 'ApplicationRealm' in a single security domain 'securityDomain'.". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7619) Is impossible remove whole Elytron subsystem when Elytron resource depends on another Elytron resource.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7619?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7619: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > Is impossible remove whole Elytron subsystem when Elytron resource depends on another Elytron resource. > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-7619 > URL: https://issues.jboss.org/browse/WFLY-7619 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Jan Kalina > Fix For: 11.0.0.Alpha1 > > > Is impossible remove whole Elytron subsystem by one command when Elytron resource depends on another Elytron resource. > *Scenario:* > * I have KeyStore in Elytron subsystem with CredentialStoreReference set to CredentialStore > * I want to delete whole Elytron subsystem > * I execute this CLI command */subsystem=elytron:remove()* and get error > {code} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies: > Service org.wildfly.security.credential-store-client.credStore was depended upon by service org.wildfly.security.key-store.firefly", > "rolled-back" => true > } > {code} > *NOTES:* > * When I perform CLI command */subsystem=elytron:remove()* again as it passes. > * When I use for remove {allow-resource-service-restart=true} as /subsystem=elytron:remove(){allow-resource-service-restart=true} then result is successful. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7681) Unify descriptions of mechanism-provider-filtering-sasl-server-factory of XSD and DMR

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFLY-7681?page=com.atlassian.jira.plugin.... ] Ilia Vassilev reassigned WFLY-7681: ----------------------------------- Assignee: Ilia Vassilev > Unify descriptions of mechanism-provider-filtering-sasl-server-factory of XSD and DMR > ------------------------------------------------------------------------------------- > > Key: WFLY-7681 > URL: https://issues.jboss.org/browse/WFLY-7681 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Ilia Vassilev > Labels: user_experience > > Descriptions of resource and attributes of {{mechanism-provider-filtering-sasl-server-factory}} are mostly different in XSD and DMR. > I suggest to use XSD documentation, which seems to me better. More understandable, better style. > Also note there is typo in {{provider-version}} XSD description agasint -> against . -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7175) Complex type server-ssl-context/ssl-session in Elytron subsystem

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7175?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7175: ----------------------------------- Affects Version/s: (was: 11.0.0.Alpha1) > Complex type server-ssl-context/ssl-session in Elytron subsystem > ---------------------------------------------------------------- > > Key: WFLY-7175 > URL: https://issues.jboss.org/browse/WFLY-7175 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > Elytron subsystem uses complex type in server-ssl-context resource which is difficult to use and can result to bad user experience, see description of JBEAP-6100 for more details. > Details: *server-ssl-context/ssl-session* - nested complex attributes (not critical in the short term - although exposing management information that provides insight into the current sessions would be a big bonus for administrators) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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