March 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8882) Make the client.messaging demo comply with TAG-16

by Brian Stansberry (JIRA)

Make the client.messaging demo comply with TAG-16 ------------------------------------------------- Key: JBAS-8882 URL: https://issues.jboss.org/browse/JBAS-8882 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8881) Make the client.jms demo comply with TAG-16

by Brian Stansberry (JIRA)

Make the client.jms demo comply with TAG-16 ------------------------------------------- Key: JBAS-8881 URL: https://issues.jboss.org/browse/JBAS-8881 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8880) Convert demos to comply with TAG-16 requirements

by Brian Stansberry (JIRA)

Convert demos to comply with TAG-16 requirements ------------------------------------------------ Key: JBAS-8880 URL: https://issues.jboss.org/browse/JBAS-8880 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.CR1 TAG-16 lists requirements for examples that we ship (spelled out in more detail at https://docspace.corp.redhat.com/docs/DOC-37891). This is a parent task for converting existing demos in the demos/ module to comply with TAG-16. There will be subtasks for each existing demo. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8887) Make the domain.interactive demo comply with TAG-16

by Brian Stansberry (JIRA)

Make the domain.interactive demo comply with TAG-16 --------------------------------------------------- Key: JBAS-8887 URL: https://issues.jboss.org/browse/JBAS-8887 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8890) Make the domain.servers demo comply with TAG-16

by Brian Stansberry (JIRA)

Make the domain.servers demo comply with TAG-16 ----------------------------------------------- Key: JBAS-8890 URL: https://issues.jboss.org/browse/JBAS-8890 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8886) Make the domain.ds demo comply with TAG-16

by Brian Stansberry (JIRA)

Make the domain.ds demo comply with TAG-16 ------------------------------------------ Key: JBAS-8886 URL: https://issues.jboss.org/browse/JBAS-8886 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8888) Make the domain.messaging demo comply with TAG-16

by Brian Stansberry (JIRA)

Make the domain.messaging demo comply with TAG-16 ------------------------------------------------- Key: JBAS-8888 URL: https://issues.jboss.org/browse/JBAS-8888 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (SECURITY-132) Traditional Authentication

by Darran Lofthouse (JIRA)

Traditional Authentication -------------------------- Key: SECURITY-132 URL: http://jira.jboss.com/jira/browse/SECURITY-132 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Incomming call may be traditional username / password type call but consideration needs to be given for potential outbound call. -- 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

14 years, 8 months

3
11
0 / 0

[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

14 years, 8 months

4
11
0 / 0

[JBoss JIRA] Created: (SECURITY-565) Fix hardcoded server name for SPNEGOSockets

by Marcus Moyses (JIRA)

Fix hardcoded server name for SPNEGOSockets ------------------------------------------- Key: SECURITY-565 URL: https://issues.jboss.org/browse/SECURITY-565 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2.0.3.SP3 Reporter: Marcus Moyses Assignee: Marcus Moyses Fix For: Negotiation_2.0.3.SP4 A hardcoded server name was incorrectly set in the client side starting a negotiation handshake. Now the server name can be set on the client side using the org.jboss.security.negotiation.server.principal system property. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
3
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 March 2011