[JBoss JIRA] (WFCORE-2483) There is missing CS integration with core management
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2483?page=com.atlassian.jira.plugi... ]
Kabir Khan updated WFCORE-2483:
-------------------------------
Fix Version/s: 3.0.0.Beta20
> There is missing CS integration with core management
> ----------------------------------------------------
>
> Key: WFCORE-2483
> URL: https://issues.jboss.org/browse/WFCORE-2483
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Hynek Švábek
> Assignee: ehsavoie Hugonnet
> Priority: Blocker
> Fix For: 3.0.0.Beta20
>
>
> Priority is BLOCKER because this issue blocks RFE verification https://issues.jboss.org/browse/EAP7-538
> There must be credential store integration with core management as is mentioned in requirements of RFE.
> *management/security-realm*
> *management/security-realm/authentication/truststore* keystore-password
> *management/security-realm/server-identity/ssl* key-password and keystore-password
> *management/security-realm/server-identity/secret*
> *management/security-realm/authentication/users*
> But *security-realm* is deprecated, these resources have this description:
> {code}
> The security-realm configuration is deprecated and may be removed or moved in future versions.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFCORE-2784) Host controller should allow passing jvm parameters to servers
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2784?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-2784:
------------------------------------------
The server vm config needs to come via the <jvm> element; we don't want it being controlled by the HC VM settings, as the server can be running a completely different JDK from the HC. And trying to intelligently mix the two sounds like a bug nest.
But being clever about ignoring stuff that we know won't work makes sense if we can. I forget how the permgen/metaspace stuff worked (i.e. how the HC knew the server's VM version) but it seems like it must have since it's the same kind of problem.
> Host controller should allow passing jvm parameters to servers
> --------------------------------------------------------------
>
> Key: WFCORE-2784
> URL: https://issues.jboss.org/browse/WFCORE-2784
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Tomaz Cerar
> Assignee: Brian Stansberry
>
> It should be possible passing jvm options from host controller to servers runing in it.
> One such example is passing -ea to servers if passed to host controller
> other example is passing JDK9 specific parameters trough
> idea of implementation https://github.com/wildfly/wildfly-core/pull/2394/commits/d824be5c6d973e4...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFCORE-2785) The HttpDeploymentUploadUnitTestCase needs to be rewritten to use the Apache HttpClient
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2785?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-2785:
---------------------------------------
That's a good point. I've modified the description to inform that it's a good reference point.
> The HttpDeploymentUploadUnitTestCase needs to be rewritten to use the Apache HttpClient
> ---------------------------------------------------------------------------------------
>
> Key: WFCORE-2785
> URL: https://issues.jboss.org/browse/WFCORE-2785
> Project: WildFly Core
> Issue Type: Task
> Components: Test Suite
> Reporter: James Perkins
> Assignee: Tomaz Cerar
>
> The {{org.jboss.as.test.integration.management.http.HttpDeploymentUploadUnitTestCase}} uses the {{java.net.Authenticator.setDefault()}} to set a default authenticator. This can cause issues with tests that run after this test. The authenticator would be used after when the expectation is for the authentication to fail. This test should be converted to use the Apache {{HttpClient}} or at a minimum avoid setting a default authenticator.
> It also doesn't look like the test cleans up the deployed content which it should. -Maybe the {{add-content}} request could just be moved to the {{HttpGenericOperationUnitTestCase}} which has some similar actions.- See the {{HttpGenericOperationUnitTestCase}} for an example of using the {{HttpClient}} for a similar test.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFCORE-2785) The HttpDeploymentUploadUnitTestCase needs to be rewritten to use the Apache HttpClient
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2785?page=com.atlassian.jira.plugi... ]
James Perkins updated WFCORE-2785:
----------------------------------
Description:
The {{org.jboss.as.test.integration.management.http.HttpDeploymentUploadUnitTestCase}} uses the {{java.net.Authenticator.setDefault()}} to set a default authenticator. This can cause issues with tests that run after this test. The authenticator would be used after when the expectation is for the authentication to fail. This test should be converted to use the Apache {{HttpClient}} or at a minimum avoid setting a default authenticator.
It also doesn't look like the test cleans up the deployed content which it should. -Maybe the {{add-content}} request could just be moved to the {{HttpGenericOperationUnitTestCase}} which has some similar actions.- See the {{HttpGenericOperationUnitTestCase}} for an example of using the {{HttpClient}} for a similar test.
was:
The {{org.jboss.as.test.integration.management.http.HttpDeploymentUploadUnitTestCase}} uses the {{java.net.Authenticator.setDefault()}} to set a default authenticator. This can cause issues with tests that run after this test. The authenticator would be used after when the expectation is for the authentication to fail. This test should be converted to use the Apache {{HttpClient}} or at a minimum avoid setting a default authenticator.
It also doesn't look like the test cleans up the deployed content which it should. Maybe the {{add-content}} request could just be moved to the {{HttpGenericOperationUnitTestCase}} which has some similar actions.
> The HttpDeploymentUploadUnitTestCase needs to be rewritten to use the Apache HttpClient
> ---------------------------------------------------------------------------------------
>
> Key: WFCORE-2785
> URL: https://issues.jboss.org/browse/WFCORE-2785
> Project: WildFly Core
> Issue Type: Task
> Components: Test Suite
> Reporter: James Perkins
> Assignee: Tomaz Cerar
>
> The {{org.jboss.as.test.integration.management.http.HttpDeploymentUploadUnitTestCase}} uses the {{java.net.Authenticator.setDefault()}} to set a default authenticator. This can cause issues with tests that run after this test. The authenticator would be used after when the expectation is for the authentication to fail. This test should be converted to use the Apache {{HttpClient}} or at a minimum avoid setting a default authenticator.
> It also doesn't look like the test cleans up the deployed content which it should. -Maybe the {{add-content}} request could just be moved to the {{HttpGenericOperationUnitTestCase}} which has some similar actions.- See the {{HttpGenericOperationUnitTestCase}} for an example of using the {{HttpClient}} for a similar test.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years