February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4853) [GSS][7.2.2] HTTP External Security Not Supported by Elytron

by Ashley Abdel-Sayed (Jira)

Ashley Abdel-Sayed created WFCORE-4853: ------------------------------------------ Summary: [GSS][7.2.2] HTTP External Security Not Supported by Elytron Key: WFCORE-4853 URL: https://issues.redhat.com/browse/WFCORE-4853 Project: WildFly Core Issue Type: Feature Request Components: Security Reporter: Ashley Abdel-Sayed Assignee: Ashley Abdel-Sayed Add EXTERNAL HTTP authentication mechanism to WildFly -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1938) [GSS][7.2.2] HTTP External Security Not Supported by Elytron

by Ashley Abdel-Sayed (Jira)

[ https://issues.redhat.com/browse/ELY-1938?page=com.atlassian.jira.plugin.... ] Ashley Abdel-Sayed deleted ELY-1938: ------------------------------------ > [GSS][7.2.2] HTTP External Security Not Supported by Elytron > ------------------------------------------------------------ > > Key: ELY-1938 > URL: https://issues.redhat.com/browse/ELY-1938 > Project: WildFly Elytron > Issue Type: Feature Request > Reporter: Ashley Abdel-Sayed > Assignee: Ashley Abdel-Sayed > Priority: Major > > For legacy security, there's an EXTERNAL HTTP authentication mechanism (io.undertow.security.impl.ExternalAuthenticationMechanism) which performs no verification and simply uses the principal that was passed from the REMOTE_USER attribute by the AJP protocol. There is a "ClientLoginModule" in legacy security used as such: https://access.redhat.com/solutions/3465231. It is a requirement to add an equivalent of this EXTERNAL mechanism available in legacy and Elytron-SASL for Elytron-HTTP in order to migrate away from legacy security. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1938) [GSS][7.2.2] HTTP External Security Not Supported by Elytron

by Ashley Abdel-Sayed (Jira)

Ashley Abdel-Sayed created ELY-1938: --------------------------------------- Summary: [GSS][7.2.2] HTTP External Security Not Supported by Elytron Key: ELY-1938 URL: https://issues.redhat.com/browse/ELY-1938 Project: WildFly Elytron Issue Type: Feature Request Affects Versions: 1.11.0.Final Reporter: Ashley Abdel-Sayed Assignee: Ashley Abdel-Sayed For legacy security, there's an EXTERNAL HTTP authentication mechanism (io.undertow.security.impl.ExternalAuthenticationMechanism) which performs no verification and simply uses the principal that was passed from the REMOTE_USER attribute by the AJP protocol. There is a "ClientLoginModule" in legacy security used as such: https://access.redhat.com/solutions/3465231. It is a requirement to add an equivalent of this EXTERNAL mechanism available in legacy and Elytron-SASL for Elytron-HTTP in order to migrate away from legacy security. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5046) [DMN Designer] Marshalling questions

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5046?page=com.atlassian.jira.plug... ] Toni Rikkola commented on DROOLS-5046: -------------------------------------- [~manstis] Sounds and looks good. > [DMN Designer] Marshalling questions > ------------------------------------ > > Key: DROOLS-5046 > URL: https://issues.redhat.com/browse/DROOLS-5046 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.33.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Our marshaller is EXPLICITLY setting Definitions.typeLanguage to FEEL. Is this acceptable? > DMN1.2 Specification "6.3.2 Definitions metamodel" states : > An instance of Definitions MAY specify a typeLanguage, which is a URI that identifies the default type language used in elements within the scope of this Definitions ... If unspecified, the default typeLanguage is FEEL. > So it is not wrong, but it is not necessary. > --------------------------------------------------------------------------------- > Our marshaller is EXPLICITLY setting ItemDefinition.id > DMN1.2 Specification "7.3.2 - ItemDefinition metamodel" states : > ...an instance of ItemDefinition HAS a name and an OPTIONAL id > So it is not wrong, but it is not necessary. > --------------------------------------------------------------------------------- > Our marshaller IS NOT setting ContextEntry.id > DMN1.2 Specification 10.5.2 - ContextEntry metamodel states : > ...ContextEntry is a specialization of DMNElement, from which it INHERITS the OPTIONAL id... > It is therefore correct for us to exclude the id (but _other tools_ includes it. Is that wrong?!) > --------------------------------------------------------------------------------- > Our marshaller is EXPLICITLY setting DecisionTable.preferredOrientation (to Rule-as-Row) > DMN1.2 Specification 8.3.1 - Decision Table metamodel states : > ...It has a preferredOrientation, which SHALL be one of the enumerated DecisionTableOrientation. > It is therefore not wrong for us to include preferredOrientation and seems mandatory. > --------------------------------------------------------------------------------- > Our marshaller is EXPLICITLY setting inputExpression.id. > DMN1.2 Specification 8.3.2 - Decision Table Input and Output metamodel:- > ...An instance of InputClause is made of an optional inputExpression... [where an inputExpression is an Expression]. > There is not mention as to whether the Expression inherits its id or needs one explicitly defined. > Is it therefore incorrect for us to include the id? > --------------------------------------------------------------------------------- > Our marshaller IS NOT setting outputEntry.expressionLanguage. > DMN1.2 Specification 8.3.2 - Decision Table Input and Output metamodel states (well does NOT state anything!) : > OutputClause does not appear to have an expressionLanguage property; only the UnaryTests that is encapsulated by OutputClause supports it. > Is this an issue with _other tools_'s marshaller? > --------------------------------------------------------------------------------- > [DMN Designer] Marshaller does not support DMN1.2 DecisionTable RuleAnnotation > https://issues.redhat.com/browse/DROOLS-5045 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13122) Include MicroProfile Fault Tolerance subsystem in the default server profiles

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13122?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13122: ---------------------------------- Issue Type: Task (was: Bug) > Include MicroProfile Fault Tolerance subsystem in the default server profiles > ----------------------------------------------------------------------------- > > Key: WFLY-13122 > URL: https://issues.redhat.com/browse/WFLY-13122 > Project: WildFly > Issue Type: Task > Components: MP Fault Tolerance > Affects Versions: 19.0.0.Beta2 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 19.0.0.Beta3, 20.0.0.Beta1 > > > MP FT can be included in the default profiles. The subsystem is very lightweight, the subsystem carries no configuration and the module dependencies are not added to the deployments if the application is not using FT annotations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1070) Automate AuthPolicy https://github.com/kiali/kiali/pull/2261

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-1070: ------------------------------------- Summary: Automate AuthPolicy https://github.com/kiali/kiali/pull/2261 Key: SWSQE-1070 URL: https://issues.redhat.com/browse/SWSQE-1070 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1070) Automate AuthPolicy https://github.com/kiali/kiali/pull/2261

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1070?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1070: ---------------------------------- Labels: automation (was: ) > Automate AuthPolicy https://github.com/kiali/kiali/pull/2261 > ------------------------------------------------------------ > > Key: SWSQE-1070 > URL: https://issues.redhat.com/browse/SWSQE-1070 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1029) Add base abstraction over *ViewAbstract classes

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1029?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1029. ----------------------------------- Resolution: Done > Add base abstraction over *ViewAbstract classes > ----------------------------------------------- > > Key: SWSQE-1029 > URL: https://issues.redhat.com/browse/SWSQE-1029 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Currently all *ViewAbstract classes are extending Widget, but they can have single abstract parent with common methods. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-98) Update WildFly Elytron to 1.10.5.Final

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELYWEB-98?page=com.atlassian.jira.plugin... ] Darran Lofthouse resolved ELYWEB-98. ------------------------------------ Resolution: Done > Update WildFly Elytron to 1.10.5.Final > -------------------------------------- > > Key: ELYWEB-98 > URL: https://issues.redhat.com/browse/ELYWEB-98 > Project: Elytron Web > Issue Type: Component Upgrade > Components: Parent > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.6.1.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-98) Update WildFly Elytron to 1.10.5.Final

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELYWEB-98?page=com.atlassian.jira.plugin... ] Darran Lofthouse reopened ELYWEB-98: ------------------------------------ > Update WildFly Elytron to 1.10.5.Final > -------------------------------------- > > Key: ELYWEB-98 > URL: https://issues.redhat.com/browse/ELYWEB-98 > Project: Elytron Web > Issue Type: Component Upgrade > Components: Parent > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.6.1.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 February 2020