[JBoss JIRA] (WFCORE-5007) Make use of the SocketAddressCallbackServerMechanismFactory to set the peer's IP address during HTTP authentication
by Farah Juma (Jira)
Farah Juma created WFCORE-5007:
----------------------------------
Summary: Make use of the SocketAddressCallbackServerMechanismFactory to set the peer's IP address during HTTP authentication
Key: WFCORE-5007
URL: https://issues.redhat.com/browse/WFCORE-5007
Project: WildFly Core
Issue Type: Task
Components: Security
Reporter: Farah Juma
Assignee: Farah Juma
WFCORE-4725 added the ability to configure a {{source-address-role-decoder}} to make use of the client's IP address for authorization decisions. Currently, it's only possible to make use of the IP address of a remote client during SASL authentication. To be able to make use of the IP address of a client during HTTP authentication, we just need to make use of a {{SocketAddressCallbackServerMechanismFactory}} to inform the server's callback handler of the peer's address.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (LOGMGR-278) PeriodicRotatingFileHandler may fail to rotate a file with a security permission
by James Perkins (Jira)
James Perkins created LOGMGR-278:
------------------------------------
Summary: PeriodicRotatingFileHandler may fail to rotate a file with a security permission
Key: LOGMGR-278
URL: https://issues.redhat.com/browse/LOGMGR-278
Project: JBoss Log Manager
Issue Type: Bug
Components: core
Reporter: James Perkins
Assignee: James Perkins
Fix For: 2.2.0.Final, 2.1.17.Final, 2.3.0.Beta1
During rotate the {{File.lastModified()}} time is used to determine if the file is ready to rotate. In situations such as a deployment on WildFly the deployment itself may fail to log a message as the security context is that of the deployment. The reason for the failure is the deployment does not have read permissions for the file.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (DROOLS-5147) [DMN Designer] DMN Decision Table - Input/Output clauses enhancements (UX)
by Elizabeth Clayton (Jira)
[ https://issues.redhat.com/browse/DROOLS-5147?page=com.atlassian.jira.plug... ]
Elizabeth Clayton updated DROOLS-5147:
--------------------------------------
Sprint: 2020 Week 25-27 (from Jun 15)
> [DMN Designer] DMN Decision Table - Input/Output clauses enhancements (UX)
> --------------------------------------------------------------------------
>
> Key: DROOLS-5147
> URL: https://issues.redhat.com/browse/DROOLS-5147
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: UXTeam, drools-tools
> Attachments: prototype.png
>
>
> Currently, the DMN Decision Tables input/output clauses work fine, but they have the following unpractical scenarios:
> - When users have a structure input node "associated" with an input clause (input column), they frequently need to go back to the data types page and remember the name of some field.
> - When users select a structure data type as the type of an output clause, they need to create sub-columns for each field manually.
> The goal for this JIRA is to get input from UX to enhance interactions with input and output clauses.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (DROOLS-5147) [DMN Designer] DMN Decision Table - Input/Output clauses enhancements (UX)
by Elizabeth Clayton (Jira)
[ https://issues.redhat.com/browse/DROOLS-5147?page=com.atlassian.jira.plug... ]
Elizabeth Clayton updated DROOLS-5147:
--------------------------------------
Labels: UXTeam drools-tools (was: drools-tools)
> [DMN Designer] DMN Decision Table - Input/Output clauses enhancements (UX)
> --------------------------------------------------------------------------
>
> Key: DROOLS-5147
> URL: https://issues.redhat.com/browse/DROOLS-5147
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: UXTeam, drools-tools
> Attachments: prototype.png
>
>
> Currently, the DMN Decision Tables input/output clauses work fine, but they have the following unpractical scenarios:
> - When users have a structure input node "associated" with an input clause (input column), they frequently need to go back to the data types page and remember the name of some field.
> - When users select a structure data type as the type of an output clause, they need to create sub-columns for each field manually.
> The goal for this JIRA is to get input from UX to enhance interactions with input and output clauses.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (DROOLS-5332) [DMN Designer] Unable to open BKM editor
by Guilherme Gomes (Jira)
[ https://issues.redhat.com/browse/DROOLS-5332?page=com.atlassian.jira.plug... ]
Guilherme Gomes updated DROOLS-5332:
------------------------------------
Sprint: 2020 Week 25-27 (from Jun 15)
> [DMN Designer] Unable to open BKM editor
> -----------------------------------------
>
> Key: DROOLS-5332
> URL: https://issues.redhat.com/browse/DROOLS-5332
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.38.0.Final
> Reporter: Michael Anstis
> Assignee: Valentino Pellegrino
> Priority: Major
> Labels: drools-tools, field, kogito-tooling, support
>
> Using the referenced file:
> https://kiegroup.github.io/kogito-online/?file=https://gist.githubusercon...
> The User is unable to edit the Business Knowledge Model nodes for the following nodes:
> - Risk Rating for Last Transaction Amount
> - Risk Rating for last 24 hours Transactions
> The {{kogito-tooling}} version reports the following to the console.
> {code}
> Error: JavaScriptException: (TypeError) : Cannot read property 'd' of null
> at Xys (/kogito-online/org.kie.workbench.common.dmn.showcase.DMNKogitoRuntimeWebapp-0.js:30330)
> at tes.a6r [as FW] (/kogito-online/org.kie.workbench.common.dmn.showcase.DMNKogitoRuntimeWebapp-0.js:31966)
> at Ist (/kogito-online/org.kie.workbench.common.dmn.showcase.DMNKogitoRuntimeWebapp-0.js:27657)
> at ntt.ptt [as yW] (/kogito-online/org.kie.workbench.common.dmn.showcase.DMNKogitoRuntimeWebapp-0.js:31973)
> at Q4r (/kogito-online/org.kie.workbench.common.dmn.showcase.DMNKogitoRuntimeWebapp-0.js:29779)
> at roy.soy [as J7] (/kogito-online/org.kie.workbench.common.dmn.showcase.DMNKogitoRuntimeWebapp-0.js:31999)
> at _Vr (/kogito-online/org.kie.workbench.common.dmn.showcase.DMNKogitoRuntimeWebapp-0.js:13043)
> {code}
> Sorry I have no debugged myself further.
> h3. Acceptance criteria:
> - Open BKM editor on business central
> - VS Code
> - Online editor
> - Desktop app
> - Github extension
> - Check the Documentation tab can be viewed too
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months