May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1156) LocalUserClient should not fail if NameCallback is unsupported when default authentication name is set

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1156?page=com.atlassian.jira.plugin.s... ] Jan Kalina reassigned ELY-1156: ------------------------------- Assignee: Jan Kalina > LocalUserClient should not fail if NameCallback is unsupported when default authentication name is set > ------------------------------------------------------------------------------------------------------ > > Key: ELY-1156 > URL: https://issues.jboss.org/browse/ELY-1156 > Project: WildFly Elytron > Issue Type: Enhancement > Reporter: David Lloyd > Assignee: Jan Kalina > Priority: Minor > > The LocalUserClient mechanism should be tolerant of unsupported callbacks for name (and realm) when there are defaults available for the corresponding values. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-584) AuthenticationContext.empty() is a method but AuthenticationConfiguration.EMPTY is a field

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-584?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-584: -------------------------------- Grabbing for intern, Hana Kaspříková. > AuthenticationContext.empty() is a method but AuthenticationConfiguration.EMPTY is a field > ------------------------------------------------------------------------------------------ > > Key: ELY-584 > URL: https://issues.jboss.org/browse/ELY-584 > Project: WildFly Elytron > Issue Type: Task > Reporter: David Lloyd > Assignee: Jan Kalina > Priority: Trivial > > Make these consistent, probably just use methods. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-16) Manual Testcases - Create and Run

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-16?page=com.atlassian.jira.plu... ] Hayk Hovsepyan resolved HAWKULARQE-16. -------------------------------------- Resolution: Done > Manual Testcases - Create and Run > --------------------------------- > > Key: HAWKULARQE-16 > URL: https://issues.jboss.org/browse/HAWKULARQE-16 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Blocker > Labels: hawkular-qe-manual > > Middleware Manager running inside and outside of Openshift. > Manual test case runs were created: > For case when MM runs Outside OS > https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/testr... > For case when MM runs Inside OS > https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/testr... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-584) AuthenticationContext.empty() is a method but AuthenticationConfiguration.EMPTY is a field

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-584?page=com.atlassian.jira.plugin.sy... ] Jan Kalina reassigned ELY-584: ------------------------------ Assignee: Jan Kalina > AuthenticationContext.empty() is a method but AuthenticationConfiguration.EMPTY is a field > ------------------------------------------------------------------------------------------ > > Key: ELY-584 > URL: https://issues.jboss.org/browse/ELY-584 > Project: WildFly Elytron > Issue Type: Task > Reporter: David Lloyd > Assignee: Jan Kalina > Priority: Trivial > > Make these consistent, probably just use methods. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-17) Automation Testcase

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-17?page=com.atlassian.jira.plu... ] Hayk Hovsepyan commented on HAWKULARQE-17: ------------------------------------------ New automation test case created: cfme.tests.middleware.test_middleware_server.test_container_server_immutability > Automation Testcase > ------------------- > > Key: HAWKULARQE-17 > URL: https://issues.jboss.org/browse/HAWKULARQE-17 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Blocker > Labels: hawkular-qe-automation > > * Automate openshift eap7 docker container starting in preparation scripts > * In CFME CI > * Add openshift into CFME > * Verify discovery of EAP7, run smoke set of tests -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1185) Only the last mechanism selector is used in Elytron client configuration

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-1185?page=com.atlassian.jira.plugin.s... ] Ondrej Lukas updated ELY-1185: ------------------------------ Affects Version/s: 1.1.0.Beta42 > Only the last mechanism selector is used in Elytron client configuration > ------------------------------------------------------------------------ > > Key: ELY-1185 > URL: https://issues.jboss.org/browse/ELY-1185 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta42 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > > When Elytron client configuration file includes {{sasl-mechanism-selector}} with string which contains more mechanisms then only the last mentioned mechanism is used. In correct behavior it should use all given mechanisms in given order, see [1]. > In case when the last given mechanism is supported by server then it tries to authenticate, otherwise no mechanism is used to attempt to authenticate. > For example, following element for selector can be used in Elytron client configuration file: > {code} > <sasl-mechanism-selector selector="PLAIN DIGEST-MD5 ANONYMOUS JBOSS-LOCAL-USER"/> > {code} > When only {{DIGEST-MD5}} is supported by server then it works only if {{DIGEST-MD5}} is the last mechanism in selector string. > [1] https://issues.jboss.org/browse/EAP7-567?focusedCommentId=13408238&page=c... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-3) Manual Testcases - Create and Run

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-3?page=com.atlassian.jira.plug... ] Hayk Hovsepyan commented on HAWKULARQE-3: ----------------------------------------- Manual testcases executed in scopes of Polarion Runs: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/testr... https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/testr... > Manual Testcases - Create and Run > --------------------------------- > > Key: HAWKULARQE-3 > URL: https://issues.jboss.org/browse/HAWKULARQE-3 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Labels: hawkular-qe-manual > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1185) Only the last mechanism selector is used in Elytron client configuration

