November 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2476) Improve security subsystem test coverage

by Kabir Khan (JIRA)

Kabir Khan created WFLY-2476: -------------------------------- Summary: Improve security subsystem test coverage Key: WFLY-2476 URL: https://issues.jboss.org/browse/WFLY-2476 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 8.0.0.Beta1 Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 8.0.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2476) Improve security subsystem test coverage

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2476?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2476: ----------------------------- Description: We should at least be testing expressions allowed > Improve security subsystem test coverage > ---------------------------------------- > > Key: WFLY-2476 > URL: https://issues.jboss.org/browse/WFLY-2476 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.CR1 > > > We should at least be testing expressions allowed -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1732) UNICAST/NAKACK: threads from the internal thread pool should not do work stealing

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1732?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1732: --------------------------- Fix Version/s: (was: 3.4.1) > UNICAST/NAKACK: threads from the internal thread pool should not do work stealing > --------------------------------------------------------------------------------- > > Key: JGRP-1732 > URL: https://issues.jboss.org/browse/JGRP-1732 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5 > > > In NAKACK\{2\} and UNICAST\{2,3\}, threads from all thread pools (regular, OOB and internal) add messages to the table, then grab as many (ordered) messages as possible from the table and pass them up. > This could lead to the case where an internal thread passes up regular or OOB messages, which might block. There's a (small) chance that this exhausts the internal thread pool. > Internal threads should therefore never block, and never steal work from other thread pools. > SOLUTION: > * An internal thread only adds the message to the table and passes it up if in order > * If the internal message is OOB, it is passed up and then the thread returns -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2471) jboss-as-infinispan_1_4.xsd differs between EAP and WildFly

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2471?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-2471: ---------------------------------------- Paul, yes that may also be the case - TBH that is why I kept the description vague in the issues I have raised today - some of the schema inconsistencies I have spotted could be a missed back port to EAP if EAP does actually support the changes. > jboss-as-infinispan_1_4.xsd differs between EAP and WildFly > ----------------------------------------------------------- > > Key: WFLY-2471 > URL: https://issues.jboss.org/browse/WFLY-2471 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Darran Lofthouse > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > The schema 'jboss-as-infinispan_1_4.xsd' is not in sync between EAP and WildFly. > For a given namespace there is supposed to be only one definition and that definition is frozen as soon as it reaches a Final release. > The following commit affected version 1.4 of the schema in WildFly but did not make it to the EAP version: - > https://github.com/wildfly/wildfly/commit/a9ed468bba498d55c2aa8008100f0f9... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBCOMMON-131) Setting cache timeout for JAAS under jboss-eap-6.1 does not work

by Artur Mioduszewski (JIRA)

