[JBoss JIRA] (WFLY-7742) CredentialStore resource name is case sensitive but CredentialStore alias is convert to lowercase.
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/WFLY-7742?page=com.atlassian.jira.plugin.... ]
Hynek Švábek reassigned WFLY-7742:
----------------------------------
Assignee: Peter Skopek (was: Darran Lofthouse)
> CredentialStore resource name is case sensitive but CredentialStore alias is convert to lowercase.
> --------------------------------------------------------------------------------------------------
>
> Key: WFLY-7742
> URL: https://issues.jboss.org/browse/WFLY-7742
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Hynek Švábek
> Assignee: Peter Skopek
>
> CredentialStore resource name is case sensitive but CredentialStore alias is convert to lowercase.
> *How to reproduce*
> {code}
> /subsystem=elytron/credential-store=csfile001:add(uri="cr-store://test/csfile001.jceks?store.password=pass123;create.storage=true")
> {code}
> {code}
> /subsystem=elytron/credential-store=csfile001/alias=csname001:add(secret-value=secValue123456)
> {code}
> {code}
> /subsystem=elytron/credential-store=csfile001/alias=csNAME001:add(secret-value=secValue987654)
> {code}
> In csfile001.jceks you can see only "csname001" entry.
> *What is the biggest problem for me is that you have a lot of CS Alias RESOURCES which reference to ONE entry and update value in CS.*
> *NOTE*
> https://docs.oracle.com/javase/8/docs/api/java/security/KeyStore.html
> {code}
> Whether aliases are case sensitive is implementation dependent. In order to avoid problems, it is recommended not to use aliases in a KeyStore that only differ in case.
> {code}
> *Suggestions for solution*
> * implement case sensitive (Our implementation looks ok, IMO there is another problem with it...)
> * add NOTE to documentation
> * something else
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFLY-7742) CredentialStore resource name is case sensitive but CredentialStore alias is convert to lowercase.
by Hynek Švábek (JIRA)
Hynek Švábek created WFLY-7742:
----------------------------------
Summary: CredentialStore resource name is case sensitive but CredentialStore alias is convert to lowercase.
Key: WFLY-7742
URL: https://issues.jboss.org/browse/WFLY-7742
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Hynek Švábek
Assignee: Darran Lofthouse
CredentialStore resource name is case sensitive but CredentialStore alias is convert to lowercase.
*How to reproduce*
{code}
/subsystem=elytron/credential-store=csfile001:add(uri="cr-store://test/csfile001.jceks?store.password=pass123;create.storage=true")
{code}
{code}
/subsystem=elytron/credential-store=csfile001/alias=csname001:add(secret-value=secValue123456)
{code}
{code}
/subsystem=elytron/credential-store=csfile001/alias=csNAME001:add(secret-value=secValue987654)
{code}
In csfile001.jceks you can see only "csname001" entry.
*What is the biggest problem for me is that you have a lot of CS Alias RESOURCES which reference to ONE entry and update value in CS.*
*NOTE*
https://docs.oracle.com/javase/8/docs/api/java/security/KeyStore.html
{code}
Whether aliases are case sensitive is implementation dependent. In order to avoid problems, it is recommended not to use aliases in a KeyStore that only differ in case.
{code}
*Suggestions for solution*
* implement case sensitive (Our implementation looks ok, IMO there is another problem with it...)
* add NOTE to documentation
* something else
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (DROOLS-1376) OOPath 2+ notifyModification() result only the 1st being effective
by Matteo Mortari (JIRA)
Matteo Mortari created DROOLS-1376:
--------------------------------------
Summary: OOPath 2+ notifyModification() result only the 1st being effective
Key: DROOLS-1376
URL: https://issues.jboss.org/browse/DROOLS-1376
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.0.0.Beta3
Reporter: Matteo Mortari
Assignee: Mario Fusco
Reproducible by adding in XPathTest:
{code:java}
@Test
public void testDoubleAdd() {
String drl =
"import org.drools.compiler.xpath.*;\n" +
"\n" +
"rule R2 when\n" +
" Group( $id: name, $p: /members{age >= 20} )\n" +
"then\n" +
" System.out.println( $id + \".\" + $p.getName() );\n" +
" insertLogical( $id + \".\" + $p.getName() );\n" +
"end\n";
KieSession ksession = new KieHelper().addContent( drl, ResourceType.DRL )
.build()
.newKieSession();
Group x = new Group("X");
Group y = new Group("Y");
ksession.insert( x );
ksession.insert( y );
ksession.fireAllRules();
assertFalse (factsCollection(ksession).contains("X.Ada"));
assertFalse (factsCollection(ksession).contains("X.Bea"));
assertFalse (factsCollection(ksession).contains("Y.Ada"));
assertFalse (factsCollection(ksession).contains("Y.Bea"));
Adult ada = new Adult("Ada", 20);
Adult bea = new Adult("Bea", 20);
x.addPerson(ada);
x.addPerson(bea);
y.addPerson(ada);
y.addPerson(bea);
ksession.fireAllRules();
assertTrue (factsCollection(ksession).contains("X.Ada"));
assertTrue (factsCollection(ksession).contains("X.Bea"));
assertTrue (factsCollection(ksession).contains("Y.Ada"));
assertTrue (factsCollection(ksession).contains("Y.Bea"));
x.removePerson(ada);
x.removePerson(bea);
y.removePerson(ada);
y.removePerson(bea);
ksession.fireAllRules();
assertFalse (factsCollection(ksession).contains("X.Ada"));
assertFalse (factsCollection(ksession).contains("X.Bea"));
assertFalse (factsCollection(ksession).contains("Y.Ada"));
assertFalse (factsCollection(ksession).contains("Y.Bea"));
}
@Test
public void testDoubleRemove() {
String drl =
"import org.drools.compiler.xpath.*;\n" +
"\n" +
"rule R2 when\n" +
" Group( $id: name, $p: /members{age >= 20} )\n" +
"then\n" +
" System.out.println( $id + \".\" + $p.getName() );\n" +
" insertLogical( $id + \".\" + $p.getName() );\n" +
"end\n";
KieSession ksession = new KieHelper().addContent( drl, ResourceType.DRL )
.build()
.newKieSession();
Adult ada = new Adult("Ada", 20);
Adult bea = new Adult("Bea", 20);
Group x = new Group("X");
Group y = new Group("Y");
x.addPerson(ada);
x.addPerson(bea);
y.addPerson(ada);
y.addPerson(bea);
ksession.insert( x );
ksession.insert( y );
ksession.fireAllRules();
assertTrue (factsCollection(ksession).contains("X.Ada"));
assertTrue (factsCollection(ksession).contains("X.Bea"));
assertTrue (factsCollection(ksession).contains("Y.Ada"));
assertTrue (factsCollection(ksession).contains("Y.Bea"));
x.removePerson(ada);
x.removePerson(bea);
y.removePerson(ada);
y.removePerson(bea);
ksession.fireAllRules();
assertFalse (factsCollection(ksession).contains("X.Ada"));
assertFalse (factsCollection(ksession).contains("X.Bea"));
assertFalse (factsCollection(ksession).contains("Y.Ada"));
assertFalse (factsCollection(ksession).contains("Y.Bea"));
}
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFLY-7741) JUnit Assumptions with assume are broken in arq testcase for @BeforeClass and @AfterClass
by Chao Wang (JIRA)
Chao Wang created WFLY-7741:
-------------------------------
Summary: JUnit Assumptions with assume are broken in arq testcase for @BeforeClass and @AfterClass
Key: WFLY-7741
URL: https://issues.jboss.org/browse/WFLY-7741
Project: WildFly
Issue Type: Bug
Components: Test Suite
Affects Versions: 10.1.0.Final
Reporter: Chao Wang
1. Write a simple unit test with JUnit assumptions in @BeforeClass and @AfterClass methods.
{code:java}
@RunWith(Arquillian.class)
public class ArqAssumeInBeforeClassTestCase {
@BeforeClass
public static void beforeClass() throws IOException, InterruptedException {
Assume.assumeTrue(false); // this should skip
}
@AfterClass
public static void afterClass() throws IOException {
Assume.assumeTrue(false); // this should skip
}
@Test
public void test() {
}
}
{code}
2. Inside wildfly/testsuite run command:
mvn clean install -Dts.noSmoke -Dts.basic -Dtest=ArqAssumeInBeforeClassTestCase (for example in basic ts)
3. You will see the AssumptionViolatedException from @BeforeClass and @AfterClass methods as:
{noformat}
T E S T S
-------------------------------------------------------
Running org.jboss.as.test.integration.deployment.structure.war.ArqAssumeInBeforeClassTestCase
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.006 sec <<< FAILURE! - in org.jboss.as.test.integration.deployment.structure.war.ArqAssumeInBeforeClassTestCase
org.jboss.as.test.integration.deployment.structure.war.ArqAssumeInBeforeClassTestCase Time elapsed: 0.005 sec <<< ERROR!
org.junit.AssumptionViolatedException: got: <false>, expected: is <true>
at org.junit.Assume.assumeThat(Assume.java:95)
at org.junit.Assume.assumeTrue(Assume.java:41)
at org.jboss.as.test.integration.deployment.structure.war.ArqAssumeInBeforeClassTestCase.beforeClass(ArqAssumeInBeforeClassTestCase.java:17)
org.jboss.as.test.integration.deployment.structure.war.ArqAssumeInBeforeClassTestCase Time elapsed: 0.006 sec <<< ERROR!
org.junit.AssumptionViolatedException: got: <false>, expected: is <true>
at org.junit.Assume.assumeThat(Assume.java:95)
at org.junit.Assume.assumeTrue(Assume.java:41)
at org.jboss.as.test.integration.deployment.structure.war.ArqAssumeInBeforeClassTestCase.afterClass(ArqAssumeInBeforeClassTestCase.java:22)
Results :
Tests in error:
org.jboss.as.test.integration.deployment.structure.war.ArqAssumeInBeforeClassTestCase.org.jboss.as.test.integration.deployment.structure.war.ArqAssumeInBeforeClassTestCase
Run 1: ArqAssumeInBeforeClassTestCase.beforeClass:17 » AssumptionViolated got: <false...
Run 2: ArqAssumeInBeforeClassTestCase.afterClass:22 » AssumptionViolated got: <false>...
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
{noformat}
However, the executions inside @BeforeClass and @AfterClass methods should simply be skipped.
Example test https://github.com/soul2zimate/wildfly/commits/ArqAssumeInBeforeClassTest...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (SECURITY-864) NameNotFoundException due to policyRegistration -- service jboss.naming.context.java.policyRegistration
by Philippe Marschall (JIRA)
[ https://issues.jboss.org/browse/SECURITY-864?page=com.atlassian.jira.plug... ]
Philippe Marschall commented on SECURITY-864:
---------------------------------------------
[~mletenay] how do you register during the initialization of JAAS LoginModule? We face the same issue but during the {{#initialize}} method of the LoginModule the JNDI context is read only.
> NameNotFoundException due to policyRegistration -- service jboss.naming.context.java.policyRegistration
> -------------------------------------------------------------------------------------------------------
>
> Key: SECURITY-864
> URL: https://issues.jboss.org/browse/SECURITY-864
> Project: PicketBox
> Issue Type: Bug
> Components: PicketBox
> Reporter: Chao Wang
> Assignee: Stefan Guilhen
>
> "NameNotFoundException due to policyRegistration -- service jboss.naming.context.java.policyRegistration" is recorded in server.log during quickstart example run by changing log level:
> {noformat}
> <logger category="org.jboss.as.security">
> <level name="TRACE"/>
> </logger>
> <logger category="org.jboss.security">
> <level name="TRACE"/>
> </logger>
> {noformat}
> See detailed description in community discussion [#907134|https://developer.jboss.org/message/907134]
> I choose Jira component picketbox since the exception is titled as "PBOX000293: Exception caught: javax.naming.NameNotFoundException"
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months