[JBoss JIRA] (WFCORE-3447) CLI SSL security commands.
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3447?page=com.atlassian.jira.plugi... ]
James Perkins updated WFCORE-3447:
----------------------------------
Fix Version/s: 4.0.0.Beta1
> CLI SSL security commands.
> --------------------------
>
> Key: WFCORE-3447
> URL: https://issues.jboss.org/browse/WFCORE-3447
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI
> Reporter: Jean-Francois Denise
> Assignee: Jean-Francois Denise
> Fix For: 4.0.0.Beta1
>
>
> In order to help configure SSL server side security, a set of CLI commands should be defined to drive users to realise the main use cases:
> - enable / disable SSL for management interfaces
> - enable / disable SSL for web server.
> These commands rely on the new elytron operations to manage key-store.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9757) Some jsf integration tests fail if -Dnode != localhost
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/WFLY-9757?page=com.atlassian.jira.plugin.... ]
Farah Juma commented on WFLY-9757:
----------------------------------
{{DoctypeDeclTestCase#testDoctypeDeclDisallowed}} currently attempts to check that the HTTP response contains a specific error message from the stack trace when attempting to access a JSF application that contains a DOCTYPE declaration. However, when WildFly is bound to an IP address other than localhost, attempting to access a JSF application that contains a DOCTYPE declaration will result in an Internal Server Error, as expected, but the stack trace containing the error message won't be part of the HTTP response as it is when WildFly is bound to localhost. The test should be updated to just make sure an Internal Server Error occurs instead of also checking that the response string contains the error message from the stack trace.
> Some jsf integration tests fail if -Dnode != localhost
> ------------------------------------------------------
>
> Key: WFLY-9757
> URL: https://issues.jboss.org/browse/WFLY-9757
> Project: WildFly
> Issue Type: Bug
> Components: JSF, Test Suite
> Reporter: Petr Kremensky
> Assignee: Farah Juma
> Attachments: org.jboss.as.test.integration.jsf.doctype.DoctypeDeclTestCase-output.txt
>
>
> Running the tests keeping a node0 to localhost works fine:
> {noformat}
> [pkremens@localhost testsuite] (master)$ mvn test -Dts.basic -Dts.noSmoke -Dtest=DoctypeDeclTestCase,DuplicateIDIntegrationTestCase,InjectionToPhaseListenerTest
> ...
> Running org.jboss.as.test.integration.jsf.doctype.DoctypeDeclTestCase
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.809 sec - in org.jboss.as.test.integration.jsf.doctype.DoctypeDeclTestCase
> Running org.jboss.as.test.integration.jsf.duplicateid.DuplicateIDIntegrationTestCase
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.645 sec - in org.jboss.as.test.integration.jsf.duplicateid.DuplicateIDIntegrationTestCase
> Running org.jboss.as.test.integration.jsf.phaseListener.injectionTarget.InjectionToPhaseListenerTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.1 sec - in org.jboss.as.test.integration.jsf.phaseListener.injectionTarget.InjectionToPhaseListenerTest
> {noformat}
> But once node0 is set, the tests start to fail.
> {noformat}
> [pkremens@localhost testsuite] (master)$ mvn test -Dts.basic -Dts.noSmoke -Dtest=DoctypeDeclTestCase,DuplicateIDIntegrationTestCase,InjectionToPhaseListenerTest -Dnode0=<IP>
> ...
> Failed tests:
> DoctypeDeclTestCase.testDoctypeDeclDisallowed:93
> DuplicateIDIntegrationTestCase.testDuplicateIDIsNotGenerated:107 expected:<200> but was:<500>
> Tests in error:
> InjectionToPhaseListenerTest.test:61 » IO java.util.concurrent.ExecutionExcept...
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-5459) Rename JGroups-related attributes
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-5459?page=com.atlassian.jira.plugin.... ]
Paul Ferraro reassigned WFLY-5459:
----------------------------------
Assignee: Paul Ferraro (was: Jeff Mesnil)
> Rename JGroups-related attributes
> ---------------------------------
>
> Key: WFLY-5459
> URL: https://issues.jboss.org/browse/WFLY-5459
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.CR2
> Reporter: Jeff Mesnil
> Assignee: Paul Ferraro
>
> Based on Paul feedback in https://github.com/wildfly/wildfly/pull/8221#issuecomment-145013596:
> {quote}You may want to consider renaming these attributes, however, since the names are now a little confusing. For example, jgroups-stack is perhaps better described as jgroups-channel-factory, since it can specify either a stack name or a channel name. jgroups-channel is also confusing in this context, since this specifies either the cluster name, in the case where jgroups-stack specifies a stack; or the fork name, in the case where the jgroups-stack specifies a channel name. Perhaps jgroups-cluster-name is a better choice?{quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months