[JBoss JIRA] (WFLY-6803) Add multi-server support to mod_cluster
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6803?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-6803:
---------------------------------
Fix Version/s: 14.0.0.CR1
> Add multi-server support to mod_cluster
> ---------------------------------------
>
> Key: WFLY-6803
> URL: https://issues.jboss.org/browse/WFLY-6803
> Project: WildFly
> Issue Type: Feature Request
> Components: mod_cluster
> Affects Versions: 10.0.0.Final, 11.0.0.Final, 12.0.0.Final, 13.0.0.Final
> Reporter: Paul Ferraro
> Assignee: Radoslav Husar
> Fix For: 14.0.0.CR1
>
>
> Currently, mod_cluster subsystem supports only a single configuration, which references the default undertow server. However, Undertow supports multiple servers, and exposes a distinct route capability per server (see WFLY-6778). mod_cluster should therefore support multiple "profiles", where each profile references a specific undertow server.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 10 months
[JBoss JIRA] (ELY-1584) Add ability to log security manager violations to out-of-band log file
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-1584?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse commented on ELY-1584:
---------------------------------------
Slightly related to this I think there have been things attempted in the past for the security manager to log in a format that could be fed back into a security policy allowing a user to run their app and identify the permissions is needed.
> Add ability to log security manager violations to out-of-band log file
> ----------------------------------------------------------------------
>
> Key: ELY-1584
> URL: https://issues.jboss.org/browse/ELY-1584
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Security Manager
> Reporter: David Lloyd
>
> It would be useful for CI if we could set a system property which would log security manager permission check violations (and the details thereof) to a log file, outside of the standard log infrastructure. This would potentially allow us to fail CI when unexpected "hidden" permission violations occur by way of a post-build script analyzes the log output.
> This might also be useful for troubleshooting more obscure security manager related problems.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 10 months
[JBoss JIRA] (ELY-1584) Add ability to log security manager violations to out-of-band log file
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-1584?page=com.atlassian.jira.plugin.s... ]
Jan Kalina commented on ELY-1584:
---------------------------------
[~dmlloyd] what exactly mean "outside of the standard log infrastructure" ?
We already have DEBUG messages in *org.wildfly.security.access*:
{code}
17:15:03,705 DEBUG (main) [org.wildfly.security.access] <WildFlySecurityManager.java:226> Permission check failed (permission "("java.io.FilePermission" "/home/jkalina/work/wildfly-elytron/target/test-classes/org/junit/runner/notification/RunNotifier$7.class" "read")" in code source "(file:/home/jkalina/work/wildfly-elytron/target/classes/ <no signer certificates>)" of "sun.misc.Launcher$AppClassLoader@18b4aac2")
{code}
jboss logger allows to redirect it into standalone log file - is not it sufficient?
> Add ability to log security manager violations to out-of-band log file
> ----------------------------------------------------------------------
>
> Key: ELY-1584
> URL: https://issues.jboss.org/browse/ELY-1584
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Security Manager
> Reporter: David Lloyd
>
> It would be useful for CI if we could set a system property which would log security manager permission check violations (and the details thereof) to a log file, outside of the standard log infrastructure. This would potentially allow us to fail CI when unexpected "hidden" permission violations occur by way of a post-build script analyzes the log output.
> This might also be useful for troubleshooting more obscure security manager related problems.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 10 months