by Ondrej Lukas (JIRA)

Ondrej Lukas created ELY-1185: --------------------------------- Summary: Only the last mechanism selector is used in Elytron client configuration Key: ELY-1185 URL: https://issues.jboss.org/browse/ELY-1185 Project: WildFly Elytron Issue Type: Bug Reporter: Ondrej Lukas Assignee: Darran Lofthouse Priority: Critical When Elytron client configuration file includes {{sasl-mechanism-selector}} with string which contains more mechanisms then only the last mentioned mechanism is used. In correct behavior it should use all given mechanisms in given order, see [1]. In case when the last given mechanism is supported by server then it tries to authenticate, otherwise no mechanism is used to attempt to authenticate. For example, following element for selector can be used in Elytron client configuration file: {code} <sasl-mechanism-selector selector="PLAIN DIGEST-MD5 ANONYMOUS JBOSS-LOCAL-USER"/> {code} When only {{DIGEST-MD5}} is supported by server then it works only if {{DIGEST-MD5}} is the last mechanism in selector string. [1] https://issues.jboss.org/browse/EAP7-567?focusedCommentId=13408238&page=c... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1184) FAMILY and HASH selectors in Elytron client are parsed incorrectly

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-1184?page=com.atlassian.jira.plugin.s... ] Ondrej Lukas updated ELY-1184: ------------------------------ Affects Version/s: 1.1.0.Beta42 > FAMILY and HASH selectors in Elytron client are parsed incorrectly > ------------------------------------------------------------------ > > Key: ELY-1184 > URL: https://issues.jboss.org/browse/ELY-1184 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta42 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > > When #FAMILY or #HASH selector is used in Elytron client configuration file then it is parsed incorrectly - end bracket ')' is included in parsed family/hash name - it means it results to {{DIGEST)}} instead of {{DIGEST}}. It seems it is parsed incorrectly in {{parseSpecialWithName}} method of {{org.wildfly.security.sasl.SaslMechanismSelector}} class in [1]. > Following element for selector is used in Elytron client configuration file: > {code} > ... > <sasl-mechanism-selector selector="#FAMILY(DIGEST)"/> > ... > {code} > [1] https://github.com/wildfly-security/wildfly-elytron/blob/master/src/main/... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1184) FAMILY and HASH selectors in Elytron client are parsed incorrectly

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-1184?page=com.atlassian.jira.plugin.s... ] Ondrej Lukas updated ELY-1184: ------------------------------ Description: When #FAMILY or #HASH selector is used in Elytron client configuration file then it is parsed incorrectly - end bracket ')' is included in parsed family/hash name - it means it results to {{DIGEST)}} instead of {{DIGEST}}. It seems it is parsed incorrectly in {{parseSpecialWithName}} method of {{org.wildfly.security.sasl.SaslMechanismSelector}} class in [1]. Following element for selector is used in Elytron client configuration file: {code} ... <sasl-mechanism-selector selector="#FAMILY(DIGEST)"/> ... {code} [1] https://github.com/wildfly-security/wildfly-elytron/blob/master/src/main/... was: When #FAMILY or #HASH selector is used in Elytron client configuration file then it is parsed incorrectly - end bracket ')' is included in parsed family/hash name. It seems it is parsed incorrectly in {{parseSpecialWithName}} method of {{org.wildfly.security.sasl.SaslMechanismSelector}} class in [1]. [1] https://github.com/wildfly-security/wildfly-elytron/blob/master/src/main/... > FAMILY and HASH selectors in Elytron client are parsed incorrectly > ------------------------------------------------------------------ > > Key: ELY-1184 > URL: https://issues.jboss.org/browse/ELY-1184 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta42 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > > When #FAMILY or #HASH selector is used in Elytron client configuration file then it is parsed incorrectly - end bracket ')' is included in parsed family/hash name - it means it results to {{DIGEST)}} instead of {{DIGEST}}. It seems it is parsed incorrectly in {{parseSpecialWithName}} method of {{org.wildfly.security.sasl.SaslMechanismSelector}} class in [1]. > Following element for selector is used in Elytron client configuration file: > {code} > ... > <sasl-mechanism-selector selector="#FAMILY(DIGEST)"/> > ... > {code} > [1] https://github.com/wildfly-security/wildfly-elytron/blob/master/src/main/... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 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 May 2017