February 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2552) Undertow AuthenticationMechanism Configuration Overrides

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2552?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2552: ----------------------------------- Labels: web_security (was: ) > Undertow AuthenticationMechanism Configuration Overrides > -------------------------------------------------------- > > Key: WFLY-2552 > URL: https://issues.jboss.org/browse/WFLY-2552 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: web_security > Fix For: 9.0.0.CR1 > > > General article covering the security configuration for Undertow / WildFly: - > https://community.jboss.org/wiki/UndertowSecurityConfiguration -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2567) Custom authentication mechanism definition - Subsystem Level

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2567?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2567: ----------------------------------- Labels: web_security (was: ) > Custom authentication mechanism definition - Subsystem Level > ------------------------------------------------------------ > > Key: WFLY-2567 > URL: https://issues.jboss.org/browse/WFLY-2567 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: web_security > Fix For: 9.0.0.CR1 > > -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2568) Custom authentication mechanism configuration - Deployment Level

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2568?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2568: ----------------------------------- Labels: web_security (was: ) > Custom authentication mechanism configuration - Deployment Level > ---------------------------------------------------------------- > > Key: WFLY-2568 > URL: https://issues.jboss.org/browse/WFLY-2568 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: web_security > Fix For: 9.0.0.CR1 > > -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2639) HttpServletRequest.getAuthType returns incorrect value

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2639?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2639: ----------------------------------- Labels: web_security (was: ) > HttpServletRequest.getAuthType returns incorrect value > ------------------------------------------------------ > > Key: WFLY-2639 > URL: https://issues.jboss.org/browse/WFLY-2639 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Reporter: Arun Gupta > Assignee: Darran Lofthouse > Priority: Minor > Labels: web_security > Fix For: 9.0.0.CR1 > > > HttpServletRequest.getAuthType returns "Programatic" if login/logout methods are used. > Javadoc says: > one of the static members BASIC_AUTH, FORM_AUTH, CLIENT_CERT_AUTH, DIGEST_AUTH (suitable for == comparison) or the container-specific string indicating the authentication scheme, or null if the request was not authenticated. > "Programatic" is not one of the expected values. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2639) HttpServletRequest.getAuthType returns incorrect value

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2639?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2639: ----------------------------------- Fix Version/s: (was: 9.0.0.CR1) > HttpServletRequest.getAuthType returns incorrect value > ------------------------------------------------------ > > Key: WFLY-2639 > URL: https://issues.jboss.org/browse/WFLY-2639 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Reporter: Arun Gupta > Assignee: Darran Lofthouse > Priority: Minor > Labels: web_security > > HttpServletRequest.getAuthType returns "Programatic" if login/logout methods are used. > Javadoc says: > one of the static members BASIC_AUTH, FORM_AUTH, CLIENT_CERT_AUTH, DIGEST_AUTH (suitable for == comparison) or the container-specific string indicating the authentication scheme, or null if the request was not authenticated. > "Programatic" is not one of the expected values. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2635) HTTP Management Interface Configuration

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2635?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2635: ----------------------------------- Labels: management_security, management_sso (was: ) > HTTP Management Interface Configuration > --------------------------------------- > > Key: WFLY-2635 > URL: https://issues.jboss.org/browse/WFLY-2635 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: management_security,, management_sso > Fix For: 9.0.0.CR1 > > > Various configuration items are required for the HTTP Management interface, this is a parent task to combine them. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-544) Support Password Stacking for Domain HTTP Server

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-544?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved WFLY-544. ----------------------------------- Fix Version/s: 8.0.0.Final (was: 9.0.0.CR1) Resolution: Out of Date The security realms already split the authentication from the authorization so it is possible to authenticate using one config and then load groups using another, > Support Password Stacking for Domain HTTP Server > ------------------------------------------------ > > Key: WFLY-544 > URL: https://issues.jboss.org/browse/WFLY-544 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Jess Sightler > Assignee: Darran Lofthouse > Fix For: 8.0.0.Final > > > Our clients need the ability to restrict logins by client certificate, and by a role stored within an LDAP server. Ideally, the system would support some form of password-stacking feature to allow access based upon a combination of authentication systems. > Cf, http://docs.jboss.org/jbossas/docs/Server_Configuration_Guide/4/html/Usin... for how this is implemented in existing EAP5 installations. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2888) Undertow subsystem ajp listener configuraion not loaded

by JuYeon Yu (JIRA)

[ https://issues.jboss.org/browse/WFLY-2888?page=com.atlassian.jira.plugin.... ] JuYeon Yu commented on WFLY-2888: --------------------------------- I set like this. <ajp-listener name="ajp" socket-bindind="ajp" max-parameters="5000"/> <http-listener name="default" socket-bindind="http" max-parameters="5000"/> when connect user http listener submit is OK. but, use ajp listener exception is occur. java.lang.IllegalStateException: UT000047: The number of parameters exceeded the maximum of 1000 So, I debugging, end i found the setting not loaded. > Undertow subsystem ajp listener configuraion not loaded > ------------------------------------------------------- > > Key: WFLY-2888 > URL: https://issues.jboss.org/browse/WFLY-2888 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Environment: WildfFly 8.0.0.Final-SANPSHOT (b365f63a1701) > Reporter: JuYeon Yu > > Ajp Listener configuration not loaded. > I set like this '<ajp-listener name="ajp" socket-binding="ajp" max-parameters="5000"/>'. > But this value not applied. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2856) Classloader leak caused by xnio-file-watcher

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2856?page=com.atlassian.jira.plugin.... ] Tomaz Cerar resolved WFLY-2856. ------------------------------- Resolution: Done Undertow 1.0.0.Final was merged to wildfly master. > Classloader leak caused by xnio-file-watcher > -------------------------------------------- > > Key: WFLY-2856 > URL: https://issues.jboss.org/browse/WFLY-2856 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.CR1 > Reporter: Harald Wellmann > Assignee: Stuart Douglas > Fix For: 8.0.0.Final > > > After redeploying my application from Eclipe/JBoss Tools via "Full Publish" a couple of times in a row, I'm getting a PermGen OutOfMemoryError. > In jvisualvm, I can see multiple threads named xnio-file-watcher, each having its context classloader set to the module classloader of my (undeployed) application. Probably the thread should be stopped (but isn't) when the application is undeployed. > This leak only occurs with unzipped deployments. > I also see these extra threads independent of Eclipse when copying an unzipped deployment to {{standalone/deployments}} and adding/removing the dodeploy/deployed marker files. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2881) org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase#testCalendarBasedTimeout

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2881?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-2881: --------------------------------- Assignee: Tomaz Cerar (was: David Lloyd) > org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase#testCalendarBasedTimeout > -------------------------------------------------------------------------------------- > > Key: WFLY-2881 > URL: https://issues.jboss.org/browse/WFLY-2881 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.0.0.Final > Reporter: Frank Langelage > Assignee: Tomaz Cerar > Attachments: org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.txt, TEST-org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.xml > > > Running build with smoke tests on current github sources I get failure in this test case. > HOUR_OF_DAY is not 0 as expected but 1. > I changed the Assert in the test case to print out firstTimeout.toString() instead of only timeZoneDisplayName. > See attached files for more. -- 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

12 years, 5 months

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-jira February 2014