July 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBMETA-358) Properly validate all XSDs

by Carlo de Wolf (JIRA)

Carlo de Wolf created JBMETA-358: ------------------------------------ Summary: Properly validate all XSDs Key: JBMETA-358 URL: https://issues.jboss.org/browse/JBMETA-358 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Carlo de Wolf Assignee: Chao Wang Priority: Critical Fix For: 7.0.4 -- 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

13 years, 11 months

2
3
0 / 0

[JBoss JIRA] (SECURITY-671) Negotiation/SPNEGO: Fallback to authenticate Form/Basic with ActiveDirectory

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-671?page=com.atlassian.jira.plug... ] Darran Lofthouse commented on SECURITY-671: ------------------------------------------- Have you tried using the standard Kerberos login module in the second domain? > Negotiation/SPNEGO: Fallback to authenticate Form/Basic with ActiveDirectory > ---------------------------------------------------------------------------- > > Key: SECURITY-671 > URL: https://issues.jboss.org/browse/SECURITY-671 > Project: PicketBox (JBoss Security and Identity Management) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: EAP 6.0.0 / JBossAS 7.1.2 > Reporter: Jochen Riedlinger > Assignee: Darran Lofthouse > > Since Version 4 of JBossAS we had our own implementations of a SPNEGOAuthenticator and SPNEGOLoginModule. While trying to migrate to EAP 6 I wanted to switch to your imlementation, because it is officially supported. > Unfortunately I find that your implementation is not yet finished because it lacks in a fallback solution that is able to validate username/password from BASIC/FORM authentication with ActiveDirectory. > Since I had this feature in my old implementation I want to offer to contribute it here to the Negotiation component of the project (unfortunately there is no JIRA component for Negotiation). > I think this would be valuable for anybody using SPNEGO. > My implementation would even word for remote-ejb-calls (with plain username password sent OR when sending a kerberos ticket in the password field) > If you are interested I'll upload my code and configuration instructions (RedHat employees can already see it in Support Case 00640390). -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-671) Negotiation/SPNEGO: Fallback to authenticate Form/Basic with ActiveDirectory

by Jochen Riedlinger (JIRA)

