-
Notifications
You must be signed in to change notification settings - Fork 473
WIP: [WFCORE-7335] Block deployments if the security manager subsyste… #6498
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
mskacelik
wants to merge
1
commit into
wildfly:main
Choose a base branch
from
mskacelik:WFCORE-7335
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+14
−6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…m has invalid config and the security manager is enabled.
Core -> WildFly Preview Integration Build 14758 outcome was FAILURE using a merge of 4e3494a Failed tests
|
Core -> Full Integration Build 14951 outcome was FAILURE using a merge of 4e3494a Failed tests
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
/cc @darranl
issue: https://issues.redhat.com/browse/WFCORE-7335
This is only a draft PR to showcase a possible solution.
When
standalone.xml
security manager subsystem configuration is invalid, f.g:Upon WF instance startup, the
ExpressionResolverImpl.java
will log and throw an exception of typeOperationClientException
wildfly-core/controller/src/main/java/org/jboss/as/controller/ExpressionResolverImpl.java
Line 282 in 70bb2a1
OperationClientException
means that:This exception is then handled in the
AbstractOperationContext
:wildfly-core/controller/src/main/java/org/jboss/as/controller/AbstractOperationContext.java
Lines 1074 to 1084 in 70bb2a1
So here is the fundamental problem.
Possible Solution
I have come up with a solution by wrapping the
OperationClientException
of the expression resolver in theSecurityManagerSubsystemAdd
, which, from my understanding, is only executed during the start-up of WildFly (boot). This wrapped exception is not handled in theAbstractOperationContext
, making the WildFly startup fail due to the exception.So, in the current implementation with invalid configuration:
-secmgr
)-secmgr
=> logs the error, but the boot won't fail-secmgr
=> logs the error, but boot will fail--admin-only
mode => both CLI and booting (invalidXML
) won't fail (with or without-secmgr
)Note
--admin-only
mode behavior valid in this case?wildfly-core
repository or in thewildfly
(repository) integration tests.RuntimeException
, but maybe other exceptions would be suited better.