[JBoss JIRA] (WFCORE-2832) JBoss CLI run with IBM JDK is not able to use secure connection when server uses Elytron ssl-context
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2832?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise moved WFLY-8800 to WFCORE-2832:
----------------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-2832 (was: WFLY-8800)
Component/s: CLI
Security
(was: CLI)
(was: Security)
> JBoss CLI run with IBM JDK is not able to use secure connection when server uses Elytron ssl-context
> ----------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2832
> URL: https://issues.jboss.org/browse/WFCORE-2832
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Security
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Blocker
>
> In case SSL through Elytron ssl-context is configured for management interface then JBoss CLI is not able to authenticate when it is run with IBM JDK.
> It works correctly when
> * Legacy SSL is used instead of Elytron ssl-context
> * or non-IBM JDK is used for JBoss CLI
> * or only authentication without SSL is used
> It fails for http-interface as well as native-interface.
> When different client is used for connection to management interface (I tried it with ModelControllerClient) then authentication and SSL works correctly.
> For http-interface following output of CLI is print:
> {code}
> Failed to connect to the controller: The controller is not available at localhost:9993: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+https://localhost:9993. The connection failed: WFLYPRT0053: Could not connect to remote+https://localhost:9993. The connection failed: java.nio.channels.ClosedChannelException
> {code}
> For native-interface following output of CLI is print:
> {code}
> Failed to connect to the controller: Unable to negotiate SSL connection with controller at localhost:9999
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2831) Remove deprecated ManagementResourceRegistration.Factory methods
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-2831:
----------------------------------------
Summary: Remove deprecated ManagementResourceRegistration.Factory methods
Key: WFCORE-2831
URL: https://issues.jboss.org/browse/WFCORE-2831
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
The ManagementResourceRegistration.Factory is meant to be created with a ProcessType, but some legacy, deprecated, unused code does not require this. Remove those methods. They were deprecated 2 years ago and this Factory is not meant for use outside the kernel anyway.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-1029) Support clients that provide an optional CallbackHandler
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-1029?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated ELY-1029:
----------------------------------
Fix Version/s: 1.1.0.Beta45
(was: 1.1.0.Beta44)
> Support clients that provide an optional CallbackHandler
> --------------------------------------------------------
>
> Key: ELY-1029
> URL: https://issues.jboss.org/browse/ELY-1029
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Authentication Client
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 1.1.0.Beta45
>
>
> Clients such as the WildFly CLI provide a CallbackHandler implementation in case it is needed and not as a sign that it must be used, i.e. the desired outcome is that if the information required can be obtained from the configuration then authentication proceeds without interaction with the end user.
> Neither the CLI or the end user should be required to be fully aware of the underlying security configuration.
> This is similar to web browser HTTP authentication where there is only an interaction with the user if actually required.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month