December 2009 - jboss-dev-forums - Jboss List Archives

[Security Development] - client authentication on a JRMP SSL connection; multiple key

by ovidiu.feodorov＠jboss.com

JBoss Security team, I would like to start a discussion concerning several possible improvements in jbosssx; they came up while working with JBoss in an environment that has complex security requirements. While all functionality I am suggesting was implemented with custom code, outside jbosssx, I believe it makes sense to generalize it, so other people can take advantage of it. The changes are related to supporting keystores containing multiple client and server key aliases at JBoss security domain configuration level, and also a way to declaratively enable client authentication at JBoss security domain configuration level, similarly to how client authentication is enabled for a Tomcat connector - I needed this in order to enable client authentication on a secure JRMP connection. Please let me know if this is a good place to start the discussion. For simplicity, I could split the thread in several sub-threads, one per each suggested functionality. In the end, if it is decided that the improvements are worth the trouble, I will create the JIRA issues and provide patches and tests. However, I would like to start the discussion here, first, because it is possible that the suggested functionality already exists, and I just simply missed it. The discussion applies to 4.x series, but I will be more than happy to adapt the patches for 5.x and 6.x, if deemed appropriate. Thanks, Ovidiu View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269670#4269670 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269670

16 years, 1 month

1
0
0 / 0

[JBoss Build System Development] - Re: NPE in maven-buildmagic-thirdparty-plugin

by pgier

Created a Jira issue to track this. https://jira.jboss.org/jira/browse/JBBUILD-582 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269666#4269666 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269666

16 years, 1 month

1
0
0 / 0

[JBoss ESB Development] - Re: Performance Improvement Prop: Cache PortReference.extend

by dward

Committed to https://svn.jboss.org/repos/labs/labs/jbossesb/workspace/performance/perf2 workspace: revision 30552. Merged and Committed to https://svn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_7_CP branch: revision 30553. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269661#4269661 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269661

16 years, 1 month

1
0
0 / 0

[EJB 3.0 Development] - Re: EJB3 project integration in AS

by wolfc

For AS 6 we should beef up the ejb3 module in AS itself as the integration module. as-int will be left behind as an deprecated artifact. Consumers should be refactored off it and consume ejb3 directly. Originally jboss-ejb3 was meant to define the EJB 3.0 profile for Profile Service. I don't see that happening any time soon, so create an jboss-ejb3_1 for the EJB 3.1 definition in similar vain. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269660#4269660 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269660

16 years, 1 month

1
0
0 / 0

[EJB 3.0 Development] - Re: ejb3-deployers-jboss-beans.xml core

by wolfc

The META-INF/*beans.xml files are only picked up when these are under deploy or deployers, not from lib. Some components have and can do a standalone bean installation and these should contain a beans descriptor that those so. For the overall there should be one beans descriptor (in AS integration module) that does the complete configuration of integration components (especially if we need components that are outside ejb3 land). For backwards compatibility we only need to make sure that the complete ejb3 distribution is as such, not individual components. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269657#4269657 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269657

16 years, 1 month

1
0
0 / 0

[JBoss ESB Development] - Re: Performance Improvement Proposal: Cache result of HttpSe

by dward

Committed to https://svn.jboss.org/repos/labs/labs/jbossesb/workspace/performance/perf2 workspace: revision 30550. Merged and Committed to https://svn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_7_CP branch: revision 30551. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269656#4269656 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269656

16 years, 1 month

1
0
0 / 0

[EJB 3.0 Development] - Re: ejb3-deployers-jboss-beans.xml core

by jaikiran

That's actually a good point. I remember Scott/Bill too had similar thoughts about such files. I'll have to do some testing to see if the AS/MC picks up these files if they are in the jars and if it requires such jars to be present in some specific locations (i have a feeling that it will ignore these files if the jars are in common/lib). However, the other side of this is - how does it affect the support team? They probably won't be able to provide quick workarounds/fixes in these files. And even extracting, then fixing the file and then adding back the file to the jar, isn't an option too when the jars are signed. Should we be thinking about this, probably the right way to fix/workaround the problem is rebuild the jar completely? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269650#4269650 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269650

16 years, 1 month

1
0
0 / 0

[EJB 3.0 Development] - Re: ejb3-deployers-jboss-beans.xml core

by ALRubinger

We're currently (well, everyone is ;) ) using one or two jboss-beans.xml files as a dumping grounds for all internal configs. It'd be great to split these up, per component, and hide them into a JAR assembly such that the user doesn't think they're for them to configure. So jar -tvf ejb3-deployers.jar: /META-INF/jboss-deployers-jboss-beans.xml | /org/jboss/ejb3/otherClasses Then when ejb3-deployers.jar is dropped in, it installs the necessary components into MC. Likewise each component is a "drop-in" installation. S, ALR View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269646#4269646 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269646

16 years, 1 month

1
0
0 / 0

[EJB 3.0 Development] - ejb3-deployers-jboss-beans.xml core

by jaikiran

While working on some of the integration points for ejb3-nointerface component, i noticed that the ejb3-deployers-jboss-beans.xml in "core" has MC beans from across various other components (like ejb3-deployers) on which "core" never even depends (not even transitively). For example, we have the: | <bean name="Ejb3MetadataProcessingDeployer" | class="org.jboss.ejb3.deployers.Ejb3MetadataProcessingDeployer" /> The org.jboss.ejb3.deployers.Ejb3MetadataProcessingDeployer comes in from the ejb3-deployers component on which core has no dependency. I am planning to move that bean definition out to a ejb3-blah-what-do-we-call-this-jboss-beans.xml in the ejb3-deployers component. This way, it will be more tied to the ejb3-deployers component and any changes to the bean internals, in a new version can be managed within this components. Any thoughts around this? Although it doesn't directly affect backward compatibility (i.e. we still ship this bean, although in a new file and a different component) is there anything else that i should be concerned about while moving this? P.S: This is just one example. There are many other MC bean configs in that file which probably need to be moved to their own components. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269645#4269645 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269645

16 years, 1 month

1
0
0 / 0

[EJB 3.0 Development] - Re: EJB3 project integration in AS

by ALRubinger

The initial idea was that "ejb3" would assemble all EJB3 components together, then "as-int" would combine what was needed in some particular target AS integration environment. As it stands these are not quite aligned. If we were to really do it this way, there's be separate integration targets like "as-int-as5" and "as-int-as6", etc. But thinking more on it, seems this integration is much better suited to be done in the integrataion layer itself: AS. So I think it's fine to merge everything together into one ("ejb3"), probably kill "as-int", then tack anything else a particular AS target needs into the AS build. ie. you're got the right idea with 3). S, ALR View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269644#4269644 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269644

16 years, 1 month

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-dev-forums December 2009