[ https://issues.jboss.org/browse/SECURITY-671?page=com.atlassian.jira.plug... ] Jochen Riedlinger commented on SECURITY-671: -------------------------------------------- Sure, your suggestion could work. Unfortunately our admins will close the possibility to authenticate with plain username/password combinations soon. In Germany we have the "Federal Office for Information Security (BSI)". As we are a state bank we have to follow their guidelines. To have SSL between the browser and JBoss and only Kerberos between JBoss and ActiveDirectory would be a clean solution (and even easy to integrate in the existing code). > Negotiation/SPNEGO: Fallback to authenticate Form/Basic with ActiveDirectory > ---------------------------------------------------------------------------- > > Key: SECURITY-671 > URL: https://issues.jboss.org/browse/SECURITY-671 > Project: PicketBox (JBoss Security and Identity Management) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: EAP 6.0.0 / JBossAS 7.1.2 > Reporter: Jochen Riedlinger > Assignee: Darran Lofthouse > > Since Version 4 of JBossAS we had our own implementations of a SPNEGOAuthenticator and SPNEGOLoginModule. While trying to migrate to EAP 6 I wanted to switch to your imlementation, because it is officially supported. > Unfortunately I find that your implementation is not yet finished because it lacks in a fallback solution that is able to validate username/password from BASIC/FORM authentication with ActiveDirectory. > Since I had this feature in my old implementation I want to offer to contribute it here to the Negotiation component of the project (unfortunately there is no JIRA component for Negotiation). > I think this would be valuable for anybody using SPNEGO. > My implementation would even word for remote-ejb-calls (with plain username password sent OR when sending a kerberos ticket in the password field) > If you are interested I'll upload my code and configuration instructions (RedHat employees can already see it in Support Case 00640390). -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-5233) different startup behaviour: commandline parameters and jboss.properties files

by Gernot P (JIRA)

Gernot P created AS7-5233: ----------------------------- Summary: different startup behaviour: commandline parameters and jboss.properties files Key: AS7-5233 URL: https://issues.jboss.org/browse/AS7-5233 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.1.Final Reporter: Gernot P Assignee: Jason Greene Starting my domain with ${JBOSS_HOME}/bin/domain.sh -Djboss.domain.base.dir=/domain1 the host-controller.log and process-controller.log are written (as expected) to /domain1/log But starting my domain with ${JBOSS_HOME}/bin/domain.sh --properties=/domain1/jboss.properties where /domain1/jboss.properties contains following line jboss.domain.base.dir=/domain1 the host-controller.log and process-controller.log are written to ${JBOSS_HOME}/domain/log The same result (logfiles are written to ${JBOSS_HOME}/domain/log) with /domain1/jboss.properties with following two lines: jboss.domain.base.dir=/domain1 jboss.domain.log.dir=/domain1/log -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-671) Negotiation/SPNEGO: Fallback to authenticate Form/Basic with ActiveDirectory

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-671?page=com.atlassian.jira.plug... ] Darran Lofthouse commented on SECURITY-671: ------------------------------------------- You can use any login module you choose in the fallback domain so it does not need to be a database module - the most common choice in the scenario you describe would be to use one of the LDAP login modules in the second domain to authenticate against LDAP using the username and password. > Negotiation/SPNEGO: Fallback to authenticate Form/Basic with ActiveDirectory > ---------------------------------------------------------------------------- > > Key: SECURITY-671 > URL: https://issues.jboss.org/browse/SECURITY-671 > Project: PicketBox (JBoss Security and Identity Management) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: EAP 6.0.0 / JBossAS 7.1.2 > Reporter: Jochen Riedlinger > Assignee: Darran Lofthouse > > Since Version 4 of JBossAS we had our own implementations of a SPNEGOAuthenticator and SPNEGOLoginModule. While trying to migrate to EAP 6 I wanted to switch to your imlementation, because it is officially supported. > Unfortunately I find that your implementation is not yet finished because it lacks in a fallback solution that is able to validate username/password from BASIC/FORM authentication with ActiveDirectory. > Since I had this feature in my old implementation I want to offer to contribute it here to the Negotiation component of the project (unfortunately there is no JIRA component for Negotiation). > I think this would be valuable for anybody using SPNEGO. > My implementation would even word for remote-ejb-calls (with plain username password sent OR when sending a kerberos ticket in the password field) > If you are interested I'll upload my code and configuration instructions (RedHat employees can already see it in Support Case 00640390). -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-5232) Path description uses wrong attribute type format

by Heiko Braun (JIRA)

Heiko Braun created AS7-5232: -------------------------------- Summary: Path description uses wrong attribute type format Key: AS7-5232 URL: https://issues.jboss.org/browse/AS7-5232 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 The path (i.e. "path=user.dir") resource uses a wrong type for the "read-only" attribute: it is described as ModelType.STRING but should be ModelType.BOOLEAN -- 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

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] (SECURITY-671) Negotiation/SPNEGO: Fallback to authenticate Form/Basic with ActiveDirectory

by Jochen Riedlinger (JIRA)

