October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7305) Getting identity by DN in Elytron ldap-realm should be case insensitive

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFLY-7305: ---------------------------------- Summary: Getting identity by DN in Elytron ldap-realm should be case insensitive Key: WFLY-7305 URL: https://issues.jboss.org/browse/WFLY-7305 Project: WildFly Issue Type: Bug Components: Security Reporter: Ondrej Lukas Assignee: Darran Lofthouse Elytron ldap-realm allows to use DN as username (e.g. full {{uid=jduke,ou=People,dc=jboss,dc=org}} can be used instead of {{jduke}}). However implementation requires that used DN must start with rdn-identifier in the same case sensitivity as is used in server configuration. Otherwise authentication fails. It means when server configuration uses {{rdn-identifier=uid}} then only {{uid=jduke,...}} can be correctly used, {{UID=jduke,...}} will fail. LDAP specification does not talk about case sensitivity of attributes, but most of LDAP servers work with attributes as case insensitive. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7305) Getting identity by DN in Elytron ldap-realm should be case insensitive

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7305?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-7305: ------------------------------- Affects Version/s: 11.0.0.Alpha1 > Getting identity by DN in Elytron ldap-realm should be case insensitive > ----------------------------------------------------------------------- > > Key: WFLY-7305 > URL: https://issues.jboss.org/browse/WFLY-7305 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > > Elytron ldap-realm allows to use DN as username (e.g. full {{uid=jduke,ou=People,dc=jboss,dc=org}} can be used instead of {{jduke}}). However implementation requires that used DN must start with rdn-identifier in the same case sensitivity as is used in server configuration. Otherwise authentication fails. It means when server configuration uses {{rdn-identifier=uid}} then only {{uid=jduke,...}} can be correctly used, {{UID=jduke,...}} will fail. > LDAP specification does not talk about case sensitivity of attributes, but most of LDAP servers work with attributes as case insensitive. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7304) Compensations subsystem

by Jive JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-7304?page=com.atlassian.jira.plugin.... ] Jive JIRA Integration updated WFLY-7304: ---------------------------------------- Forum Reference: https://developer.jboss.org/message/963125#963125 > Compensations subsystem > ----------------------- > > Key: WFLY-7304 > URL: https://issues.jboss.org/browse/WFLY-7304 > Project: WildFly > Issue Type: Task > Components: Transactions > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 11.0.0.Alpha1 > > > Currently compensations bootstrap happens in the transactions subsystem. It registers deployment processor to scan the annotations and add the dependencies if necessary. This is not expensive and doesn't cause any issues other than adding the dependencies to the transactions subsystem. However, I'm currently finishing off the recovery implementation and more bootstrap logic will be needed. In addition, two more recovery modules will have to be registered: one for the participant (a new one) and one for the coordinator (from XTS). This will require to add XTS dependency too. > The whole compensations bootstrapping will not need a lot of code. However, I'm thinking maybe it would be good to pull it out to the separate subsystem in order to maintain the separation of concerns. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7304) Compensations subsystem

by Gytis Trikleris (JIRA)

Gytis Trikleris created WFLY-7304: ------------------------------------- Summary: Compensations subsystem Key: WFLY-7304 URL: https://issues.jboss.org/browse/WFLY-7304 Project: WildFly Issue Type: Task Components: Transactions Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Minor Fix For: 11.0.0.Alpha1 Currently compensations bootstrap happens in the transactions subsystem. It registers deployment processor to scan the annotations and add the dependencies if necessary. This is not expensive and doesn't cause any issues other than adding the dependencies to the transactions subsystem. However, I'm currently finishing off the recovery implementation and more bootstrap logic will be needed. In addition, two more recovery modules will have to be registered: one for the participant (a new one) and one for the coordinator (from XTS). This will require to add XTS dependency too. The whole compensations bootstrapping will not need a lot of code. However, I'm thinking maybe it would be good to pull it out to the separate subsystem in order to maintain the separation of concerns. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7303) Unignore tests in org.jboss.as.test.integration.ejb.mdb.MDBTestCase and org.jboss.as.test.integration.ejb.mdb.deliveryactive.MDBTestCase

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7303?page=com.atlassian.jira.plugin.... ] Farah Juma updated WFLY-7303: ----------------------------- Description: When tests in {{org.jboss.as.test.integration.ejb.mdb.MDBTestCase}} and {{org.jboss.as.test.integration.ejb.mdb.deliveryactive.MDBTestCase}} fail, the tests that get run after these ones fail as well. These tests in MDBTestCases will be fixed during Phase III Remoting 5 integration but temporarily ignoring them for now to try to get the CI job in better shape. (was: When tests in {{org.jboss.as.test.integration.ejb.mdb.MDBTestCase}} and {{org.jboss.as.test.integration.ejb.mdb.deliveryactive.MDBTestCase}}, the tests that get run after these ones fail as well. These tests in MDBTestCases will be fixed during Phase III Remoting 5 integration but temporarily ignoring them for now to try to get the CI job in better shape.) > Unignore tests in org.jboss.as.test.integration.ejb.mdb.MDBTestCase and org.jboss.as.test.integration.ejb.mdb.deliveryactive.MDBTestCase > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7303 > URL: https://issues.jboss.org/browse/WFLY-7303 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Farah Juma > Assignee: Farah Juma > Labels: affects_elytron > > When tests in {{org.jboss.as.test.integration.ejb.mdb.MDBTestCase}} and {{org.jboss.as.test.integration.ejb.mdb.deliveryactive.MDBTestCase}} fail, the tests that get run after these ones fail as well. These tests in MDBTestCases will be fixed during Phase III Remoting 5 integration but temporarily ignoring them for now to try to get the CI job in better shape. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7303) Unignore tests in org.jboss.as.test.integration.ejb.mdb.MDBTestCase and org.jboss.as.test.integration.ejb.mdb.deliveryactive.MDBTestCase

