September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-531) KieServices.Factory.get().getKieClasspathContainer() doesn't discover KieModules in a non-Maven project

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-531?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-531: ------------------------------------------------ Marek Winkler <mwinkler(a)redhat.com> changed the Status of [bug 1117114|https://bugzilla.redhat.com/show_bug.cgi?id=1117114] from ON_QA to VERIFIED > KieServices.Factory.get().getKieClasspathContainer() doesn't discover KieModules in a non-Maven project > ------------------------------------------------------------------------------------------------------- > > Key: DROOLS-531 > URL: https://issues.jboss.org/browse/DROOLS-531 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.CR1 > Reporter: Michael Anstis > Assignee: Mario Fusco > Labels: backport-to-6.0.x > Fix For: 6.1.0.Final > > > If you try to use a ClassPath Container KieContainerImpl uses a ClasspathKieProject that scans the classpath for pom.xml or pom.properties files. If the consuming project is not a Maven project (and hence lacks either a pom.xml or pom.properties file) no KBases/KSessions defined in the consuming project's kmodule.xml and /resources folder are discovered. > This also manifests as a problem when running Maven WebApp projects in IDEA (other IDE's and project types may be similarly affected). IDEA copies the JARs sources and resources to the target folder at runtime; which excludes the module's pom.xml and pom.properties files. > Consequentially ClasspathKieProject fails to determine a ReleaseId for any KieModules defined in the module and hence fails to discover any KBases/KSessions too. > See https://github.com/ederign/uf-social-activities/blob/master/uberfire-soci... where we try to use a named KSession. > This is defined in https://github.com/ederign/uf-social-activities/blob/master/uberfire-soci... > Rules being in https://github.com/ederign/uf-social-activities/tree/master/uberfire-soci... > Workaround is to include a dummy pom.properties; as we did here https://github.com/ederign/uf-social-activities/blob/master/uberfire-soci... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1067) Integrate JGroups with core AS security infrastructure

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/WFLY-1067?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz edited comment on WFLY-1067 at 9/29/14 11:44 AM: --------------------------------------------------------------------- At the clustering meeting last week, given that there are now three possible security protocol layers (AUTH, ENCRYPT, SASL), we proposed introducing a new child-type: {noformat} <stack name="udp"> <transport type="UDP" socket-binding="jgroups-udp"/> <protocol type="PING"/> <protocol type="MERGE3"/> <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/> <protocol type="FD_ALL"/> <protocol type="VERIFY_SUSPECT"/> <protocol type="pbcast.NAKACK2"/> <protocol type="UNICAST3"/> <protocol type="pbcast.STABLE"/> <security-protocol type="AUTH" mech="DIGEST" realm="JGroupsRealm"/> <security-protocol type="ENCRYPT" mech="Client-CERT" realm="JGroupsRealm"/> <protocol type="pbcast.GMS"/> <protocol type="UFC"/> <protocol type="MFC"/> <protocol type="FRAG2"/> <protocol type="RSVP"/> </stack> {noformat} If there were further configuration required for any security protocol which was not made available via the realm, this could be provided as properties as usual. In the case of providing a secret key to TP for probe, a realm attribute could be added to the transport child to handle that case. was (Author: rachmato): At the clustering meeting last week, given that there are now three possible security protocol layers, we proposed introducing a new child-type: {noformat} <stack name="udp"> <transport type="UDP" socket-binding="jgroups-udp"/> <protocol type="PING"/> <protocol type="MERGE3"/> <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/> <protocol type="FD_ALL"/> <protocol type="VERIFY_SUSPECT"/> <protocol type="pbcast.NAKACK2"/> <protocol type="UNICAST3"/> <protocol type="pbcast.STABLE"/> <security-protocol type="AUTH" mech="DIGEST" realm="JGroupsRealm"/> <security-protocol type="ENCRYPT" mech="Client-CERT" realm="JGroupsRealm"/> <protocol type="pbcast.GMS"/> <protocol type="UFC"/> <protocol type="MFC"/> <protocol type="FRAG2"/> <protocol type="RSVP"/> </stack> {noformat} In the case of providing a secret key to TP for probe, a realm attribute could be added to the transport child to handle that case. If there were further configuration required for any security protocol which was not made available via the realm, this could be provided as properties as usual. > Integrate JGroups with core AS security infrastructure > ------------------------------------------------------ > > Key: WFLY-1067 > URL: https://issues.jboss.org/browse/WFLY-1067 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Security > Reporter: Brian Stansberry > Assignee: Richard Achmatowicz > > Container task for better integrating JGroups security with overall AS security. The basic concept is the various security aware aspects of JGroups will expose an SPI, and the AS can create implementations of those SPIs that integrate with the AS security realms. The AS JGroups subsystem will inject the implementation into the JGroups runtime components. > Subtasks are for the various aspects. These can be done separately but a common overall design should be created to ensure a consistent approach is taken. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1067) Integrate JGroups with core AS security infrastructure

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/WFLY-1067?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz commented on WFLY-1067: ------------------------------------------- It's also worth mentioning that there are certain authentication mechanisms which appear in JGroups and have no counterpart in the idea of realms. For example, authentication based on IP membership lists (you have to be in the list to be able to join) or regular expression constraints on IP addresses (your IP address has to match the regexp to be able to join). Not sure what the approach would be here: forgo the realm and just specify properties, or extend the realm to cater to the new configuration data. > Integrate JGroups with core AS security infrastructure > ------------------------------------------------------ > > Key: WFLY-1067 > URL: https://issues.jboss.org/browse/WFLY-1067 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Security > Reporter: Brian Stansberry > Assignee: Richard Achmatowicz > > Container task for better integrating JGroups security with overall AS security. The basic concept is the various security aware aspects of JGroups will expose an SPI, and the AS can create implementations of those SPIs that integrate with the AS security realms. The AS JGroups subsystem will inject the implementation into the JGroups runtime components. > Subtasks are for the various aspects. These can be done separately but a common overall design should be created to ensure a consistent approach is taken. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1067) Integrate JGroups with core AS security infrastructure

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/WFLY-1067?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz commented on WFLY-1067: ------------------------------------------- At the clustering meeting last week, given that there are now three possible security protocol layers, we proposed introducing a new child-type: {noformat} <stack name="udp"> <transport type="UDP" socket-binding="jgroups-udp"/> <protocol type="PING"/> <protocol type="MERGE3"/> <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/> <protocol type="FD_ALL"/> <protocol type="VERIFY_SUSPECT"/> <protocol type="pbcast.NAKACK2"/> <protocol type="UNICAST3"/> <protocol type="pbcast.STABLE"/> <security-protocol type="AUTH" mech="DIGEST" realm="JGroupsRealm"/> <security-protocol type="ENCRYPT" mech="Client-CERT" realm="JGroupsRealm"/> <protocol type="pbcast.GMS"/> <protocol type="UFC"/> <protocol type="MFC"/> <protocol type="FRAG2"/> <protocol type="RSVP"/> </stack> {noformat} In the case of providing a secret key to TP for probe, a realm attribute could be added to the transport child to handle that case. If there were further configuration required for any security protocol which was not made available via the realm, this could be provided as properties as usual. > Integrate JGroups with core AS security infrastructure > ------------------------------------------------------ > > Key: WFLY-1067 > URL: https://issues.jboss.org/browse/WFLY-1067 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Security > Reporter: Brian Stansberry > Assignee: Richard Achmatowicz > > Container task for better integrating JGroups security with overall AS security. The basic concept is the various security aware aspects of JGroups will expose an SPI, and the AS can create implementations of those SPIs that integrate with the AS security realms. The AS JGroups subsystem will inject the implementation into the JGroups runtime components. > Subtasks are for the various aspects. These can be done separately but a common overall design should be created to ensure a consistent approach is taken. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1067) Integrate JGroups with core AS security infrastructure

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/WFLY-1067?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz commented on WFLY-1067: ------------------------------------------- I'll mention first that since this issue was created, a. SASL protocol layer for JGroups was written (JGRP-1729). However, unlike it's point-to-point version, this SASL layer does not currently support Quality of Protection features of SASL (JGRP-1883). So there is no possibility to deprecate AUTH and ENCRYPT in favour of SASL, at the moment. > Integrate JGroups with core AS security infrastructure > ------------------------------------------------------ > > Key: WFLY-1067 > URL: https://issues.jboss.org/browse/WFLY-1067 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Security > Reporter: Brian Stansberry > Assignee: Richard Achmatowicz > > Container task for better integrating JGroups security with overall AS security. The basic concept is the various security aware aspects of JGroups will expose an SPI, and the AS can create implementations of those SPIs that integrate with the AS security realms. The AS JGroups subsystem will inject the implementation into the JGroups runtime components. > Subtasks are for the various aspects. These can be done separately but a common overall design should be created to ensure a consistent approach is taken. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1203) Integrate JGroups ENCRYPT with AS security infrastructure

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/WFLY-1203?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz reassigned WFLY-1203: ----------------------------------------- Assignee: Richard Achmatowicz (was: Paul Ferraro) > Integrate JGroups ENCRYPT with AS security infrastructure > --------------------------------------------------------- > > Key: WFLY-1203 > URL: https://issues.jboss.org/browse/WFLY-1203 > Project: WildFly > Issue Type: Sub-task > Components: Clustering, Security > Reporter: Brian Stansberry > Assignee: Richard Achmatowicz > > Integrate JGroups ENCRYPT (or some similar protocol) with the AS security infrastructure, such that redundant configuration of keystore information is avoided. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1201) Integrate JGroups diagnostics with AS security

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/WFLY-1201?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz reassigned WFLY-1201: ----------------------------------------- Assignee: Richard Achmatowicz (was: Paul Ferraro) > Integrate JGroups diagnostics with AS security > ---------------------------------------------- > > Key: WFLY-1201 > URL: https://issues.jboss.org/browse/WFLY-1201 > Project: WildFly > Issue Type: Sub-task > Components: Clustering, Security > Reporter: Brian Stansberry > Assignee: Richard Achmatowicz > > Integrate JGroups diagnostics with AS security, such that probe.sh users can provide credentials allowing them to authenticate against the AS security realm used for securing other management interfaces. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1202) Integrate JGroups AUTH with AS security infrastructure

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/WFLY-1202?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz reassigned WFLY-1202: ----------------------------------------- Assignee: Richard Achmatowicz (was: Paul Ferraro) > Integrate JGroups AUTH with AS security infrastructure > ------------------------------------------------------ > > Key: WFLY-1202 > URL: https://issues.jboss.org/browse/WFLY-1202 > Project: WildFly > Issue Type: Sub-task > Components: Clustering, Security > Reporter: Brian Stansberry > Assignee: Richard Achmatowicz > > Integrate JGroups AUTH (or some similar protocol) with the AS security realm infrastructure, such that the credentials needed for a peer to authenticate can come from the realm and be verified by the realm. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1067) Integrate JGroups with core AS security infrastructure

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/WFLY-1067?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz reassigned WFLY-1067: ----------------------------------------- Assignee: Richard Achmatowicz (was: Paul Ferraro) > Integrate JGroups with core AS security infrastructure > ------------------------------------------------------ > > Key: WFLY-1067 > URL: https://issues.jboss.org/browse/WFLY-1067 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Security > Reporter: Brian Stansberry > Assignee: Richard Achmatowicz > > Container task for better integrating JGroups security with overall AS security. The basic concept is the various security aware aspects of JGroups will expose an SPI, and the AS can create implementations of those SPIs that integrate with the AS security realms. The AS JGroups subsystem will inject the implementation into the JGroups runtime components. > Subtasks are for the various aspects. These can be done separately but a common overall design should be created to ensure a consistent approach is taken. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1223) IronJacamar 1.0.28.Final

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1223?page=com.atlassian.jira.plugin... ] Jesper Pedersen closed JBJCA-1223. ---------------------------------- > IronJacamar 1.0.28.Final > ------------------------ > > Key: JBJCA-1223 > URL: https://issues.jboss.org/browse/JBJCA-1223 > Project: IronJacamar > Issue Type: Release > Components: Build > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.28.Final > > > Release notes: https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310691&versi... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2014