[JBoss JIRA] (WFLY-8333) Print info message with JGroups version during the EAP startup
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8333?page=com.atlassian.jira.plugin.... ]
Radoslav Husar moved JBEAP-9480 to WFLY-8333:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8333 (was: JBEAP-9480)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Clustering
(was: Clustering)
Affects Version/s: (was: 7.1.0.DR13)
> Print info message with JGroups version during the EAP startup
> --------------------------------------------------------------
>
> Key: WFLY-8333
> URL: https://issues.jboss.org/browse/WFLY-8333
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
>
> Right now, no INFO message with JGroups version is logged during EAP startup, which makes difficult to recognize what JGroups version is currently used.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFCORE-1859) Investigate and fix JDK9 modular params propagation to forked processes
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1859?page=com.atlassian.jira.plugi... ]
Richard Opalka reopened WFCORE-1859:
------------------------------------
No true - there are still tests that are failing if modular JVM args are not propagated to forked processed. I resuscitated the following branch for verification: https://github.com/ropalka/wildfly-core/commits/JDK9
If I exclude the last proposal commit: https://github.com/ropalka/wildfly-core/commit/5d3f4c1f24796b0bfe78d5368e...
then problematic tests are:
{code}
wildfly-core/testsuite/domain$>
org.jboss.as.test.integration.domain.SimpleDomainControllerMigrationTestCase
org.jboss.as.test.integration.domain.ProductInfoUnitTestCase
org.jboss.as.test.integration.domain.SlaveSynchronizationTestCase
org.jboss.as.test.integration.domain.slavereconnect.SlaveReconnectTestCase
org.jboss.as.test.integration.domain.autoignore.AutoIgnoredResourcesDomainTestCase
org.jboss.as.test.integration.domain.suites.FullRbacProviderRunAsTestSuite
org.jboss.as.test.integration.domain.suites.FullRbacProviderTestSuite
org.jboss.as.test.integration.domain.suites.SimpleRbacProviderTestSuite
org.jboss.as.test.integration.domain.suites.CLITestSuite
org.jboss.as.test.integration.domain.suites.FullRbacProviderPropertiesRoleMappingTestSuite
org.jboss.as.test.integration.domain.suites.DomainTestSuite
org.jboss.as.test.integration.domain.OperationTimeoutTestCase
org.jboss.as.test.integration.domain.ServerManagementTestCase
org.jboss.as.test.integration.domain.DefaultInterfaceOveridingDomainTestCase
org.jboss.as.test.integration.domain.AdminOnlyModeTestCase
org.jboss.as.test.integration.domain.events.ProcessStateListenerTestCase
org.jboss.as.test.integration.domain.events.JmxControlledStateNotificationsTestCase
org.jboss.as.test.integration.domain.LegacyConfigurationChangesTestCase
org.jboss.as.test.integration.domain.AdminOnlyPolicyTestCase
org.jboss.as.test.integration.domain.ConfigurationChangesTestCase
org.jboss.as.test.integration.domain.suspendresume.DomainGracefulShutdownTestCase
org.jboss.as.test.integration.domain.suspendresume.DomainSuspendResumeTestCase
org.jboss.as.test.integration.domain.ReloadWithConfigTestCase
org.jboss.as.test.integration.domain.DomainControllerMigrationTestCase
org.jboss.as.test.integration.respawn.RespawnHttpTestCase
Tests run: 29, Failures: 0, Errors: 25, Skipped: 4
{code}
> Investigate and fix JDK9 modular params propagation to forked processes
> -----------------------------------------------------------------------
>
> Key: WFCORE-1859
> URL: https://issues.jboss.org/browse/WFCORE-1859
> Project: WildFly Core
> Issue Type: Sub-task
> Components: Server, Test Suite
> Reporter: Richard Opalka
> Assignee: Tomaz Cerar
> Priority: Blocker
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8329) cannot set await-initial-transfer attribute in infinispan configuration
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8329?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-8329:
---------------------------------
Issue Type: Feature Request (was: Bug)
> cannot set await-initial-transfer attribute in infinispan configuration
> -----------------------------------------------------------------------
>
> Key: WFLY-8329
> URL: https://issues.jboss.org/browse/WFLY-8329
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: 10.1.0.Final
> Reporter: Daniele Pirola
> Assignee: Paul Ferraro
>
> Inside wildfly infinispan configuration I can't set attribute {{await-initial-transfer}} even if it's present in Infinispan 8.2.4.Final (see {{org.infinispan.configuration.cache.StateTransferConfiguration}}).
> This is the subsystem that doesn't work:
> {{<subsystem xmlns="urn:jboss:domain:infinispan:4.0">
> <cache-container XXX >
> <distributed-cache XXX >
> ...
> <state-transfer await-initial-transfer="true" />
> </distributed-cache>}}
> There is a workaround to set this attribute at runtime?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFCORE-2455) Empty secret-value is not allowed in credential stores
by Josef Cacek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2455?page=com.atlassian.jira.plugi... ]
Josef Cacek updated WFCORE-2455:
--------------------------------
Description:
It's not possible to add an entry with empty secret-value into a credential store.
Masking the fact the password is empty is a valid scenario.
{code}
[standalone@localhost:9990 /] /subsystem=elytron/credential-store=cred-store-default/alias=emptysecret:add()
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0155: 'secret-value' may not be null",
"rolled-back" => true
}
[standalone@localhost:9990 /] /subsystem=elytron/credential-store=cred-store-default/alias=emptysecret:add(secret-value="")
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0113: '' is an invalid value for parameter secret-value. Values must have a minimum length of 1 characters",
"rolled-back" => true
}
{code}
*Unignore tests*
When this issue is fixed, unignore (and fix if needed) related tests in {{testsuite/elytron/src/test/java/org/wildfly/test/integration/elytron/application/}}. Thanks.
{code}
git grep WFLY-8143
{code}
was:
It's not possible to add an entry with empty secret-value into a credential store.
Masking the fact the password is empty is a valid scenario.
{code}
[standalone@localhost:9990 /] /subsystem=elytron/credential-store=cred-store-default/alias=emptysecret:add()
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0155: 'secret-value' may not be null",
"rolled-back" => true
}
[standalone@localhost:9990 /] /subsystem=elytron/credential-store=cred-store-default/alias=emptysecret:add(secret-value="")
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0113: '' is an invalid value for parameter secret-value. Values must have a minimum length of 1 characters",
"rolled-back" => true
}
{code}
> Empty secret-value is not allowed in credential stores
> -------------------------------------------------------
>
> Key: WFCORE-2455
> URL: https://issues.jboss.org/browse/WFCORE-2455
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Josef Cacek
> Assignee: Darran Lofthouse
> Priority: Critical
> Labels: credential-store
>
> It's not possible to add an entry with empty secret-value into a credential store.
> Masking the fact the password is empty is a valid scenario.
> {code}
> [standalone@localhost:9990 /] /subsystem=elytron/credential-store=cred-store-default/alias=emptysecret:add()
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0155: 'secret-value' may not be null",
> "rolled-back" => true
> }
> [standalone@localhost:9990 /] /subsystem=elytron/credential-store=cred-store-default/alias=emptysecret:add(secret-value="")
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0113: '' is an invalid value for parameter secret-value. Values must have a minimum length of 1 characters",
> "rolled-back" => true
> }
> {code}
> *Unignore tests*
> When this issue is fixed, unignore (and fix if needed) related tests in {{testsuite/elytron/src/test/java/org/wildfly/test/integration/elytron/application/}}. Thanks.
> {code}
> git grep WFLY-8143
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFCORE-2399) Removing and re-adding alias to credential store leads to Duplicate resource failure
by Josef Cacek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2399?page=com.atlassian.jira.plugi... ]
Josef Cacek updated WFCORE-2399:
--------------------------------
Description:
When an alias is removed from a credential store and added once more, the {{add}} operation fails with Duplicate resource message.
*Unignore tests*
When this issue is fixed, unignore (and fix if needed) related tests in {{testsuite/elytron/src/test/java/org/wildfly/test/integration/elytron/application/}}. Thanks.
{code}
git grep WFLY-8144
{code}
was:When an alias is removed from a credential store and added once more, the {{add}} operation fails with Duplicate resource message.
> Removing and re-adding alias to credential store leads to Duplicate resource failure
> ------------------------------------------------------------------------------------
>
> Key: WFCORE-2399
> URL: https://issues.jboss.org/browse/WFCORE-2399
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Josef Cacek
> Assignee: Darran Lofthouse
> Priority: Critical
> Labels: credential-store
>
> When an alias is removed from a credential store and added once more, the {{add}} operation fails with Duplicate resource message.
> *Unignore tests*
> When this issue is fixed, unignore (and fix if needed) related tests in {{testsuite/elytron/src/test/java/org/wildfly/test/integration/elytron/application/}}. Thanks.
> {code}
> git grep WFLY-8144
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFCORE-2517) Coverity, Dereference after null check (Elytron subsystem)
by Martin Choma (JIRA)
Martin Choma created WFCORE-2517:
------------------------------------
Summary: Coverity, Dereference after null check (Elytron subsystem)
Key: WFCORE-2517
URL: https://issues.jboss.org/browse/WFCORE-2517
Project: WildFly Core
Issue Type: Bug
Components: Security
Reporter: Martin Choma
Assignee: Darran Lofthouse
Coverity found possible dereference of null. In this code {{defaultPolicy}} is checked for null and in next step {{defaultPolicy.equals()}} is called.
https://scan7.coverity.com/reports.htm#v23632/p12663/fileInstanceId=10578...
{code:java|title=PolicyParser.java}
boolean providerFound = defaultPolicy == null;
while (reader.hasNext() && reader.nextTag() != END_ELEMENT) {
verifyNamespace(reader);
String localName = reader.getLocalName();
switch (localName) {
// Permission Mapper
case JACC_POLICY:
providerFound = defaultPolicy.equals(parseJaccPolicy(addPolicy, reader, operations)) || providerFound;
break;
case CUSTOM_POLICY:
providerFound = defaultPolicy.equals(parseCustomPolicy(addPolicy, reader, operations)) || providerFound;
break;
default:
throw unexpectedElement(reader);
}
}
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (ELY-997) Elytron form authentication does not store POST data
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-997?page=com.atlassian.jira.plugin.sy... ]
Jan Kalina updated ELY-997:
---------------------------
Fix Version/s: 1.1.0.Beta29
> Elytron form authentication does not store POST data
> ----------------------------------------------------
>
> Key: ELY-997
> URL: https://issues.jboss.org/browse/ELY-997
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Mechanisms
> Affects Versions: 1.1.0.Beta28
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Blocker
> Labels: authentication, eap71_alpha, form, http, servlet
> Fix For: 1.1.0.Beta29
>
>
> Form authentication backed by Elytron in the web applications uses status code 303 (See Other) to redirect user after processing /j_security_check.
> We see two serious issues here:
> * Legacy security uses status code 302 (Moved Temporarily/Found) to handle this redirect and existing applications/clients may behave differently for these different codes. (e.g. default behavior of Apache HTTP client is to follow redirect for 303, but not to follow for 302)
> * The 303 status code was introduced in HTTP 1.1 so it's not part of HTTP 1.0, but the 303 is returned also for HTTP/1.0 request as a HTTP/1.0 response, which is wrong.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months