[JBoss JIRA] (WFLY-10997) WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups
by Bartosz Baranowski (Jira)
[ https://issues.jboss.org/browse/WFLY-10997?page=com.atlassian.jira.plugin... ]
Bartosz Baranowski updated WFLY-10997:
--------------------------------------
Workaround Description: @RunAs("ejbuser") seems to alleviate problem. (At least if declared on Servlet from: http://lacrosse.corp.redhat.com/lgao/WFLY-10997_reproducer.zip)
> WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups
> -----------------------------------------------------------------------------------------------------
>
> Key: WFLY-10997
> URL: https://issues.jboss.org/browse/WFLY-10997
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Lin Gao
> Assignee: Bartosz Baranowski
> Priority: Major
> Labels: downstream_dependency
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups
> Using WildFlyInitialContextFactory and calling a remote EJB server.
> Observations:
> 1) If the ejb lookup is "reproducer/TestSLSB!test.Test" (basically like a RemoteNaming lookup), the ejb is invoked successfully, but the caller is seen as anonymous instead of the ejbuser which is specified in the Context properties.
> Using the ejb-client type lookup: ejb:/reproducer/TestSLSB!test.Test , then it shows up as ejbuser as expected
> 2) if a client creates 2 InitialContexts and uses the lookup reproducer/TestSLSB!test.Test" on ctx1 , then uses the lookup "ejb:/reproducer/TestSLSB!test.Test " on ctx2 in that order, then they both show anonymous (as if it uses only the context that was created first).
> If you switch the order, and use ejb:/reproducer/TestSLSB!test.Test first, then they both show ejbuser
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3154) Minor UI improvements/bugfixes for Scenario
by Juraj Soltes (Jira)
[ https://issues.jboss.org/browse/DROOLS-3154?page=com.atlassian.jira.plugi... ]
Juraj Soltes commented on DROOLS-3154:
--------------------------------------
[~uxdlc] Thank you :). [~gabriolo] Regarding the header menu, I would remove it from there, too. I think there it is even more confusing, since I would expect to have only header-related actions in the header context menu.
> Minor UI improvements/bugfixes for Scenario
> -------------------------------------------
>
> Key: DROOLS-3154
> URL: https://issues.jboss.org/browse/DROOLS-3154
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Critical
> Labels: UX-CSS
> Attachments: test-editor-margin.png
>
>
> This item contains a list of general UI bugs to be fixed:
> - Use grey borders for all the grid and not only for the header
> - Add some padding to the cells of the grid
> - Add some padding to right panel the tab titles
> - Remove scrolling bar from right panel
> - Review expression editor component HTML/CSS (paddings, indents, etc)
> - Review right panel padding (now it is hardcoded)
> - Use text area inputs instead of text box for inline editing
> - Reduce the width of Index column
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3169) [DMN Designer] Last Context Entry differentiation
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3169?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3169:
-----------------------------------
Sprint: (was: 2018 Week 42-44)
> [DMN Designer] Last Context Entry differentiation
> -------------------------------------------------
>
> Key: DROOLS-3169
> URL: https://issues.jboss.org/browse/DROOLS-3169
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot 2018-10-23 18.37.56.png, Screenshot from 2018-10-22 17-35-07.png
>
>
> The last Context Entry, shown in the attachment, should be differentiated to other Context Entries. Currently we differentiate it just by the Name *Default* that user can not change.
> We should improve this in one of the following ways:
> - Keep name *Default*, change font to italics and use grey background color
> - Merge the *Default* and *Value* cells of last entry and remove the name *Default*
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months