[ https://issues.jboss.org/browse/JBCOMMON-131?page=com.atlassian.jira.plug... ] Artur Mioduszewski commented on JBCOMMON-131: --------------------------------------------- Solution for problem is below configuration setting in standalone.xml file: --------------------------------- ... <subsystem xmlns="urn:jboss:domain:infinispan:1.4"> <cache-container name="security" default-cache="auth-cache"> </cache-container> ... <security-domain name="myJaasDomain" cache-type="infinispan"> ... -------------------------------- > Setting cache timeout for JAAS under jboss-eap-6.1 does not work > ---------------------------------------------------------------- > > Key: JBCOMMON-131 > URL: https://issues.jboss.org/browse/JBCOMMON-131 > Project: JBoss Common > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: jboss-eap-6.1 > Reporter: Artur Mioduszewski > Assignee: Dimitris Andreadis > > When: cache-type="default" in security-domain configuration -> authentication works correctly. > When I have used below configuration in order to try to set cache timeout in JAAS -> JAAS authentication stops to work - I am not able to log in (on JBoss console there are not any errors) > <code> > ... > <security-domain name="myJaasDomain" cache-type="infinispan"> > <authentication> > <login-module code="Database" flag="required"> > <module-option name="dsJndiName" value="java:jboss/datasources/digital-signal-service-dev-ws-DS"/> > <module-option name="principalsQuery" value="SELECT l.PASSWORD FROM LOGIN l WHERE l.USERNAME=?"/> > <module-option name="rolesQuery" value="SELECT ar.NAME, 'Roles' FROM login l, login_access_group lg, access_group g, access_group_s_access_right ga, s_access_right ar WHERE l.username = ? AND l.id = lg.login_ID AND lg.groups_ID = g.id AND g.ID = ga.access_group_ID AND ga.accessRights_ID = ar.ID"/> > <module-option name="hashAlgorithm" value="MD5"/> > <module-option name="hashEncoding" value="base64"/> > <module-option name="unauthenticatedIdentity" value="guest"/> > </login-module> > </authentication> > </security-domain> > ... > <subsystem xmlns="urn:jboss:domain:infinispan:1.2" default-cache-container="web"> > <cache-container name="cluster" aliases="ha-partition" default-cache="default"> > <transport lock-timeout="60000"/> > <replicated-cache name="default" mode="SYNC" batching="true"> > <locking isolation="REPEATABLE_READ"/> > </replicated-cache> > </cache-container> > <cache-container name="web" aliases="standard-session-cache" default-cache="repl"> > <transport lock-timeout="60000"/> > <replicated-cache name="repl" mode="ASYNC" batching="true"> > <file-store/> > </replicated-cache> > <replicated-cache name="sso" mode="SYNC" batching="true"/> > <distributed-cache name="dist" mode="ASYNC" batching="true"> > <file-store/> > </distributed-cache> > </cache-container> > <cache-container name="ejb" aliases="sfsb sfsb-cache" default-cache="repl"> > <transport lock-timeout="60000"/> > <replicated-cache name="repl" mode="ASYNC" batching="true"> > <file-store/> > </replicated-cache> > <replicated-cache name="remote-connector-client-mappings" mode="SYNC" batching="true"/> > <distributed-cache name="dist" mode="ASYNC" batching="true"> > <file-store/> > </distributed-cache> > </cache-container> > <cache-container name="hibernate" default-cache="local-query"> > <transport lock-timeout="60000"/> > <local-cache name="local-query"> > <transaction mode="NONE"/> > <expiration max-idle="100000"/> > </local-cache> > <invalidation-cache name="entity" mode="SYNC"> > <transaction mode="NON_XA"/> > <expiration max-idle="100000"/> > </invalidation-cache> > <replicated-cache name="timestamps" mode="ASYNC"> > <transaction mode="NONE"/> > </replicated-cache> > </cache-container> > </subsystem> > ... > <code> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2471) jboss-as-infinispan_1_4.xsd differs between EAP and WildFly

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-2471?page=com.atlassian.jira.plugin.... ] Paul Ferraro edited comment on WFLY-2471 at 11/8/13 8:20 AM: ------------------------------------------------------------- As I recall (as the person who made the change), the change to the 1.4 schema was to fix a bug. Previously, the schema allowed an <invalidation-cache/> to contain a <state-transfer/> element. However, this is not allowed by either the parser or the model. So, really, assuming my recollection is correct, this fix should be backported to EAP 6. was (Author: pferraro): As I recall (as the person who made the change), the change to the 1.4 schema was to fix a bug. As I recall, previously, the schema allowed an <invalidation-cache/> to contain a <state-transfer/> element. However, this is not allowed by either the parser or the model. So, really, assuming my recollection is correct, this fix should be backported to EAP 6. > jboss-as-infinispan_1_4.xsd differs between EAP and WildFly > ----------------------------------------------------------- > > Key: WFLY-2471 > URL: https://issues.jboss.org/browse/WFLY-2471 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Darran Lofthouse > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > The schema 'jboss-as-infinispan_1_4.xsd' is not in sync between EAP and WildFly. > For a given namespace there is supposed to be only one definition and that definition is frozen as soon as it reaches a Final release. > The following commit affected version 1.4 of the schema in WildFly but did not make it to the EAP version: - > https://github.com/wildfly/wildfly/commit/a9ed468bba498d55c2aa8008100f0f9... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2471) jboss-as-infinispan_1_4.xsd differs between EAP and WildFly

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-2471?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-2471: ------------------------------------ As I recall (as the person who made the change), the change to the 1.4 schema was to fix a bug. As I recall, previously, the schema allowed an <invalidation-cache/> to contain a <state-transfer/> element. However, this is not allowed by either the parser or the model. So, really, assuming my recollection is correct, this fix should be backported to EAP 6. > jboss-as-infinispan_1_4.xsd differs between EAP and WildFly > ----------------------------------------------------------- > > Key: WFLY-2471 > URL: https://issues.jboss.org/browse/WFLY-2471 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Darran Lofthouse > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > The schema 'jboss-as-infinispan_1_4.xsd' is not in sync between EAP and WildFly. > For a given namespace there is supposed to be only one definition and that definition is frozen as soon as it reaches a Final release. > The following commit affected version 1.4 of the schema in WildFly but did not make it to the EAP version: - > https://github.com/wildfly/wildfly/commit/a9ed468bba498d55c2aa8008100f0f9... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2471) jboss-as-infinispan_1_4.xsd differs between EAP and WildFly

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2471?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-2471: ---------------------------------------- >From what I have seen so far, yes I believe this change should just not have been made to the 1.4 schema - the addition of the 1.5 schema which was subsequently renamed to 2.0 should have been sufficient. > jboss-as-infinispan_1_4.xsd differs between EAP and WildFly > ----------------------------------------------------------- > > Key: WFLY-2471 > URL: https://issues.jboss.org/browse/WFLY-2471 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Darran Lofthouse > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > The schema 'jboss-as-infinispan_1_4.xsd' is not in sync between EAP and WildFly. > For a given namespace there is supposed to be only one definition and that definition is frozen as soon as it reaches a Final release. > The following commit affected version 1.4 of the schema in WildFly but did not make it to the EAP version: - > https://github.com/wildfly/wildfly/commit/a9ed468bba498d55c2aa8008100f0f9... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2471) jboss-as-infinispan_1_4.xsd differs between EAP and WildFly

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2471?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-2471: -------------------------------------- The change is about cross-site replication which is not supported in EAP. So in other words this issue is that the schema version should have been bumped, right? > jboss-as-infinispan_1_4.xsd differs between EAP and WildFly > ----------------------------------------------------------- > > Key: WFLY-2471 > URL: https://issues.jboss.org/browse/WFLY-2471 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Darran Lofthouse > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > The schema 'jboss-as-infinispan_1_4.xsd' is not in sync between EAP and WildFly. > For a given namespace there is supposed to be only one definition and that definition is frozen as soon as it reaches a Final release. > The following commit affected version 1.4 of the schema in WildFly but did not make it to the EAP version: - > https://github.com/wildfly/wildfly/commit/a9ed468bba498d55c2aa8008100f0f9... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2475) Bad marshalling of identity-trust's module in security subsystem

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2475?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2475: ----------------------------- Summary: Bad marshalling of identity-trust's module in security subsystem (was: Bad marshalling of identity-trust's module) > Bad marshalling of identity-trust's module in security subsystem > ---------------------------------------------------------------- > > Key: WFLY-2475 > URL: https://issues.jboss.org/browse/WFLY-2475 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.CR1 > > > {code} > <identity-trust> > <trust-module name="acl" code="AclThingy" flag="required" module="test"> > <module-option name="d" value="r"/> > </trust-module> > </identity-trust> > {code} > becomes > {code} > <identity-trust> > <login-module name="acl" code="AclThingy" flag="required" module="test"> > <module-option name="d" value="r"/> > </login-module> > </identity-trust> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2013