[JBoss JIRA] (WFLY-10997) WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups
by Lin Gao (Jira)
[ https://issues.jboss.org/browse/WFLY-10997?page=com.atlassian.jira.plugin... ]
Lin Gao reassigned WFLY-10997:
------------------------------
Assignee: Tomasz Adamski (was: Lin Gao)
> 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: Tomasz Adamski
> 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, 7 months
[JBoss JIRA] (WFLY-10837) IIOP subsystem requires port binding to be defined which was not necessary in prior WFLY versions
by Petr Kremensky (Jira)
[ https://issues.jboss.org/browse/WFLY-10837?page=com.atlassian.jira.plugin... ]
Petr Kremensky edited comment on WFLY-10837 at 10/12/18 2:09 AM:
-----------------------------------------------------------------
[~tomekadamski] Did you try to run the [reproducer|https://issues.jboss.org/browse/WFLY-10837?focusedCommentId=13... (I've updated it 7.2.0.CD14.CR1 -> 7.2.0.CD14.CR2)
The version of the subsystem before the target server is started is
{noformat}
<subsystem xmlns="urn:jboss:domain:iiop-openjdk:1.0">
<initializers transactions="spec" security="identity"/>
</subsystem>
{noformat}
so it seems to me that transformer doesn't do its job (I cannot see any transformation of iiop-openjdk after I start the target server with legacy config).
was (Author: pkremens):
[~tomekadamski] Did you try to run the [reproducer|https://issues.jboss.org/browse/WFLY-10837?focusedCommentId=13... (I've updated it 7.2.0.CD14.CR1 -> 7.2.0.CD14.CR2)
The version of the subsystem is before target server is started is
{noformat}
<subsystem xmlns="urn:jboss:domain:iiop-openjdk:1.0">
<initializers transactions="spec" security="identity"/>
</subsystem>
{noformat}
so it seems to me that transformer doesn't do its job (I cannot see any transformation of iiop-openjdk after I start the target server with legacy config).
> IIOP subsystem requires port binding to be defined which was not necessary in prior WFLY versions
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-10837
> URL: https://issues.jboss.org/browse/WFLY-10837
> Project: WildFly
> Issue Type: Bug
> Components: IIOP
> Reporter: Ondra Chaloupka
> Assignee: Tomasz Adamski
> Priority: Blocker
> Fix For: 14.0.0.Final
>
>
> If the {{standalone-*.xml}} configuration defines to use IIOP subsystem but it does not defines the port binding element
> {code}
> <orb socket-binding="iiop"/>
> {code}
> The server starts with error
> {code}
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.iiop-openjdk.orb-service: org.jboss.msc.service.StartException in service jboss.iiop-openjdk.orb-service: java.lang.IllegalStateException: WFLYIIOP0115: No IIOP socket bindings have been configured
> at org.wildfly.iiop.openjdk.service.CorbaORBService.start(CorbaORBService.java:150)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException: WFLYIIOP0115: No IIOP socket bindings have been configured
> at org.wildfly.iiop.openjdk.service.CorbaORBService.start(CorbaORBService.java:109)
> ... 8 more
> {code}
> The attribute of the {{socket-binding}} in the model is not defined as {{required}}.
> {code}
> "socket-binding" => {
> "type" => STRING,
> "description" => "The name of the socket binding configuration that specifies the ORB port.",
> "attribute-group" => "orb",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-constraints" => {"sensitive" => {"socket-binding-ref" => {"type" => "core"}}},
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> }
> {code}
> Up to that declaring the iiop socket binding was not necessary in WildFly 13.0.0.Final. Could that be a backward compatibility problem too?
> Up to that
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-10837) IIOP subsystem requires port binding to be defined which was not necessary in prior WFLY versions
by Petr Kremensky (Jira)
[ https://issues.jboss.org/browse/WFLY-10837?page=com.atlassian.jira.plugin... ]
Petr Kremensky commented on WFLY-10837:
---------------------------------------
[~brian.stansberry] your assumptions are correct, only 7.0.\(x\) is affected by this issue - see [eap-7.x-migration-tool-paths|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2....]
> IIOP subsystem requires port binding to be defined which was not necessary in prior WFLY versions
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-10837
> URL: https://issues.jboss.org/browse/WFLY-10837
> Project: WildFly
> Issue Type: Bug
> Components: IIOP
> Reporter: Ondra Chaloupka
> Assignee: Tomasz Adamski
> Priority: Blocker
> Fix For: 14.0.0.Final
>
>
> If the {{standalone-*.xml}} configuration defines to use IIOP subsystem but it does not defines the port binding element
> {code}
> <orb socket-binding="iiop"/>
> {code}
> The server starts with error
> {code}
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.iiop-openjdk.orb-service: org.jboss.msc.service.StartException in service jboss.iiop-openjdk.orb-service: java.lang.IllegalStateException: WFLYIIOP0115: No IIOP socket bindings have been configured
> at org.wildfly.iiop.openjdk.service.CorbaORBService.start(CorbaORBService.java:150)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException: WFLYIIOP0115: No IIOP socket bindings have been configured
> at org.wildfly.iiop.openjdk.service.CorbaORBService.start(CorbaORBService.java:109)
> ... 8 more
> {code}
> The attribute of the {{socket-binding}} in the model is not defined as {{required}}.
> {code}
> "socket-binding" => {
> "type" => STRING,
> "description" => "The name of the socket binding configuration that specifies the ORB port.",
> "attribute-group" => "orb",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-constraints" => {"sensitive" => {"socket-binding-ref" => {"type" => "core"}}},
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> }
> {code}
> Up to that declaring the iiop socket binding was not necessary in WildFly 13.0.0.Final. Could that be a backward compatibility problem too?
> Up to that
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3032) [DMN Designer] UX "empty" state for custom data types
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3032?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3032:
-------------------------------------
[~uxdlc] thanks.
> [DMN Designer] UX "empty" state for custom data types
> -----------------------------------------------------
>
> Key: DROOLS-3032
> URL: https://issues.jboss.org/browse/DROOLS-3032
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Screen Shot 2018-10-11 at 1.53.08 PM.png, Screen Shot 2018-10-11 at 10.56.18 AM.png, Screen Shot 2018-10-11 at 12.01.44 PM.png, Screenshot from 2018-09-24 18-12-02.png
>
>
> There is no visual information if no custom data type is defined. In the attached dialog we should differentiate between states when no custom da taype is declared and when some custom data types are declared. The same way we do it in list of spaces and list of projects.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11160) Upgrade jboss-el-api_spec from 1.0.12.Final to 1.0.13.Final
by Chao Wang (Jira)
[ https://issues.jboss.org/browse/WFLY-11160?page=com.atlassian.jira.plugin... ]
Chao Wang moved JBEAP-15653 to WFLY-11160:
------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-11160 (was: JBEAP-15653)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Web (Undertow)
(was: Web (Undertow))
Affects Version/s: 14.0.0.Final
(was: 7.2.0.CD14)
Fix Version/s: (was: 7.2.1.GA)
> Upgrade jboss-el-api_spec from 1.0.12.Final to 1.0.13.Final
> -----------------------------------------------------------
>
> Key: WFLY-11160
> URL: https://issues.jboss.org/browse/WFLY-11160
> Project: WildFly
> Issue Type: Component Upgrade
> Components: Web (Undertow)
> Affects Versions: 14.0.0.Final
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Major
> Labels: downstream_dependency
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3121) Stunner - Diagram Preview raises an exception due to hover event
by Guilherme Carreiro (Jira)
Guilherme Carreiro created DROOLS-3121:
------------------------------------------
Summary: Stunner - Diagram Preview raises an exception due to hover event
Key: DROOLS-3121
URL: https://issues.jboss.org/browse/DROOLS-3121
Project: Drools
Issue Type: Bug
Components: Stunner
Environment: Stunner - Diagram Preview raises an exception due to hover event
Reporter: Guilherme Carreiro
Assignee: Roger Martínez
Attachments: steps_to_reproduce.gif
Diagram Preview raises an exception due to hover event.
!steps_to_reproduce.gif|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-10837) IIOP subsystem requires port binding to be defined which was not necessary in prior WFLY versions
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-10837?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-10837:
-----------------------------------------
[~pkremens] My guess is you were using EAP 7.0 when changing the model resulted in losing the orb element from the xml? It looks like that was a bug in 7.0. I don't see that behavior in 7.1. In your example both of those attributes were configured with their default values, and in the past there have been some bugs with xml marshallers not bothering to write default values even though the user explicitly set the attribute (in this case via the original xml).
Anyway, that explains how you are hitting this scenario.
[~tomekadamski] I see a couple issues here:
1) The failure at org.wildfly.iiop.openjdk.service.CorbaORBService.start(CorbaORBService.java:150) should never occur. The model should have been rejected before CorbaService was even instantiated. I see there's a ConfigValidator class that's used for extra validation, so that could perhaps handle this.
2) The [ssl-]socket-binding attributes no longer have default values but the parsers for the legacy xsd versions do not preserve compatibility by adding in the legacy default values if no value was parsed. I've never used this before but it looks like the hook for doing that kind of extra thing is by using in the legacy parsers PersistentResourceXmlBuilder.setAdditionalOperationsGenerator. Pass in an AdditionalOperationsGenerator that will stick in the needed defaults if the attributes aren't already set.
BTW, it's valid that the metadata says neither 'socket-binding' nor 'ssl-socket-binding' is required. Neither is. It's just that at least one of them must be set, which is a situation that cannot be described via the metadata, except by the free form text description of the attributes.
> IIOP subsystem requires port binding to be defined which was not necessary in prior WFLY versions
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-10837
> URL: https://issues.jboss.org/browse/WFLY-10837
> Project: WildFly
> Issue Type: Bug
> Components: IIOP
> Reporter: Ondra Chaloupka
> Assignee: Tomasz Adamski
> Priority: Blocker
> Fix For: 14.0.0.Final
>
>
> If the {{standalone-*.xml}} configuration defines to use IIOP subsystem but it does not defines the port binding element
> {code}
> <orb socket-binding="iiop"/>
> {code}
> The server starts with error
> {code}
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.iiop-openjdk.orb-service: org.jboss.msc.service.StartException in service jboss.iiop-openjdk.orb-service: java.lang.IllegalStateException: WFLYIIOP0115: No IIOP socket bindings have been configured
> at org.wildfly.iiop.openjdk.service.CorbaORBService.start(CorbaORBService.java:150)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException: WFLYIIOP0115: No IIOP socket bindings have been configured
> at org.wildfly.iiop.openjdk.service.CorbaORBService.start(CorbaORBService.java:109)
> ... 8 more
> {code}
> The attribute of the {{socket-binding}} in the model is not defined as {{required}}.
> {code}
> "socket-binding" => {
> "type" => STRING,
> "description" => "The name of the socket binding configuration that specifies the ORB port.",
> "attribute-group" => "orb",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-constraints" => {"sensitive" => {"socket-binding-ref" => {"type" => "core"}}},
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> }
> {code}
> Up to that declaring the iiop socket binding was not necessary in WildFly 13.0.0.Final. Could that be a backward compatibility problem too?
> Up to that
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months