-
Notifications
You must be signed in to change notification settings - Fork 469
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
[WFCORE-5101] [Community] SSLContext to support delegation to alternate instances based on peer information. #4311
Conversation
Core - Full Integration Build 9882 outcome was FAILURE using a merge of 9609837 |
Core - Full Integration Build 9930 outcome was FAILURE using a merge of 9609837 |
ServiceTarget serviceTarget = context.getServiceTarget(); | ||
ServiceBuilder<AuthenticationContext> serviceBuilder = | ||
(ServiceBuilder<AuthenticationContext>)context.getCapabilityServiceTarget().addCapability(AUTHENTICATION_CONTEXT_RUNTIME_CAPABILITY); | ||
TrivialService<AuthenticationContext> certificateAuthorityTrivialService = new TrivialService<AuthenticationContext>(getValueSupplier(serviceBuilder, context, model)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very minor but looks like certificateAuthorityTrivialService
should be renamed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed. Thanks!
Core - Full Integration Build 10039 outcome was FAILURE using a merge of b66a3da |
Core - Full Integration Build 10006 outcome was FAILURE using a merge of b66a3da |
Core - Full Integration Build 10040 outcome was FAILURE using a merge of 5bf06d7 |
Core - Full Integration Build 10007 outcome was FAILURE using a merge of 5bf06d7 |
There has been no activity on this PR for 30 days. It will be auto-closed after 90 days. |
this PR is out of sync with the main branch. |
Converted to draft whilst awaiting pre-check |
Core - Full Integration Build 10467 outcome was FAILURE using a merge of c3bfb6d |
Core - Full Integration Build 10532 outcome was FAILURE using a merge of c3bfb6d |
Core - Full Integration Build 10469 outcome was FAILURE using a merge of 553a1c1 |
Core -> WildFly Preview Integration Build 13445 outcome was FAILURE using a merge of f30aca3 |
Core -> Full Integration Build 13638 outcome was FAILURE using a merge of f30aca3 |
Core -> Full Integration Build 13389 outcome was FAILURE using a merge of f30aca3 |
…ldFly Elytron model and schema
Core -> Full Integration Build 13390 outcome was FAILURE using a merge of e562b79 |
Core -> WildFly Preview Integration Build 13446 outcome was FAILURE using a merge of e562b79 |
Core -> Full Integration Build 13639 outcome was FAILURE using a merge of e562b79 |
Core -> WildFly Preview Integration Build 13447 outcome was FAILURE using a merge of 78b28b7 |
Core -> Full Integration Build 13391 outcome was FAILURE using a merge of 78b28b7 |
Core -> Full Integration Build 13640 outcome was FAILURE using a merge of 78b28b7 |
@fjuma it sounds like the main piece missing here is finishing off the skipping provisioning when not at the community stability level - I think we can move that to a Blocker issue WFCORE / ELY to address before WildFly 32 Final |
@@ -170,6 +170,8 @@ private static void from18(ChainedTransformationDescriptionBuilder chainedBuilde | |||
.setDiscard(DiscardAttributeChecker.UNDEFINED, EMIT_EVENTS) | |||
.addRejectCheck(new RejectAttributeChecker.SimpleRejectAttributeChecker(ModelNode.TRUE), IGNORE_UNAVAILABLE_REALMS) | |||
.addRejectCheck(RejectAttributeChecker.DEFINED, EMIT_EVENTS); | |||
builder.rejectChildResource(PathElement.pathElement(ElytronDescriptionConstants.DYNAMIC_CLIENT_SSL_CONTEXTS)); | |||
builder.rejectChildResource(PathElement.pathElement(ElytronDescriptionConstants.DYNAMIC_CLIENT_SSL_CONTEXT)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can add a follow up commit to not block this PR but @pferraro from something you said elsewhere, are we missing a subsystem model bump?
I think you said a change to any resource at any stability level should trigger a bump so we probably need this bumping to 19 so the transformer should then be when transforming from19
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can add a follow up commit to not block this PR but @pferraro from something you said elsewhere, are we missing a subsystem model bump?
Yes - this requires a model version bump.
Modifying an existing transformer for a version that was already released will cause regressions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Created a blocker issue, WFCORE-6756, for this.
elytron/src/test/java/org/wildfly/extension/elytron/TestEnvironment.java
Outdated
Show resolved
Hide resolved
…te instancesbased on peer information.
…xt to avoid dependency on unsupported module
Core -> WildFly Preview Integration Build 13453 outcome was FAILURE using a merge of 8cabe0b |
Core -> Full Integration Build 13646 outcome was FAILURE using a merge of 8cabe0b |
Core -> Full Integration Build 13397 outcome was FAILURE using a merge of 8cabe0b |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding my approval on this one since I've created WFCORE issues to track the remaining items. The created issues have also been linked from WFCORE-5101.
/retest |
https://issues.redhat.com/browse/WFCORE-5101
Requires: https://issues.redhat.com/browse/ELY-1996 which has PR here: wildfly-security/wildfly-elytron#1382