August 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (SECURITY-141) Fallback to different authenticator if authentication fails

by Darran Lofthouse (JIRA)

Fallback to different authenticator if authentication fails ----------------------------------------------------------- Key: SECURITY-141 URL: http://jira.jboss.com/jira/browse/SECURITY-141 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Need to consider how this will work especially regarding security domains, possible to do something active directory - password-stacking and an LDAP login module that for negotiation does just role mapping and for non negotiation also does authentication. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
11
0 / 0

[JBoss JIRA] Created: (JBAS-8320) Logging initialization

by Alexey Loubyansky (JIRA)

Logging initialization ---------------------- Key: JBAS-8320 URL: https://jira.jboss.org/browse/JBAS-8320 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Modules Reporter: Alexey Loubyansky Assignee: David Lloyd Fix For: 7.0.0.M1 The following exception is thrown during the start-up on windows (Sun JDK). The system property is in fact set as the error message suggests and I can successfully invoke java.util.logging.Logger logger = java.util.logging.Logger.getLogger("mylogger"); System.out.println(logger.getClass().getName() + " " + logger.getClass().getClassLoader().getClass().getName() + " " + logger.getClass().getClassLoader()); from ManagedProcess just before this.log = Logger.getLogger("org.jboss.process." + processName); (which causes the error) and output will be org.jboss.logmanager.Logger org.jboss.modules.ModuleClassLoader ClassLoader for Module "module:org.jboss.logmanager:jboss-logmanager" Exception in thread "main" java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") at org.jboss.logmanager.Logger.getLogger(Logger.java:60) at org.jboss.logging.JBossLogManagerProvider.doGetLogger(JBossLogManagerProvider.java:55) at org.jboss.logging.JBossLogManagerProvider.getLogger(JBossLogManagerProvider.java:46) at org.jboss.logging.Logger.getLogger(Logger.java:2222) at org.jboss.as.process.ManagedProcess.<init>(ManagedProcess.java:66) at org.jboss.as.process.ProcessManagerMaster.addProcess(ProcessManagerMaster.java:64) at org.jboss.as.process.ProcessManagerMaster.main(ProcessManagerMaster.java:52) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.modules.Module.run(Module.java:105) at org.jboss.modules.Main.main(Main.java:169) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
13
0 / 0

[JBoss JIRA] Created: (SECURITY-45) Assimilate the Higgins Project SPI

by Anil Saldhana (JIRA)

Assimilate the Higgins Project SPI ---------------------------------- Key: SECURITY-45 URL: http://jira.jboss.com/jira/browse/SECURITY-45 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Security SPI Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1 There is a need to get the SPI for Project Higgins Trust Framework into the JBoss Security SPI. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
5
0 / 0

[JBoss JIRA] Created: (SECURITY-470) Callbackhandlers to get information from LDAP

by Anil Saldhana (JIRA)

Callbackhandlers to get information from LDAP --------------------------------------------- Key: SECURITY-470 URL: https://jira.jboss.org/jira/browse/SECURITY-470 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PicketBox Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: PicketBox_v3_0_beta4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
3
0 / 0

[JBoss JIRA] Created: (JGRP-790) FD_SOCK / shared transport: make FD_SOCK a singleton

by Bela Ban (JIRA)

FD_SOCK / shared transport: make FD_SOCK a singleton ---------------------------------------------------- Key: JGRP-790 URL: http://jira.jboss.com/jira/browse/JGRP-790 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.7 If we have multiple channels over the same shared transport, FD_SOCK creates multiple server sockets within the same JVM. Investigate whether we can collapse those into one server socket if we run over the same shared transport. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-8208) Expressing configuration property metadata in domain schema

by Brian Stansberry (JIRA)

Expressing configuration property metadata in domain schema ----------------------------------------------------------- Key: JBAS-8208 URL: https://jira.jboss.org/browse/JBAS-8208 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Fix For: 7.0.0.M1 Clients of the domain management API are going to need to see metadata about the various items they are configuring. Besides simple type stuff, information on things like whether changes require restart, etc, need to be available. This task is to determine where this information comes from and how it can be made available to the layer that provides it to the client. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

5
11
0 / 0

[JBoss JIRA] Created: (JBAS-8137) Simple start and stop scripts

by Brian Stansberry (JIRA)

Simple start and stop scripts ----------------------------- Key: JBAS-8137 URL: https://jira.jboss.org/browse/JBAS-8137 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: Unscheduled This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: >> I would like to see all the configurations that normally get set on the >> command line (JBoss opts and system props) moved to a config file so all >> that is ever required to start a Jboss instance is simply "run.sh >> /<configuration>/". The domain and host configuration files we'll introduce with AS 7 should encapsulate most things that are currently passed in via -D or the arguments to main(). If we start adding additional command line options that need to be processed before the domain/host configuration files are read, we should make it easy to set those in a configuration file (perhaps a simple properties file). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-6332) Injection from outside modules

by Carlo de Wolf (JIRA)

Injection from outside modules ------------------------------ Key: JBAS-6332 URL: https://jira.jboss.org/jira/browse/JBAS-6332 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.GA Reporter: Carlo de Wolf When a servlet is packaged standalone (outside ear) and an EJB is packaged standalone, the EJB can't be injected into the servlet without specifying a JNDI name somewhere. It would be nice to have the ability to inject beans from outside your own enterprise application. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

7
9
0 / 0

[JBoss JIRA] Created: (SECURITY-467) Callbackhandlers to get information from various sources (DB/LDAP)

by Anil Saldhana (JIRA)

Callbackhandlers to get information from various sources (DB/LDAP) ------------------------------------------------------------------ Key: SECURITY-467 URL: https://jira.jboss.org/jira/browse/SECURITY-467 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PicketBox Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: PicketBox_v3_0_beta2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

6
9
0 / 0

[JBoss JIRA] Created: (JBAS-8202) Repository SPI

by Brian Stansberry (JIRA)

Repository SPI -------------- Key: JBAS-8202 URL: https://jira.jboss.org/browse/JBAS-8202 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Fix For: 7.0.0.M2 SPI to allow the DomainController (and Server???) to pull content from a location besides the local filesystem. This doesn't need to be finalized for M1, so scheduling for M2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2010