[JBoss JIRA] (DROOLS-5480) [DMN Designer] Show parameters list for Decision Services
by Guilherme Gomes (Jira)
Guilherme Gomes created DROOLS-5480:
---------------------------------------
Summary: [DMN Designer] Show parameters list for Decision Services
Key: DROOLS-5480
URL: https://issues.redhat.com/browse/DROOLS-5480
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Reporter: Guilherme Gomes
Assignee: Guilherme Gomes
Currently, users need to guess/check the XML to discover the order of parameters for Decision Services.
The DMN designer must show this list of parameters in the properties panel.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 2 months
[JBoss JIRA] (JGRP-2484) SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2484?page=com.atlassian.jira.plugin... ]
Bela Ban commented on JGRP-2484:
--------------------------------
ASYM_ENCRYPT_TestKeyExchange (and subclass)
> SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL
> -------------------------------------------------
>
> Key: JGRP-2484
> URL: https://issues.redhat.com/browse/JGRP-2484
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 5.0.0.Final
>
>
> WildFly OpenSSL provides a high-performance implementation of SSLContext.
> While SSL_KEY_EXCHANGE supports passing custom SSLContext instances through the programmatic API, this is not possible through the declarative API.
> It should be possible to detect the presence of WildFly OpenSSL on the classpath and use it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 2 months
[JBoss JIRA] (JGRP-2484) SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/JGRP-2484?page=com.atlassian.jira.plugin... ]
Tristan Tarrant commented on JGRP-2484:
---------------------------------------
Yes it seems random. Which test was this ?
> SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL
> -------------------------------------------------
>
> Key: JGRP-2484
> URL: https://issues.redhat.com/browse/JGRP-2484
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 5.0.0.Final
>
>
> WildFly OpenSSL provides a high-performance implementation of SSLContext.
> While SSL_KEY_EXCHANGE supports passing custom SSLContext instances through the programmatic API, this is not possible through the declarative API.
> It should be possible to detect the presence of WildFly OpenSSL on the classpath and use it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 2 months
[JBoss JIRA] (WFCORE-5028) CallbackHandler from CLI overriding discovered wildfly-config for authentication.
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFCORE-5028?page=com.atlassian.jira.plug... ]
Darran Lofthouse updated WFCORE-5028:
-------------------------------------
Git Pull Request: https://github.com/wildfly/wildfly-core/pull/4252, https://github.com/wildfly/wildfly-core/pull/4253 (was: https://github.com/wildfly/wildfly-core/pull/4252)
> CallbackHandler from CLI overriding discovered wildfly-config for authentication.
> ---------------------------------------------------------------------------------
>
> Key: WFCORE-5028
> URL: https://issues.redhat.com/browse/WFCORE-5028
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 12.0.2.Final, 13.0.0.Beta2
>
>
> WFCORE-4976 made an update to ProtocolConnectionUtils so that a supplied CallbackHandler takes priority - this works where a client is using ModelControllerClient.create() and passing in a CallbackHandler as we should take that as an indication that the caller wants control of authentication.
> However by fixing in ProtocolConnectionUtils it has also picked up the case where the CLI passes in the CallbackHandler - that case however should only use the CBH if the information can not be obtained from the AuthenticationConfiguration. This call does not come via ModelControllerClient but both paths meet at ProtocolConnectionUtils.
> Either the adjustment of the AuthenticationContext to give the CallbackHandler should happen in ModelControllerClient - or an additional boolean should be passed into ProtocolConnectionUtils to indicate if the CallbackHandler should be given priority. The latter may be a less invasive evolution of the fix prepared so far.
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 2 months