[JBoss JIRA] (WFCORE-2025) CLI SSLContext Priority
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2025?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-2025:
-------------------------------------
Fix Version/s: 3.0.0.Alpha16
(was: 3.0.0.Alpha15)
> CLI SSLContext Priority
> -----------------------
>
> Key: WFCORE-2025
> URL: https://issues.jboss.org/browse/WFCORE-2025
> Project: WildFly Core
> Issue Type: Task
> Components: CLI, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 3.0.0.Alpha16
>
>
> We have three different places an SSLContext could come from for the CLI: -
> # CLI Configuration
> # AuthenticationClient Configuration
> # Default interactive SSLContext
> We need to ensure they are prioritised as above.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 11 months
[JBoss JIRA] (WFCORE-2068) HTTPSConnectionWithCLITestCase and HTTPSManagementInterfaceTestCase Failing Due To Native Protocol Issue
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2068?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-2068:
-------------------------------------
Fix Version/s: 3.0.0.Alpha16
(was: 3.0.0.Alpha15)
> HTTPSConnectionWithCLITestCase and HTTPSManagementInterfaceTestCase Failing Due To Native Protocol Issue
> --------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2068
> URL: https://issues.jboss.org/browse/WFCORE-2068
> Project: WildFly Core
> Issue Type: Bug
> Components: Remoting, Test Suite
> Reporter: Darran Lofthouse
> Assignee: Jean-Francois Denise
> Priority: Blocker
> Fix For: 3.0.0.Alpha16
>
>
> The listed test case is failing during clean up with the following error: -
> {noformat}
> java.io.IOException: java.io.IOException: WFLYPRT0054: Channel closed
> at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:166)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:135)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:59)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:80)
> {noformat}
> The stage of the test using HTTP Upgrade over a HTTPS connection appears to be working fine, the issue is with the native management interface used for test clean up.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 11 months
[JBoss JIRA] (WFCORE-2060) Support Elytron RoleMapper categories
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2060?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-2060:
-------------------------------------
Fix Version/s: 3.0.0.Alpha16
(was: 3.0.0.Alpha15)
> Support Elytron RoleMapper categories
> -------------------------------------
>
> Key: WFCORE-2060
> URL: https://issues.jboss.org/browse/WFCORE-2060
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 3.0.0.Alpha16
>
>
> (Support for this could be added later, just scheduling in current releases for now if we have time)
> The Elytron role mapping configuration can contain different mappers for different categories, this issue is to make use of categories for management role mapping.
> We need to decide if we use hard coded names, some naming convention which is part hard coded, part based on deployment or a fully configurable category.
> On the access=authorization resource this could simply be an optional String 'role-category' if we go for configured. Possibly a boolean to state if we fallback to the default RoleMapping on the domain.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 11 months