January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-629) Create a new LoginModule to handle the server authentication

by Darran Lofthouse (Created) (JIRA)

Create a new LoginModule to handle the server authentication ------------------------------------------------------------ Key: SECURITY-629 URL: https://issues.jboss.org/browse/SECURITY-629 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.3.SP4 If we supply a module of our own to handle the server authentication we can solve a couple of problems: - 1 - Detect which Krb5LoginModule is actually available without needing different config for different JVMs 2 - Allow a username / password auth even though the identity will be used later with GSSAPI -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
1
0 / 0

[JBoss JIRA] Created: (SECURITY-542) Add Full Kerberos Support for EJB3 Invocations

by Darran Lofthouse (JIRA)

Add Full Kerberos Support for EJB3 Invocations ---------------------------------------------- Key: SECURITY-542 URL: https://jira.jboss.org/browse/SECURITY-542 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.4.GA Add full Kerberos support for EJB3 invocations. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
2
0 / 0

[JBoss JIRA] (AS7-2029) ConfigAdmin properties not replicated in domain mode

by Thomas Diesler (Created) (JIRA)

ConfigAdmin properties not replicated in domain mode ---------------------------------------------------- Key: AS7-2029 URL: https://issues.jboss.org/browse/AS7-2029 Project: Application Server 7 Issue Type: Task Components: Domain Management, OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

7
12
0 / 0

[JBoss JIRA] (AS7-2171) Revisit deployment triggering subsystem startup

by Thomas Diesler (Created) (JIRA)

Revisit deployment triggering subsystem startup ----------------------------------------------- Key: AS7-2171 URL: https://issues.jboss.org/browse/AS7-2171 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Currently the RestEasyIntegrationTestCase deploys a JAXRS endpoint that integrates with an OSGi service. The endoint deployment does not trigger the OSGi subsystem to start up, but depends on the compendium being deployed. The compendium gets deployed during OSGi subsystem startup. There is currently no way for a deployment foo to declare a dependency on deployment bar when bar gets deployed during subsystem startup, which gets triggered by deployment foo. OSGi has the notion of dynamic package import which seems to be required here for non-osgi deployments -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
6
0 / 0

[JBoss JIRA] Created: (AS7-1488) Document how Extension-List works in the class loading guide

by Stuart Douglas (JIRA)

Document how Extension-List works in the class loading guide ------------------------------------------------------------ Key: AS7-1488 URL: https://issues.jboss.org/browse/AS7-1488 Project: Application Server 7 Issue Type: Task Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
1
0 / 0

[JBoss JIRA] (JBRULES-3251) Implement marshalling backwards compatibility test framework in Drools

by Marco Rietveld (Created) (JIRA)

Implement marshalling backwards compatibility test framework in Drools ---------------------------------------------------------------------- Key: JBRULES-3251 URL: https://issues.jboss.org/browse/JBRULES-3251 Project: Drools Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Marco Rietveld Assignee: Marco Rietveld -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
4
0 / 0

[JBoss JIRA] (JBRULES-3252) Add framework to test marshalling and make it available in the drools-persistence-jpa test-jar.

by Marco Rietveld (Created) (JIRA)

Add framework to test marshalling and make it available in the drools-persistence-jpa test-jar. ------------------------------------------------------------------------------------------------ Key: JBRULES-3252 URL: https://issues.jboss.org/browse/JBRULES-3252 Project: Drools Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Marco Rietveld Assignee: Marco Rietveld Priority: Minor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
2
0 / 0

[JBoss JIRA] (JBRULES-3280) Use marshalling test framework in drools-persistence-jpa

by Marco Rietveld (Created) (JIRA)

Use marshalling test framework in drools-persistence-jpa -------------------------------------------------------- Key: JBRULES-3280 URL: https://issues.jboss.org/browse/JBRULES-3280 Project: Drools Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Marco Rietveld Assignee: Marco Rietveld -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2978) Add support for ObjectMarshallingStrategies in Spring namespace

by Miroslav Štencel (JIRA)

Add support for ObjectMarshallingStrategies in Spring namespace --------------------------------------------------------------- Key: JBRULES-2978 URL: https://issues.jboss.org/browse/JBRULES-2978 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-spring Affects Versions: 5.2.0.M1 Reporter: Miroslav Štencel Assignee: Mark Proctor VariablePersisters functionality has been replaced by ObjectMarshallingStrategies. Please reflect the changes also in Spring namespace. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
2
0 / 0

[JBoss JIRA] Created: (AS7-1752) Starting multiple standalone servers from the same install is not clean

by Brian Stansberry (JIRA)

Starting multiple standalone servers from the same install is not clean ----------------------------------------------------------------------- Key: AS7-1752 URL: https://issues.jboss.org/browse/AS7-1752 Project: Application Server 7 Issue Type: Task Components: Server Affects Versions: 7.0.1.Final, 7.0.0.Final Reporter: Brian Stansberry Fix For: 7.1.0.CR1 It should be easy to copy the standalone dir to another dir (say, "serverB" in the same level in the FS tree) and launch a second server using ./standalone.sh -Djboss.server.base.dir=serverB It somewhat works, but things that aren't as smooth as they should be: a) The resolution of jboss.server.base.dir isn't very smart. For example, to do the common thing and launch the script from within the bin dir you have to either use an absolute path to instance1/2 or do something kludgey like: ./standalone.sh -Djboss.server.base.dir=../serverB If the path is relative and resolving it doesn't result in a file that exists, an attempt should be made to resolve against jboss.home.dir. 2) The launch script directly references the standalone/configuration/logging.properties and standalone/log/boot.log files. So, if those files aren't present the server doesn't boot properly, and both, e.g. serverA and serverB will use the standalone/log/boot.log as their boot log file (where logging goes until the boot process starts the logging subsystem.) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
4
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 January 2012