April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-737) spnego AdvancedLdapLoginModule cannot cope with roles contains a slash

by Tom Fonteyne (JIRA)

[ https://issues.jboss.org/browse/SECURITY-737?page=com.atlassian.jira.plug... ] Tom Fonteyne commented on SECURITY-737: --------------------------------------- svn ci jboss-negotiation-extras/src/main/java/org/jboss/security/negotiation/AdvancedLdapLoginModule.java -m "[SECURITY-737] spnego AdvancedLdapLoginModule cannot cope with roles contains a slash" Sending jboss-negotiation-extras/src/main/java/org/jboss/security/negotiation/AdvancedLdapLoginModule.java Transmitting file data . Committed revision 114376 > spnego AdvancedLdapLoginModule cannot cope with roles contains a slash > ---------------------------------------------------------------------- > > Key: SECURITY-737 > URL: https://issues.jboss.org/browse/SECURITY-737 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_1_3 > Reporter: Tom Fonteyne > Assignee: Tom Fonteyne > > cloned from: https://bugzilla.redhat.com/show_bug.cgi?id=953513 > back port for EAP 5.x upstream -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-737) spnego AdvancedLdapLoginModule cannot cope with roles contains a slash

by Tom Fonteyne (JIRA)

[ https://issues.jboss.org/browse/SECURITY-737?page=com.atlassian.jira.plug... ] Tom Fonteyne moved JBPAPP-10718 to SECURITY-737: ------------------------------------------------ Project: PicketBox (was: JBoss Enterprise Application Platform 4 and 5) Key: SECURITY-737 (was: JBPAPP-10718) Affects Version/s: Negotiation_2_1_3 (was: EAP_EWP 5.1.2) Component/s: Negotiation (was: Security) Fix Version/s: (was: TBD EAP 5) Docs QE Status: (was: NEW) > spnego AdvancedLdapLoginModule cannot cope with roles contains a slash > ---------------------------------------------------------------------- > > Key: SECURITY-737 > URL: https://issues.jboss.org/browse/SECURITY-737 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_1_3 > Reporter: Tom Fonteyne > Assignee: Tom Fonteyne > > cloned from: https://bugzilla.redhat.com/show_bug.cgi?id=953513 > back port for EAP 5.x upstream -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-735) spnego AdvancedLdapLoginModule cannot cope with roles contains a slash

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-735?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved SECURITY-735. --------------------------------------- Resolution: Done > spnego AdvancedLdapLoginModule cannot cope with roles contains a slash > ---------------------------------------------------------------------- > > Key: SECURITY-735 > URL: https://issues.jboss.org/browse/SECURITY-735 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_2_2 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_2_3 > > -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-736) Tag and release JBoss Negotiation 2.2.3

by Darran Lofthouse (JIRA)

Darran Lofthouse created SECURITY-736: ----------------------------------------- Summary: Tag and release JBoss Negotiation 2.2.3 Key: SECURITY-736 URL: https://issues.jboss.org/browse/SECURITY-736 Project: PicketBox Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2_2_3 -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-6558) JSR-346 CDI 1.1 support (integrate Weld 2)

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/AS7-6558?page=com.atlassian.jira.plugin.s... ] Jozef Hartinger commented on AS7-6558: -------------------------------------- Initial CDI 1.1 integration https://github.com/jbossas/jboss-as/pull/4417 > JSR-346 CDI 1.1 support (integrate Weld 2) > ------------------------------------------ > > Key: AS7-6558 > URL: https://issues.jboss.org/browse/AS7-6558 > Project: Application Server 7 > Issue Type: Sub-task > Components: CDI / Weld > Reporter: David Lloyd > Assignee: Jozef Hartinger > Fix For: 8.0.0.Alpha1 > > > Integrate Weld 2 in order to meet the Java EE 7 spec requirements. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1025) Prefill scheduled too early for new connections

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1025?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1025. ------------------------------------ Resolution: Done > Prefill scheduled too early for new connections > ----------------------------------------------- > > Key: JBJCA-1025 > URL: https://issues.jboss.org/browse/JBJCA-1025 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.16.Final, 1.1.0.Beta4 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.17.Final, 1.1.0.Beta5 > > -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-67) Improve LogManager formatter capability: System resources, thread ID and minified category

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-67?page=com.atlassian.jira.plugin.... ] David Lloyd commented on LOGMGR-67: ----------------------------------- This is a new feature so it would go into the new stream; backporting is a possibility that we can discuss later on though. > Improve LogManager formatter capability: System resources, thread ID and minified category > ------------------------------------------------------------------------------------------ > > Key: LOGMGR-67 > URL: https://issues.jboss.org/browse/LOGMGR-67 > Project: JBoss Log Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 1.3.2.Final > Environment: JBoss EAP 6.0.1 > Reporter: Jeremy KUHN > Assignee: James Perkins > Labels: jboss > Fix For: 1.5.0.Beta1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Hello, > We are currently developing a major JEE application running on multiple JBoss EAP 6.0.1 instances in a service oriented architecture. > The current implementation of JBoss-logmanager (1.3.2.Final) shipped with JBoss EAP doesn't provide the functionality we require in term of logging formatting. > We are missing: > - Thread ID (Thread names are too long and of different length that disturb the reading of logs) > - we haven't find a way to get the hostname displayed in the logs, a simple solution would be to be able to include System properties and therefore the jboss.host.name property in the pattern. System properties would also be interesting to identified the log coming from a specific application (we'll have one application deployed per JBoss instance). Ideally, we'd like to have the ability to provide a context name to know which application has logged the event but this seems to have been delivered with logging profiles. > - logback has this interesting feature that lets you minify the log category: instead of org.jboss.logmanager.config.ConfigAction you'll get o.j.l.c.ConfigAction which is more readable in the logs. > Regards -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-67) Improve LogManager formatter capability: System resources, thread ID and minified category

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-67?page=com.atlassian.jira.plugin.... ] David Lloyd commented on LOGMGR-67: ----------------------------------- Implementation note: let's make sure that the formats that we are adding which are equivalent to existing offerings in other frameworks match their formatting, to avoid end-user confusion. > Improve LogManager formatter capability: System resources, thread ID and minified category > ------------------------------------------------------------------------------------------ > > Key: LOGMGR-67 > URL: https://issues.jboss.org/browse/LOGMGR-67 > Project: JBoss Log Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 1.3.2.Final > Environment: JBoss EAP 6.0.1 > Reporter: Jeremy KUHN > Assignee: David Lloyd > Labels: jboss > Fix For: 1.3.2.Final > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Hello, > We are currently developing a major JEE application running on multiple JBoss EAP 6.0.1 instances in a service oriented architecture. > The current implementation of JBoss-logmanager (1.3.2.Final) shipped with JBoss EAP doesn't provide the functionality we require in term of logging formatting. > We are missing: > - Thread ID (Thread names are too long and of different length that disturb the reading of logs) > - we haven't find a way to get the hostname displayed in the logs, a simple solution would be to be able to include System properties and therefore the jboss.host.name property in the pattern. System properties would also be interesting to identified the log coming from a specific application (we'll have one application deployed per JBoss instance). Ideally, we'd like to have the ability to provide a context name to know which application has logged the event but this seems to have been delivered with logging profiles. > - logback has this interesting feature that lets you minify the log category: instead of org.jboss.logmanager.config.ConfigAction you'll get o.j.l.c.ConfigAction which is more readable in the logs. > Regards -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-67) Improve LogManager formatter capability: System resources, thread ID and minified category

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-67?page=com.atlassian.jira.plugin.... ] David Lloyd updated LOGMGR-67: ------------------------------ Assignee: James Perkins (was: David Lloyd) > Improve LogManager formatter capability: System resources, thread ID and minified category > ------------------------------------------------------------------------------------------ > > Key: LOGMGR-67 > URL: https://issues.jboss.org/browse/LOGMGR-67 > Project: JBoss Log Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 1.3.2.Final > Environment: JBoss EAP 6.0.1 > Reporter: Jeremy KUHN > Assignee: James Perkins > Labels: jboss > Fix For: 1.3.2.Final > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Hello, > We are currently developing a major JEE application running on multiple JBoss EAP 6.0.1 instances in a service oriented architecture. > The current implementation of JBoss-logmanager (1.3.2.Final) shipped with JBoss EAP doesn't provide the functionality we require in term of logging formatting. > We are missing: > - Thread ID (Thread names are too long and of different length that disturb the reading of logs) > - we haven't find a way to get the hostname displayed in the logs, a simple solution would be to be able to include System properties and therefore the jboss.host.name property in the pattern. System properties would also be interesting to identified the log coming from a specific application (we'll have one application deployed per JBoss instance). Ideally, we'd like to have the ability to provide a context name to know which application has logged the event but this seems to have been delivered with logging profiles. > - logback has this interesting feature that lets you minify the log category: instead of org.jboss.logmanager.config.ConfigAction you'll get o.j.l.c.ConfigAction which is more readable in the logs. > Regards -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-67) Improve LogManager formatter capability: System resources, thread ID and minified category

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-67?page=com.atlassian.jira.plugin.... ] David Lloyd updated LOGMGR-67: ------------------------------ Fix Version/s: 1.5.0.Beta1 (was: 1.3.2.Final) > Improve LogManager formatter capability: System resources, thread ID and minified category > ------------------------------------------------------------------------------------------ > > Key: LOGMGR-67 > URL: https://issues.jboss.org/browse/LOGMGR-67 > Project: JBoss Log Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 1.3.2.Final > Environment: JBoss EAP 6.0.1 > Reporter: Jeremy KUHN > Assignee: James Perkins > Labels: jboss > Fix For: 1.5.0.Beta1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Hello, > We are currently developing a major JEE application running on multiple JBoss EAP 6.0.1 instances in a service oriented architecture. > The current implementation of JBoss-logmanager (1.3.2.Final) shipped with JBoss EAP doesn't provide the functionality we require in term of logging formatting. > We are missing: > - Thread ID (Thread names are too long and of different length that disturb the reading of logs) > - we haven't find a way to get the hostname displayed in the logs, a simple solution would be to be able to include System properties and therefore the jboss.host.name property in the pattern. System properties would also be interesting to identified the log coming from a specific application (we'll have one application deployed per JBoss instance). Ideally, we'd like to have the ability to provide a context name to know which application has logged the event but this seems to have been delivered with logging profiles. > - logback has this interesting feature that lets you minify the log category: instead of org.jboss.logmanager.config.ConfigAction you'll get o.j.l.c.ConfigAction which is more readable in the logs. > Regards -- 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

11 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013