[JBoss JIRA] (WFCORE-4485) Support for multiple security realms - Distributed Identities
by Lumir Navrat (Jira)
[ https://issues.jboss.org/browse/WFCORE-4485?page=com.atlassian.jira.plugi... ]
Lumir Navrat commented on WFCORE-4485:
--------------------------------------
Our use case is this:
Eclipse RCP remote thick client that connect to WF server.
1. during connect to WF input username and password.
2. on server is now Elytron intermediate configuration that pass ot to JAAS. Where is configured our custom WinCoreLoginModule with sufficent and standard JDBC server login module. with sufficent too.
When user isn't authenticated in WinCoreModule than it is tried if exists in database. Our WinCoreModule allow authenticate user to the windows credentional store located on computer where server is running. In case when WF is instaled on same machine as thick client => clients computer.
I'm not sure if real mapper is usable in our use case. Because username is in same format for both login modules.
> Support for multiple security realms - Distributed Identities
> -------------------------------------------------------------
>
> Key: WFCORE-4485
> URL: https://issues.jboss.org/browse/WFCORE-4485
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Reporter: Farah Juma
> Priority: Major
> Labels: CD17-Deferred, EAP-CD19, Previous_RFE
> Fix For: 11.0.0.Beta1
>
>
> By stacking LoginModules it was possible using PicketBox to attempt to authenticate using one remote store and if that failed try the next store in the list.
> This RFE is to consider the use case where identities could be located across multiple stores and how they are aggregated together.
> Additionally this use case should consider how the authorization information could be loaded from multiple sources and merged.
> This RFE is not about fail over in the event of a realm being unavailable although it may be related.
> This RFE is created as a result of comparing the differences between the PicketBox JAAS architecture and the Elytron architecture so I would not recommend this proceeds without some real world use cases identified.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4171) rule filtering by folder-type packages attribute does not work after upgrading to 7.11.0.Final
by Hiroko Miura (Jira)
[ https://issues.jboss.org/browse/DROOLS-4171?page=com.atlassian.jira.plugi... ]
Hiroko Miura updated DROOLS-4171:
---------------------------------
Description:
In kjar project, there are many rules per folder under resources directory and
filtered these rules by using packages attribute in kmodule.xml.
e.g.
- file structure
{noformat}
src/main/resources/
├── logback-test.xml
├── META-INF
│ ├── kmodule.xml
│ └── maven
│ └── pom.properties
└── rules
├── aws
│ └── Sample1.drl
├── test1
│ └── Sample1.drl
└── test2
└── Sample2.drl
{noformat}
- kmodule.xml
{noformat}
<?xml version="1.0" encoding="UTF-8"?>
<kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule">
<kbase name="rules" packages="rules.aws">
<ksession name="ksession-rules"/>
</kbase>
</kmodule>
{noformat}
This could be built with library version 7.5.0.Final.
But after upgrading 7.11.0.Final or later, it fails.
was:
In kjar project, there are many rules per folder under resources directory and
filtered these rules by using packages attribute in kmodule.xml.
e.g.
- file structure
{noformat}
src/main/resources/
├── logback-test.xml
├── META-INF
│ ├── kmodule.xml
│ └── maven
│ └── pom.properties
└── rules
├── aws
│ └── Sample1.drl
├── test1
│ └── Sample1.drl
└── test2
└── Sample2.drl
{noformat}
- kmodule.xml
{noformat}
<?xml version="1.0" encoding="UTF-8"?>
<kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule">
<kbase name="rules" packages="rules.aws">
<ksession name="ksession-rules"/>
</kbase>
</kmodule>
{noformat}
This could be built with library version 7.11.0.Final.
But after upgrading 7.14.0.Final or later, it fails.
> rule filtering by folder-type packages attribute does not work after upgrading to 7.11.0.Final
> ------------------------------------------------------------------------------------------------
>
> Key: DROOLS-4171
> URL: https://issues.jboss.org/browse/DROOLS-4171
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.11.0.Final, 7.14.0.Final, 7.18.0.Final
> Reporter: Hiroko Miura
> Assignee: Mario Fusco
> Priority: Major
> Labels: support
> Attachments: buildKjarTest.zip
>
>
> In kjar project, there are many rules per folder under resources directory and
> filtered these rules by using packages attribute in kmodule.xml.
> e.g.
> - file structure
> {noformat}
> src/main/resources/
> ├── logback-test.xml
> ├── META-INF
> │ ├── kmodule.xml
> │ └── maven
> │ └── pom.properties
> └── rules
> ├── aws
> │ └── Sample1.drl
> ├── test1
> │ └── Sample1.drl
> └── test2
> └── Sample2.drl
> {noformat}
> - kmodule.xml
> {noformat}
> <?xml version="1.0" encoding="UTF-8"?>
> <kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule">
> <kbase name="rules" packages="rules.aws">
> <ksession name="ksession-rules"/>
> </kbase>
> </kmodule>
> {noformat}
> This could be built with library version 7.5.0.Final.
> But after upgrading 7.11.0.Final or later, it fails.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4171) rule filtering by folder-type packages attribute does not work after upgrading to 7.11.0.Final
by Hiroko Miura (Jira)
[ https://issues.jboss.org/browse/DROOLS-4171?page=com.atlassian.jira.plugi... ]
Hiroko Miura updated DROOLS-4171:
---------------------------------
Description:
In kjar project, there are many rules per folder under resources directory and
filtered these rules by using packages attribute in kmodule.xml.
e.g.
- file structure
{noformat}
src/main/resources/
├── logback-test.xml
├── META-INF
│ ├── kmodule.xml
│ └── maven
│ └── pom.properties
└── rules
├── aws
│ └── Sample1.drl
├── test1
│ └── Sample1.drl
└── test2
└── Sample2.drl
{noformat}
- kmodule.xml
{noformat}
<?xml version="1.0" encoding="UTF-8"?>
<kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule">
<kbase name="rules" packages="rules.aws">
<ksession name="ksession-rules"/>
</kbase>
</kmodule>
{noformat}
This could be built with library version 7.11.0.Final.
But after upgrading 7.14.0.Final or later, it fails.
was:
In kjar project, there are many rules per folder under resources directory and
filtered these rules by using packages attribute in kmodule.xml.
e.g.
src/main/resources/
├── logback-test.xml
├── META-INF
│ ├── kmodule.xml
│ └── maven
│ └── pom.properties
└── rules
├── aws
│ └── Sample1.drl
├── test1
│ └── Sample1.drl
└── test2
└── Sample2.drl
- kmodule.xml
{noformat}
<?xml version="1.0" encoding="UTF-8"?>
<kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule">
<kbase name="rules" packages="rules.aws">
<ksession name="ksession-rules"/>
</kbase>
</kmodule>
{noformat}
This could be built with library version 7.11.0.Final.
But after upgrading 7.14.0.Final or later, it fails.
> rule filtering by folder-type packages attribute does not work after upgrading to 7.11.0.Final
> ------------------------------------------------------------------------------------------------
>
> Key: DROOLS-4171
> URL: https://issues.jboss.org/browse/DROOLS-4171
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.11.0.Final, 7.14.0.Final, 7.18.0.Final
> Reporter: Hiroko Miura
> Assignee: Mario Fusco
> Priority: Major
> Labels: support
> Attachments: buildKjarTest.zip
>
>
> In kjar project, there are many rules per folder under resources directory and
> filtered these rules by using packages attribute in kmodule.xml.
> e.g.
> - file structure
> {noformat}
> src/main/resources/
> ├── logback-test.xml
> ├── META-INF
> │ ├── kmodule.xml
> │ └── maven
> │ └── pom.properties
> └── rules
> ├── aws
> │ └── Sample1.drl
> ├── test1
> │ └── Sample1.drl
> └── test2
> └── Sample2.drl
> {noformat}
> - kmodule.xml
> {noformat}
> <?xml version="1.0" encoding="UTF-8"?>
> <kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule">
> <kbase name="rules" packages="rules.aws">
> <ksession name="ksession-rules"/>
> </kbase>
> </kmodule>
> {noformat}
> This could be built with library version 7.11.0.Final.
> But after upgrading 7.14.0.Final or later, it fails.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4171) rule filtering by folder-type packages attribute does not work after upgrading to 7.11.0.Final
by Hiroko Miura (Jira)
[ https://issues.jboss.org/browse/DROOLS-4171?page=com.atlassian.jira.plugi... ]
Hiroko Miura updated DROOLS-4171:
---------------------------------
Steps to Reproduce:
1. build attached reproducer project by 'mvn clean install'.
=> this works without error.
2. edit pom.xml and change runtime.version
You can see the following version is set.
{noformat}
<runtime.version>7.5.0.Final-redhat-6</runtime.version--> <!-- RHDM 7.0.1 -->
{noformat}
set more later version than this, say 7.11.0.Final-redhat-00003.
3. build again by 'mvn clean install'.
=> this fails with the following error
{noformat}
[ERROR] Unable to build KieBaseModel:defaultKieBase
[5,0]: Duplicate rule name: rule1
Rule Compilation error : [Rule name='rule1']
com/sample/Rule_rule1713162208.java (3:123) : The type Rule_rule1713162208 is already defined
{noformat}
was:
1. build attached reproducer project by 'mvn clean install'.
=> this works without error.
2. edit pom.xml and change runtime.version
You can see the following version is set.
{noformat}
<runtime.version>7.5.0.Final-redhat-6</runtime.version--> <!-- RHDM 7.0.1 -->
{noformat}
set more later version than this, say 7.11.0.Final-redhat-00003.
3. build again by 'mvn clean install'.
=> this fails with the following error
[ERROR] Unable to build KieBaseModel:defaultKieBase
[5,0]: Duplicate rule name: rule1
Rule Compilation error : [Rule name='rule1']
com/sample/Rule_rule1713162208.java (3:123) : The type Rule_rule1713162208 is already defined
> rule filtering by folder-type packages attribute does not work after upgrading to 7.11.0.Final
> ------------------------------------------------------------------------------------------------
>
> Key: DROOLS-4171
> URL: https://issues.jboss.org/browse/DROOLS-4171
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.11.0.Final, 7.14.0.Final, 7.18.0.Final
> Reporter: Hiroko Miura
> Assignee: Mario Fusco
> Priority: Major
> Labels: support
> Attachments: buildKjarTest.zip
>
>
> In kjar project, there are many rules per folder under resources directory and
> filtered these rules by using packages attribute in kmodule.xml.
> e.g.
> src/main/resources/
> ├── logback-test.xml
> ├── META-INF
> │ ├── kmodule.xml
> │ └── maven
> │ └── pom.properties
> └── rules
> ├── aws
> │ └── Sample1.drl
> ├── test1
> │ └── Sample1.drl
> └── test2
> └── Sample2.drl
> - kmodule.xml
> {noformat}
> <?xml version="1.0" encoding="UTF-8"?>
> <kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule">
> <kbase name="rules" packages="rules.aws">
> <ksession name="ksession-rules"/>
> </kbase>
> </kmodule>
> {noformat}
> This could be built with library version 7.11.0.Final.
> But after upgrading 7.14.0.Final or later, it fails.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4171) rule filtering by folder-type packages attribute does not work after upgrading to 7.11.0.Final
by Hiroko Miura (Jira)
[ https://issues.jboss.org/browse/DROOLS-4171?page=com.atlassian.jira.plugi... ]
Hiroko Miura updated DROOLS-4171:
---------------------------------
Steps to Reproduce:
1. build attached reproducer project by 'mvn clean install'.
=> this works without error.
2. edit pom.xml and change runtime.version
You can see the following version is set.
{noformat}
<runtime.version>7.5.0.Final-redhat-6</runtime.version--> <!-- RHDM 7.0.1 -->
{noformat}
set more later version than this, say 7.11.0.Final-redhat-00003.
3. build again by 'mvn clean install'.
=> this fails with the following error
[ERROR] Unable to build KieBaseModel:defaultKieBase
[5,0]: Duplicate rule name: rule1
Rule Compilation error : [Rule name='rule1']
com/sample/Rule_rule1713162208.java (3:123) : The type Rule_rule1713162208 is already defined
was:
1. build attached reproducer project by 'mvn clean install'.
2. edit pom.xml and change runtime.version
You can see the following version is set.
{noformat}
<runtime.version>7.5.0.Final-redhat-6</runtime.version--> <!-- RHDM 7.0.1 -->
{noformat}
set more later version than this, say 7.11.0.Final-redhat-00003.
3. build again by 'mvn clean install'.
=> this fails with the following error
[ERROR] Unable to build KieBaseModel:defaultKieBase
[5,0]: Duplicate rule name: rule1
Rule Compilation error : [Rule name='rule1']
com/sample/Rule_rule1713162208.java (3:123) : The type Rule_rule1713162208 is already defined
> rule filtering by folder-type packages attribute does not work after upgrading to 7.11.0.Final
> ------------------------------------------------------------------------------------------------
>
> Key: DROOLS-4171
> URL: https://issues.jboss.org/browse/DROOLS-4171
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.11.0.Final, 7.14.0.Final, 7.18.0.Final
> Reporter: Hiroko Miura
> Assignee: Mario Fusco
> Priority: Major
> Labels: support
> Attachments: buildKjarTest.zip
>
>
> In kjar project, there are many rules per folder under resources directory and
> filtered these rules by using packages attribute in kmodule.xml.
> e.g.
> src/main/resources/
> ├── logback-test.xml
> ├── META-INF
> │ ├── kmodule.xml
> │ └── maven
> │ └── pom.properties
> └── rules
> ├── aws
> │ └── Sample1.drl
> ├── test1
> │ └── Sample1.drl
> └── test2
> └── Sample2.drl
> - kmodule.xml
> {noformat}
> <?xml version="1.0" encoding="UTF-8"?>
> <kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule">
> <kbase name="rules" packages="rules.aws">
> <ksession name="ksession-rules"/>
> </kbase>
> </kmodule>
> {noformat}
> This could be built with library version 7.11.0.Final.
> But after upgrading 7.14.0.Final or later, it fails.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4171) rule filtering by folder-type packages attribute does not work after upgrading to 7.11.0.Final
by Hiroko Miura (Jira)
Hiroko Miura created DROOLS-4171:
------------------------------------
Summary: rule filtering by folder-type packages attribute does not work after upgrading to 7.11.0.Final
Key: DROOLS-4171
URL: https://issues.jboss.org/browse/DROOLS-4171
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.18.0.Final, 7.14.0.Final, 7.11.0.Final
Reporter: Hiroko Miura
Assignee: Mario Fusco
Attachments: buildKjarTest.zip
In kjar project, there are many rules per folder under resources directory and
filtered these rules by using packages attribute in kmodule.xml.
e.g.
src/main/resources/
├── logback-test.xml
├── META-INF
│ ├── kmodule.xml
│ └── maven
│ └── pom.properties
└── rules
├── aws
│ └── Sample1.drl
├── test1
│ └── Sample1.drl
└── test2
└── Sample2.drl
- kmodule.xml
{noformat}
<?xml version="1.0" encoding="UTF-8"?>
<kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule">
<kbase name="rules" packages="rules.aws">
<ksession name="ksession-rules"/>
</kbase>
</kmodule>
{noformat}
This could be built with library version 7.11.0.Final.
But after upgrading 7.14.0.Final or later, it fails.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ]
Daniele Zonca commented on DROOLS-3731:
---------------------------------------
[~uxdlc]
The panel [~porcelli] was referring to is the test result panel displayed when user executes all the tests at project level (using {{Test}} button near {{Build}} and {{Deploy}}) so I expect it is out of scope for this ticket.
[~karreiro]
Yes I agree, as soon as we will define color classification or something similar to highlight different coverage status we should update at least the second section of the coverage report (decisions sorted by number of time each of them as been executed)
[~zhutaojiajia] [~uxdlc]
About DMN I expect the entire flow will be something like:
- user creates a DMN model
- user creates a test scenario to test that model
- user executes test scenario and it has some errors
- user click somewhere ({{Go to model}} maybe?)
- when DMN editor is opened following that link/button it will highlight test scenario result (I like [~tirelli] proposal here about two different behaviors)
I think we could place a generic {{Go to model}} link on the top of the coverage report panel and then another button like {{Analyse scenario results}} for each scenario in the third section of the panel
!tmp.png|thumbnail! (forgive me for my bad image editing skill :) )
I'm not sure I like that this proposal because the only way to have this "enhanced" view in DMN editor will be following a link from test scenario but I don't have in mind any other flow to propose
I think it could be nice to support a similar feature also in test report at project level. If we agree to do that I would suggest to track this with a different ticket because when we run all test scenarios at project level BC executes DMN based scenarios, Rule based scenarios and old test scenarios too so we need to defined a sort of global coverage report and the interaction flow.
> DMN UX - More info overlaid on models.
> --------------------------------------
>
> Key: DROOLS-3731
> URL: https://issues.jboss.org/browse/DROOLS-3731
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Tao Zhu
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam, drools-tools
> Attachments: Screen Shot 2019-05-29 at 2.49.21 PM.png, colors.png, download (1).png, download.png, multi.gif, single.gif, tmp.png, 屏幕快照 2019-06-11 下午3.02.19.png, 屏幕快照 2019-06-11 下午3.10.26.png
>
>
> As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression.
> Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-3731:
----------------------------------
Attachment: tmp.png
> DMN UX - More info overlaid on models.
> --------------------------------------
>
> Key: DROOLS-3731
> URL: https://issues.jboss.org/browse/DROOLS-3731
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Tao Zhu
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam, drools-tools
> Attachments: Screen Shot 2019-05-29 at 2.49.21 PM.png, colors.png, download (1).png, download.png, multi.gif, single.gif, tmp.png, 屏幕快照 2019-06-11 下午3.02.19.png, 屏幕快照 2019-06-11 下午3.10.26.png
>
>
> As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression.
> Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-3731:
----------------------------------
Attachment: (was: tmp.png)
> DMN UX - More info overlaid on models.
> --------------------------------------
>
> Key: DROOLS-3731
> URL: https://issues.jboss.org/browse/DROOLS-3731
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Tao Zhu
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam, drools-tools
> Attachments: Screen Shot 2019-05-29 at 2.49.21 PM.png, colors.png, download (1).png, download.png, multi.gif, single.gif, tmp.png, 屏幕快照 2019-06-11 下午3.02.19.png, 屏幕快照 2019-06-11 下午3.10.26.png
>
>
> As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression.
> Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-3731:
----------------------------------
Attachment: tmp.png
> DMN UX - More info overlaid on models.
> --------------------------------------
>
> Key: DROOLS-3731
> URL: https://issues.jboss.org/browse/DROOLS-3731
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Tao Zhu
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam, drools-tools
> Attachments: Screen Shot 2019-05-29 at 2.49.21 PM.png, colors.png, download (1).png, download.png, multi.gif, single.gif, tmp.png, 屏幕快照 2019-06-11 下午3.02.19.png, 屏幕快照 2019-06-11 下午3.10.26.png
>
>
> As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression.
> Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month