April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11957) Support Group Managed Service Accounts (gMSA) - extend LDAP feature

by Craig Carpenter (Jira)

[ https://issues.jboss.org/browse/WFLY-11957?page=com.atlassian.jira.plugin... ] Craig Carpenter commented on WFLY-11957: ---------------------------------------- >From what we have viewed - Wildfly is not supporting the gMSA account type where only the user credential is provided. The lack of a password in the connection string is resulting in a invalid connection attempt. > Support Group Managed Service Accounts (gMSA) - extend LDAP feature > ------------------------------------------------------------------- > > Key: WFLY-11957 > URL: https://issues.jboss.org/browse/WFLY-11957 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Craig Carpenter > Assignee: Darran Lofthouse > Priority: Major > > The introduction of gMSA in the enterprise is generating a need for support of this type of LDAP account where the user id is available but not the password. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11957) Support Group Managed Service Accounts (gMSA) - extend LDAP feature

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-11957?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFLY-11957: ----------------------------------------- I am assuming it is the following you are referring to? https://blogs.technet.microsoft.com/askpfeplat/2012/12/16/windows-server-... At this point it would be the WildFly Elytron security implementation we would look at adding new features to. In the context of this accounts what scenarios are you considering they need to be supported? Our LDAP realm implementation already has a flexible approach to defining the underlying LDAP queries. Are there some specific scenarios you are trying to achieve? > Support Group Managed Service Accounts (gMSA) - extend LDAP feature > ------------------------------------------------------------------- > > Key: WFLY-11957 > URL: https://issues.jboss.org/browse/WFLY-11957 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Craig Carpenter > Assignee: Darran Lofthouse > Priority: Major > > The introduction of gMSA in the enterprise is generating a need for support of this type of LDAP account where the user id is available but not the password. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2857) [DMN Designer] Incorporate Stunner Zoom controls

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-2857?page=com.atlassian.jira.plugi... ] Michael Anstis resolved DROOLS-2857. ------------------------------------ Fix Version/s: 7.20.0.Final Resolution: Out of Date [~roger600] implemented with https://issues.jboss.org/browse/JBPM-7443 > [DMN Designer] Incorporate Stunner Zoom controls > ------------------------------------------------ > > Key: DROOLS-2857 > URL: https://issues.jboss.org/browse/DROOLS-2857 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Elizabeth Clayton > Assignee: Michael Anstis > Priority: Major > Labels: UX, UXTeam, drools-tools > Fix For: 7.20.0.Final > > > Pick-up canvas Zoom control solution for DMN editor, solution documented at: https://issues.jboss.org/browse/JBPM-7443 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11957) Support Group Managed Service Accounts (gMSA) - extend LDAP feature

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-11957?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFLY-11957: ------------------------------------ Priority: Major (was: Critical) > Support Group Managed Service Accounts (gMSA) - extend LDAP feature > ------------------------------------------------------------------- > > Key: WFLY-11957 > URL: https://issues.jboss.org/browse/WFLY-11957 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Craig Carpenter > Assignee: Darran Lofthouse > Priority: Major > > The introduction of gMSA in the enterprise is generating a need for support of this type of LDAP account where the user id is available but not the password. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3868) Upgrade antlr4-runtime version to 4.7.2

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3868?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3868: ----------------------------------- Component/s: dmn engine (was: DMN Editor) > Upgrade antlr4-runtime version to 4.7.2 > --------------------------------------- > > Key: DROOLS-3868 > URL: https://issues.jboss.org/browse/DROOLS-3868 > Project: Drools > Issue Type: Task > Components: dmn engine > Affects Versions: 7.20.0.Final > Reporter: Dominik Hanak > Assignee: Dominik Hanak > Priority: Major > > There is a new version of antlr4-runtime - 4.7.2. We use 4.5.3 in community. > It would be nice to upgrade to version 4.7.2. > NOTE: This is also needed for - https://issues.jboss.org/browse/JBPM-8195 > I prepared a PR - https://github.com/kiegroup/droolsjbpm-build-bootstrap/pull/946 > Running FDB shows that 9 tests started to fail. > These are the failed tests: > {code:java} > org.kie.dmn.core.DMNRuntimeTest.testInvalidVariableNames[true] > org.kie.dmn.core.DMNRuntimeTest.testInvalidVariableNames[false] > org.kie.dmn.feel.parser.feel11.FEELParserTest.testVariableNameWithInvalidCharacterPercent > org.kie.dmn.feel.parser.feel11.FEELParserTest.testVariableNameWithInvalidCharacterAt > org.kie.dmn.validation.ValidatorTest.testVALIDATION > org.kie.dmn.validation.ValidatorTypeRefTest.testTYPEREF_NOT_FEEL_NOT_DEF_DefinitionsInput > org.kie.dmn.validation.ValidatorTypeRefTest.testTYPEREF_NOT_FEEL_NOT_DEF_FileInput > org.kie.dmn.validation.ValidatorTypeRefTest.testTYPEREF_NOT_FEEL_NOT_DEF_ReaderInput > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10607) Fix intermittent failures in *EJBForwardingTestCase

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-10607?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFLY-10607: --------------------------------------- Here is an example failure with the non-TX case: https://gist.github.com/rhusar/cdf3c175a0b8a8ac65d7ba27b7cbbd82 I find it unlikely to be a security issue given that its intermittent. > Fix intermittent failures in *EJBForwardingTestCase > --------------------------------------------------- > > Key: WFLY-10607 > URL: https://issues.jboss.org/browse/WFLY-10607 > Project: WildFly > Issue Type: Bug > Components: EJB, Test Suite > Affects Versions: 16.0.0.Final > Reporter: Petr Kremensky > Assignee: Richard Achmatowicz > Priority: Major > Attachments: org.jboss.as.test.clustering.cluster.ejb.forwarding.TxRemoteEJBForwardingTestCase-output.txt > > > The tests were ignored by https://github.com/wildfly/wildfly/pull/10563 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3854) DMN: Add a nested row to a new Structured data type by default

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3854?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-3854: ------------------------------------------- [~dmarrazzo]Thanks. We discussed this at the scrum meeting and I believe the preference is to do iterative enhancements as we continue to get more feedback - so the "Save" issue might be outside the scope of this specific jira. I believe we could go ahead with this jira (adding the child row by default) to the Structured type as a first step. Then make additional stories for the additional items. Have I restated that accurately [~karreiro]? And I just want to add a side note to this jira: [~karreiro] is it valid per the specs/standards to have a Structured type with no child types? If so, then we need to provide a means to address this in the auto-generated child row, wdyt? > DMN: Add a nested row to a new Structured data type by default > -------------------------------------------------------------- > > Key: DROOLS-3854 > URL: https://issues.jboss.org/browse/DROOLS-3854 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam > Attachments: Screen Shot 2019-04-03 at 4.15.11 PM.png > > > Usability: Reduce the number of clicks / actions to add a nested element. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10607) Fix intermittent failures in *EJBForwardingTestCase

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-10607?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10607: ---------------------------------- Attachment: org.jboss.as.test.clustering.cluster.ejb.forwarding.TxRemoteEJBForwardingTestCase-output.txt > Fix intermittent failures in *EJBForwardingTestCase > --------------------------------------------------- > > Key: WFLY-10607 > URL: https://issues.jboss.org/browse/WFLY-10607 > Project: WildFly > Issue Type: Bug > Components: EJB, Test Suite > Affects Versions: 16.0.0.Final > Reporter: Petr Kremensky > Assignee: Richard Achmatowicz > Priority: Major > Attachments: org.jboss.as.test.clustering.cluster.ejb.forwarding.TxRemoteEJBForwardingTestCase-output.txt > > > The tests were ignored by https://github.com/wildfly/wildfly/pull/10563 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1785) Guided Decision Table editor does not allow proper operators after editing a BRL clause

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1785?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-1785. ------------------------------- Fix Version/s: 7.21.0.Final Resolution: Out of Date The issue can not be reproduced anymore. > Guided Decision Table editor does not allow proper operators after editing a BRL clause > --------------------------------------------------------------------------------------- > > Key: DROOLS-1785 > URL: https://issues.jboss.org/browse/DROOLS-1785 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 6.1.0.Final > Environment: RedHat Linux 6.3 x86_64; firefox 10.0.5 > Reporter: Stephen Slaboda > Assignee: Guilherme Gomes > Priority: Major > Labels: decision_table, drools-wb > Fix For: 7.21.0.Final > > Attachments: Screenshot from 2019-04-10 15-23-27.png, exampleModel.png, occurrenceOfBug.png, sourceTabAfterBugObserved.png > > > When editing an existing BRL condition column in the guided rule editor, condition clauses in the BRL that compare using relational operators (i.e. <, >, etc.) for Long values (maybe other numerics as well) are reset to "--- please choose ---". The choices then given are only ==, !=, == NULL, and != NULL. > The choices should be the same as when I first selected "greater than or equal to" or the like, and should retain the value I originally set. Looking at the source tab, I still see the > value. This happens with both Literal and Formula entries (didn't try others). When initially editing the rule, this bug does not appear. However, after closing the editor and opening the rule in the decision table editor again, it happens consistently. > Looking at the .gdst file for the rule, I see that the <operator> tag for the column in question is >= in order to escape the XML tag trigger. This may be a factor in what is causing this bug. In my production environment, I am not able to make the decision table rule fire. > If I copy the source from the decision table editor's source tab into a pure DRL rule, the DRL rule fires just fine given the same input. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1785) Guided Decision Table editor does not allow proper operators after editing a BRL clause

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1785?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-1785: -------------------------------- Attachment: Screenshot from 2019-04-10 15-23-27.png > Guided Decision Table editor does not allow proper operators after editing a BRL clause > --------------------------------------------------------------------------------------- > > Key: DROOLS-1785 > URL: https://issues.jboss.org/browse/DROOLS-1785 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 6.1.0.Final > Environment: RedHat Linux 6.3 x86_64; firefox 10.0.5 > Reporter: Stephen Slaboda > Assignee: Guilherme Gomes > Priority: Major > Labels: decision_table, drools-wb > Fix For: 7.21.0.Final > > Attachments: Screenshot from 2019-04-10 15-23-27.png, exampleModel.png, occurrenceOfBug.png, sourceTabAfterBugObserved.png > > > When editing an existing BRL condition column in the guided rule editor, condition clauses in the BRL that compare using relational operators (i.e. <, >, etc.) for Long values (maybe other numerics as well) are reset to "--- please choose ---". The choices then given are only ==, !=, == NULL, and != NULL. > The choices should be the same as when I first selected "greater than or equal to" or the like, and should retain the value I originally set. Looking at the source tab, I still see the > value. This happens with both Literal and Formula entries (didn't try others). When initially editing the rule, this bug does not appear. However, after closing the editor and opening the rule in the decision table editor again, it happens consistently. > Looking at the .gdst file for the rule, I see that the <operator> tag for the column in question is >= in order to escape the XML tag trigger. This may be a factor in what is causing this bug. In my production environment, I am not able to make the decision table rule fire. > If I copy the source from the decision table editor's source tab into a pure DRL rule, the DRL rule fires just fine given the same input. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 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 April 2019