[ https://issues.jboss.org/browse/SECURITY-671?page=com.atlassian.jira.plug... ] Jochen Riedlinger reopened SECURITY-671: ---------------------------------------- No, fallback to FORM is not really supported. With fallback I mean that if a user enters username/password in the form (yes this part is already there) the LoginModule "generates" the according SPNEGO/Kerberos ticket itself and verifies it with ActiveDirectory. At the moment the fallback to FORM can only delegate to another "basic" LoginModule (like DatabaseLoginModule, etc.). So the exsisting "pseudo-fallback" has another datastore for the fallback instead of doing a fallback to the same Datastore(ActiveDirectory) as the actual original SPNEGO authentication does. I hope this explaination was better, so you understand now what's the advantage of my idea. > Negotiation/SPNEGO: Fallback to authenticate Form/Basic with ActiveDirectory > ---------------------------------------------------------------------------- > > Key: SECURITY-671 > URL: https://issues.jboss.org/browse/SECURITY-671 > Project: PicketBox (JBoss Security and Identity Management) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: EAP 6.0.0 / JBossAS 7.1.2 > Reporter: Jochen Riedlinger > Assignee: Darran Lofthouse > > Since Version 4 of JBossAS we had our own implementations of a SPNEGOAuthenticator and SPNEGOLoginModule. While trying to migrate to EAP 6 I wanted to switch to your imlementation, because it is officially supported. > Unfortunately I find that your implementation is not yet finished because it lacks in a fallback solution that is able to validate username/password from BASIC/FORM authentication with ActiveDirectory. > Since I had this feature in my old implementation I want to offer to contribute it here to the Negotiation component of the project (unfortunately there is no JIRA component for Negotiation). > I think this would be valuable for anybody using SPNEGO. > My implementation would even word for remote-ejb-calls (with plain username password sent OR when sending a kerberos ticket in the password field) > If you are interested I'll upload my code and configuration instructions (RedHat employees can already see it in Support Case 00640390). -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-2959) Adding <capability name="javax.jms.api"/> to standalone.xml's osgi section does not result in the javax.jms api's being visible to OSGi bundles.

by Aaron Whiteside (Created) (JIRA)

Adding <capability name="javax.jms.api"/> to standalone.xml's osgi section does not result in the javax.jms api's being visible to OSGi bundles. ------------------------------------------------------------------------------------------------------------------------------------------------ Key: AS7-2959 URL: https://issues.jboss.org/browse/AS7-2959 Project: Application Server 7 Issue Type: Bug Components: JMS, OSGi Affects Versions: 7.1.0.Beta1 Reporter: Aaron Whiteside Assignee: Clebert Suconic Adding <capability name="javax.jms.api"/> to standalone.xml's osgi section does not result in the javax.jms api's being visible to OSGi bundles. I found however that adding <capability name="javax.xml.bind.api"/> worked as expected for the javax.xml.bind case (meaning it exposes the correct versions for the packages). It seems that <capability name="javax.jms.api"/> exposes a version of 0.0.0, which is obviously not 1.1.0 which is required by importers of javax.jms and thus bundles fail to deploy. -- 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

13 years, 11 months

4
8
0 / 0

[JBoss JIRA] (AS7-5231) CLONE - Removing singleton service should also remove child services.

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created AS7-5231: ------------------------------------- Summary: CLONE - Removing singleton service should also remove child services. Key: AS7-5231 URL: https://issues.jboss.org/browse/AS7-5231 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.2.Final (EAP) Reporter: Wolf-Dieter Fink Assignee: Paul Ferraro Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 When a singleton service is installed, 2 additional child services are installed automatically. To support clean redeploy, these services should auto-remove when the parent service is removed. -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-671) Negotiation/SPNEGO: Fallback to authenticate Form/Basic with ActiveDirectory

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-671?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved SECURITY-671. --------------------------------------- Resolution: Rejected Fallback to FORM authentication is already supported. > Negotiation/SPNEGO: Fallback to authenticate Form/Basic with ActiveDirectory > ---------------------------------------------------------------------------- > > Key: SECURITY-671 > URL: https://issues.jboss.org/browse/SECURITY-671 > Project: PicketBox (JBoss Security and Identity Management) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: EAP 6.0.0 / JBossAS 7.1.2 > Reporter: Jochen Riedlinger > Assignee: Darran Lofthouse > > Since Version 4 of JBossAS we had our own implementations of a SPNEGOAuthenticator and SPNEGOLoginModule. While trying to migrate to EAP 6 I wanted to switch to your imlementation, because it is officially supported. > Unfortunately I find that your implementation is not yet finished because it lacks in a fallback solution that is able to validate username/password from BASIC/FORM authentication with ActiveDirectory. > Since I had this feature in my old implementation I want to offer to contribute it here to the Negotiation component of the project (unfortunately there is no JIRA component for Negotiation). > I think this would be valuable for anybody using SPNEGO. > My implementation would even word for remote-ejb-calls (with plain username password sent OR when sending a kerberos ticket in the password field) > If you are interested I'll upload my code and configuration instructions (RedHat employees can already see it in Support Case 00640390). -- 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

13 years, 11 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 July 2012