[Red Hat JIRA] (ELY-2049) Add trace capability to o.w.s.m.WildFlySecurityManager findAccessDenial
by Boris Unckel (Jira)
Boris Unckel created ELY-2049:
---------------------------------
Summary: Add trace capability to o.w.s.m.WildFlySecurityManager findAccessDenial
Key: ELY-2049
URL: https://issues.redhat.com/browse/ELY-2049
Project: WildFly Elytron
Issue Type: Enhancement
Components: Security Manager
Affects Versions: 1.13.0.CR1
Reporter: Boris Unckel
The current implementation is very strong for regular cases. It works fine to display missing permissions when CodeSource and/or ClassLoader are correctly set to the checked protection domain. If one of those is missing and there is no good exception handling, it is impossible to track down missing permissions.
Example:
[java.io.File|https://github.com/openjdk/jdk/blob/jdk-11%2B28/src/java.bas...]
line 2048
The idea is to provide a yielded trace log and provide the missing permission, the full protection domain and a dummy exception to have stack trace where this occurs.
Current code:
{code:java}
public static ProtectionDomain findAccessDenial(final Permission permission, final ProtectionDomain... domains) {
ProtectionDomain deniedDomain = null;
if (domains != null) for (ProtectionDomain domain : domains) {
if (! domain.implies(permission)) {
final CodeSource codeSource = domain.getCodeSource();
final ClassLoader classLoader = domain.getClassLoader();
final Principal[] principals = domain.getPrincipals();
if (principals == null || principals.length == 0) {
access.accessCheckFailed(permission, codeSource, classLoader);
} else {
access.accessCheckFailed(permission, codeSource, classLoader, Arrays.toString(principals));
}
if (deniedDomain == null && ! LOG_ONLY) {
deniedDomain = domain;
}
}
}
return deniedDomain;
}
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (WFCORE-4291) Restore legacy (not "graceful") startup mode
by Jeff Mesnil (Jira)
[ https://issues.redhat.com/browse/WFCORE-4291?page=com.atlassian.jira.plug... ]
Jeff Mesnil reassigned WFCORE-4291:
-----------------------------------
Assignee: Jeff Mesnil (was: Jason Lee)
> Restore legacy (not "graceful") startup mode
> --------------------------------------------
>
> Key: WFCORE-4291
> URL: https://issues.redhat.com/browse/WFCORE-4291
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Management
> Reporter: Vladimir Grabarchuk
> Assignee: Jeff Mesnil
> Priority: Major
>
> Please allow a configurable legacy startup mode which was the default before WF11, when components can service HTTP requests as soon as they are deployed, not when the container deploys all components.
> The use case for this is the following: there is a configuration service component upon which other components depend for configuration data, requested and served via a HTTP request. With the new "graceful startup" this scenario no longer seems possible, as it results in read timeouts, mis-configured artifacts, and failed deployments altogether.
> If generally feasible, another value of the *--start-mode=legacy* seems appropriate to accommodate the original (legacy) behavior.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (DROOLS-5872) DrlDumper generates wrong drl when AccumulateDescr does not have constraint
by Hiroko Miura (Jira)
Hiroko Miura created DROOLS-5872:
------------------------------------
Summary: DrlDumper generates wrong drl when AccumulateDescr does not have constraint
Key: DROOLS-5872
URL: https://issues.redhat.com/browse/DROOLS-5872
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.46.0.Final, 7.44.0.Final
Reporter: Hiroko Miura
Assignee: Mario Fusco
Attachments: accumulate-without-constraint-test.zip
When AccumulateDescr does not have constraint, generated DRL can not be built.
Here is an example code.
{code:java}
PackageDescr packageDescr = DescrFactory.newPackage().name("example")
.newImport().target("java.math.BigDecimal").end()
.newRule().name("Test Rule")
.lhs()
.accumulate()
.source().pattern().type("example.RuleTest.Fact").id("$target", false)
.end()
.end()
.function("count", "$cnt", false)
// adding the following constraint can avoid from KieBase build error
// .constraint("true")
.end()
.end()
.rhs("System.out.println($cnt);")
.end()
.end().getDescr();
String drl = new DrlDumper().dump(packageDescr);
{code}
This dumps the following DRL.
{code:java}
package example
import java.math.BigDecimal
rule "Test Rule"
when
accumulate(
$target : example.RuleTest.Fact( ) ,
$cnt : count( ) ;
)
then
System.out.println($cnt);
end
{code}
KieBase build with above drl fails with the following error.
{noformat}
2020-12-02 15:05:47,875 ERROR [org.drools.compiler.kie.builder.impl.KieProject] (main) Unable to build KieBaseModel:defaultKieBase
[10,9]: [ERR 101] Line 10:9 no viable alternative at input ')' in rule "Test Rule"
[0,0]: Parser returned a null Package
{noformat}
Adding constraint like comment line in above code can avoid from build error.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (WFLY-14151) Introduce a base "metrics" subsystem and move microprofile-health to the microprofile feature-pack
by Jeff Mesnil (Jira)
Jeff Mesnil created WFLY-14151:
----------------------------------
Summary: Introduce a base "metrics" subsystem and move microprofile-health to the microprofile feature-pack
Key: WFLY-14151
URL: https://issues.redhat.com/browse/WFLY-14151
Project: WildFly
Issue Type: Feature Request
Components: MP Metrics
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Fix For: 22.0.0.Beta1
The microprofile-metrics-smallrye subsystem is provided by the wilfdfly galleon-pack.
However its logical inclusion is in the microprofile feature pack (org.wildfly:wildfly-mp-feature-pack-galleon-common) which provides features for MicroProfile.
We should move the subsystem (and extension) to this feature pack.
However, the base WildFly server is still expected to provide "base" metrics (for the WildFly management model and the JVM) that can be consumed out of the box.
I propose to introduce a simple "metrics" subsystem (without any external dependencies) that exposes the WildFly management model and the JVM (using JMX) to the /metrics endpoint (on the management port) with the Prometheus format.
The microprofile-metrics-smallrye subsystem will be refactored to "plug" in the same HTTP endpoint and overrides the base metrics endpoint and provide the full features of MicroProfile metrics (application metrics, JSON output, etc.)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (DROOLS-5669) DMN Decision Table Analysis integrated in Maven and Kogito
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5669?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5669:
-----------------------------------
Sprint: 2020 Week 40-42 (from Sep 28), 2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30) (was: 2020 Week 40-42 (from Sep 28), 2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9))
> DMN Decision Table Analysis integrated in Maven and Kogito
> ----------------------------------------------------------
>
> Key: DROOLS-5669
> URL: https://issues.redhat.com/browse/DROOLS-5669
> Project: Drools
> Issue Type: Story
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Priority: Major
>
> *Motivation*: currently DT (static) analysis is only available when editor is open
> *Goals*: perform DMN DT analysis during build time, so the user is not required to await when backend services are available, or even worse needed to open DMN files one by one and checking DT analysis manually per each file.
> *Impacts*: integration with kie-maven-plugin, Kogito codegen (which in turn is used by Kogito Quarkus extension AND Kogito maven plugin for SB)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months