by Farah Juma (JIRA)

Farah Juma created WFLY-7303: -------------------------------- Summary: Unignore tests in org.jboss.as.test.integration.ejb.mdb.MDBTestCase and org.jboss.as.test.integration.ejb.mdb.deliveryactive.MDBTestCase Key: WFLY-7303 URL: https://issues.jboss.org/browse/WFLY-7303 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Farah Juma Assignee: Farah Juma When tests in {{org.jboss.as.test.integration.ejb.mdb.MDBTestCase}} and {{org.jboss.as.test.integration.ejb.mdb.deliveryactive.MDBTestCase}}, the tests that get run after these ones fail as well. These tests in MDBTestCases will be fixed during Phase III Remoting 5 integration but temporarily ignoring them for now to try to get the CI job in better shape. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1864) Whitespaces are not removed from dependencies in module add command

by Bartosz Spyrko-Śmietanko (JIRA)

Bartosz Spyrko-Śmietanko created WFCORE-1864: ------------------------------------------------ Summary: Whitespaces are not removed from dependencies in module add command Key: WFCORE-1864 URL: https://issues.jboss.org/browse/WFCORE-1864 Project: WildFly Core Issue Type: Bug Components: CLI Affects Versions: 3.0.0.Alpha9 Reporter: Bartosz Spyrko-Śmietanko Assignee: Bartosz Spyrko-Śmietanko Running {{module add --name=foo.bar --resources=foo.jar --dependencies=[org.a, org.b ]}} will result in following dependencies in module.xml {{ ... <dependencies> <module name="org.a"/> <module name=" org.b "/> </dependencies> ... }} The module name in dependencies should be stripped of leading and trailing whitespaces. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5839) Create "Best practice" document for writing tests

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-5839?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda commented on WFLY-5839: ----------------------------------------- Enhanced syntax slide on https://drive.google.com/file/d/0B1UdSRDDWsroLW52TngyMEpkVTA/view is nice too. > Create "Best practice" document for writing tests > ------------------------------------------------- > > Key: WFLY-5839 > URL: https://issues.jboss.org/browse/WFLY-5839 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Rostislav Svoboda > Assignee: Tomaz Cerar > Fix For: No Release > > > Please create "Best practice" document for writing tests > In AS TS there are currently multiple solutions for the same thing, ARQ is used where WF deployer would be sufficient, tests are not exactly in the correct location - they can be even in WF Core TS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1326) Stateful working memory regression OCT-2016: nurserostering long_hint01.xml

by Jiri Locker (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1326?page=com.atlassian.jira.plugi... ] Jiri Locker updated DROOLS-1326: -------------------------------- Summary: Stateful working memory regression OCT-2016: nurserostering long_hint01.xml (was: Statefull working memory regression OCT-2016: nurserostering long_hint01.xml) > Stateful working memory regression OCT-2016: nurserostering long_hint01.xml > --------------------------------------------------------------------------- > > Key: DROOLS-1326 > URL: https://issues.jboss.org/browse/DROOLS-1326 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta2 > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Priority: Blocker > > Something regressed in Drools master between 27-SEP and 11-OCT. > See: > https://kie-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/optaplanner-turtl... > I 'll ask [~jlocker] to isolate. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5839) Create "Best practice" document for writing tests

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-5839?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda resolved WFLY-5839. ------------------------------------- Fix Version/s: No Release Resolution: Done > Create "Best practice" document for writing tests > ------------------------------------------------- > > Key: WFLY-5839 > URL: https://issues.jboss.org/browse/WFLY-5839 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Rostislav Svoboda > Assignee: Tomaz Cerar > Fix For: No Release > > > Please create "Best practice" document for writing tests > In AS TS there are currently multiple solutions for the same thing, ARQ is used where WF deployer would be sufficient, tests are not exactly in the correct location - they can be even in WF Core TS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2016