[Red Hat JIRA] (WFLY-14189) The RunAs annotation doesn't work in EJBs with Elytron
by Diana Vilkolakova (Jira)
[ https://issues.redhat.com/browse/WFLY-14189?page=com.atlassian.jira.plugi... ]
Diana Vilkolakova commented on WFLY-14189:
------------------------------------------
[~alessandromoscatelli] I tried running your example with legacy security and I also had to specify security domain explicitly. Can I ask which version you had it working with? Thanks!
> The RunAs annotation doesn't work in EJBs with Elytron
> ------------------------------------------------------
>
> Key: WFLY-14189
> URL: https://issues.redhat.com/browse/WFLY-14189
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Security
> Affects Versions: 21.0.0.Final
> Reporter: Alessandro Moscatelli
> Assignee: Diana Vilkolakova
> Priority: Major
> Labels: ejb, elytron, regression, runas, security, startup
> Attachments: standalone-full-ha.new.xml, test.zip
>
>
> Role is not correctly assigned when using @RunAs annotation and Elytron Security Domain. Everything works correctly with legacy picketbox Security Domain.
> Wildfly is configured to use default "other" application-security-domain, also using default security domain ApplicationDomain.
> This exception is rised when deploying the application.
> Caused by: javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public abstract void org.visiontech.test.TestInterface.test() of bean: Test2 is not allowedCaused by: javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public abstract void org.visiontech.test.TestInterface.test() of bean: Test2 is not allowed at org.jboss.as.ejb3@21.0.0.Final//org.jboss.as.ejb3.security.JaccInterceptor.hasPermission(JaccInterceptor.java:120)
> Test/Sample project: [^test.zip]
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (WFWIP-369) EAP metrics are shown on Metrics dashboard but not from linked Prometheus UI in OCP web console
by Jan Kasik (Jira)
[ https://issues.redhat.com/browse/WFWIP-369?page=com.atlassian.jira.plugin... ]
Jan Kasik moved CLOUD-3880 to WFWIP-369:
----------------------------------------
Component/s: OpenShift
(was: EAP7)
Key: WFWIP-369 (was: CLOUD-3880)
Affects Version/s: (was: EAP73 7.3.7.GA)
Workflow: GIT Pull Request workflow (was: CDW v1)
Project: WildFly WIP (was: Cloud Enablement)
> EAP metrics are shown on Metrics dashboard but not from linked Prometheus UI in OCP web console
> -----------------------------------------------------------------------------------------------
>
> Key: WFWIP-369
> URL: https://issues.redhat.com/browse/WFWIP-369
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Jan Kasik
> Assignee: Jeff Mesnil
> Priority: Critical
> Labels: operator
>
> The Prometheus instance linked to "Prometheus UI" link is not able to query metrics from EAP. If this intentional, the integration and user experience is flawed because users can be confused since the link is not labeled properly.
> This is a bug in integration of Prometheus, OpenShift and EAP.
> cc [~jdenise]
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (WFLY-14298) Using fault-tolerance in Wildfly 22 causes WELD-001408
by sdfsd fsdfsdf (Jira)
sdfsd fsdfsdf created WFLY-14298:
------------------------------------
Summary: Using fault-tolerance in Wildfly 22 causes WELD-001408
Key: WFLY-14298
URL: https://issues.redhat.com/browse/WFLY-14298
Project: WildFly
Issue Type: Bug
Components: EE
Affects Versions: 22.0.0.Final
Reporter: sdfsd fsdfsdf
Assignee: Brian Stansberry
In wildfly 21, I used to put these lines into the standalone-full-ha.xml:
<extension module="org.wildfly.extension.microprofile.fault-tolerance-smallrye"/>
...
<subsystem xmlns="urn:wildfly:microprofile-fault-tolerance-smallrye:1.0"/>
If I put those lines into the standalone-full-ha.xml of Wildfly 22 I get the following error when deploying an appliction that uses fault-tolerance:
WELD-001408: Unsatisfied dependencies for type MetricRegistry with qualifiers @Default
@Inject io.smallrye.faulttolerance.metrics.MetricsCollectorFactory.registry
I already have these lines in the standalone:
<extension module="org.wildfly.extension.metrics"/>
<extension module="org.wildfly.extension.health"/>
Is there something else I need to add in the standalone in order to keep using fault-tolerance in Wildfly 22?
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (DROOLS-5911) It's not possible to save arrow edits on DMN Editor
by Guilherme Gomes (Jira)
[ https://issues.redhat.com/browse/DROOLS-5911?page=com.atlassian.jira.plug... ]
Guilherme Gomes commented on DROOLS-5911:
-----------------------------------------
Hi [~roger600], as this is not a blocker, I would leave the fix for 7.11. However, let's see what [~davidredhat] thinks.
> It's not possible to save arrow edits on DMN Editor
> ---------------------------------------------------
>
> Key: DROOLS-5911
> URL: https://issues.redhat.com/browse/DROOLS-5911
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.48.0.Final
> Reporter: Wagner Lemos
> Assignee: Wagner Lemos
> Priority: Major
> Labels: Stunner, kogito, kogito-tooling
>
> On the DMN Editor, making a change on the arrow that connects two nodes isn't being saved. An example of change is moving the rear or tip of the arrow to another side of the node
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months