[JBoss JIRA] (WFCORE-4482) Out of the box SSL with Wildfly Elytron
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFCORE-4482?page=com.atlassian.jira.plugi... ]
Jeff Mesnil updated WFCORE-4482:
--------------------------------
Fix Version/s: 11.0.0.Beta5
(was: 11.0.0.Beta4)
> Out of the box SSL with Wildfly Elytron
> ---------------------------------------
>
> Key: WFCORE-4482
> URL: https://issues.jboss.org/browse/WFCORE-4482
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Reporter: Farah Juma
> Assignee: Farah Juma
> Priority: Major
> Labels: EAP-CD19
> Fix For: 11.0.0.Beta5
>
>
> The details of this RFE will be explored within the analysis, presently Undertow depends on a security-realm that generates a self signed cert on start up so we will require an Elytron equivalent.
> There may be opportunities to tie this in in some way with the new CA integration support but that can be explored in the analysis.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFCORE-3376) Modules may create loggers on a deployments log context
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFCORE-3376?page=com.atlassian.jira.plugi... ]
Jeff Mesnil updated WFCORE-3376:
--------------------------------
Fix Version/s: 11.0.0.Beta5
(was: 11.0.0.Beta4)
> Modules may create loggers on a deployments log context
> -------------------------------------------------------
>
> Key: WFCORE-3376
> URL: https://issues.jboss.org/browse/WFCORE-3376
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Critical
> Fix For: 11.0.0.Beta5
>
>
> Currently WildFly uses a {{ClassLoaderLogContextSelector}} to determine the log context to use when creating loggers. If a deployment has it's own log context, via logging-profile or per-deployment logging, and a dependency on a module, that module may create loggers on the deployments log context. This is due to the fact the the call stack is walked until it finds a log context associated with a class loader.
> What is needed is a way to short-circuit once a non-logging API class loader is found and determine if there is an associated log context with the callers class loader.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFCORE-4486) Support for multiple security realms - Failover
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFCORE-4486?page=com.atlassian.jira.plugi... ]
Jeff Mesnil updated WFCORE-4486:
--------------------------------
Fix Version/s: 11.0.0.Beta5
(was: 11.0.0.Beta4)
> Support for multiple security realms - Failover
> -----------------------------------------------
>
> Key: WFCORE-4486
> URL: https://issues.jboss.org/browse/WFCORE-4486
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Reporter: Farah Juma
> Assignee: Martin Mazanek
> Priority: Major
> Labels: CD17-Deferred, EAP-CD19
> Fix For: 11.0.0.Beta5
>
>
> Our security realms are able to indicate unavailability by throwing a RealmUnavailableException
> We should support fail over to an alternative realm.
> A common request is fail over to a local file based realm if an LDAP or database server has gone down allowing administrators to retain access to the server.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFCORE-4766) Add additional logging to ManagementInterfaceAddStepHandler.LenientVerifyInstallationStep
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFCORE-4766?page=com.atlassian.jira.plugi... ]
Jeff Mesnil updated WFCORE-4766:
--------------------------------
Fix Version/s: 11.0.0.Beta5
(was: 11.0.0.Beta4)
> Add additional logging to ManagementInterfaceAddStepHandler.LenientVerifyInstallationStep
> -----------------------------------------------------------------------------------------
>
> Key: WFCORE-4766
> URL: https://issues.jboss.org/browse/WFCORE-4766
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 11.0.0.Beta3
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 11.0.0.Beta5
>
>
> Debugging a recent issue the class org.jboss.as.controller.management.ManagementInterfaceAddStepHandler.LenientVerifyInstallationStep was detecting missing services but was not logging anything despite this class making the decision to abort the start up of the server.
> If a handler is going to make such a terminal decision it should be logging why it is doing it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months