January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (SECURITY-352) Cache Server Subject

by Darran Lofthouse (JIRA)

Cache Server Subject -------------------- Key: SECURITY-352 URL: https://jira.jboss.org/jira/browse/SECURITY-352 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.4.GA Each authentication process currently has 3 AS-REQ requests (6 if pre-auth is an issue) One request for each of the SPNEGO round trips and then one request for the LDAP search. Attempts to make use of a local ticket cache failed: -  As the keytab had not been read it meant that the requirements for storeKey were not met, this is needed for SPNEGO. <module-option name="storeKey">true</module-option> A mechanism to cache the server subject is needed. The expiration time of the ticket can be obtained to decide how long to cache the ticket for: - Set<Object> privateCredentials = serverSubject.getPrivateCredentials(); for (Object current : privateCredentials) { if (current instanceof KerberosTicket) { KerberosTicket ticket = (KerberosTicket) current; System.out.println(ticket.getEndTime()); } } -- 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

11 years, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (SECURITY-357) Add Active Directory Debugging to User Guide

by Darran Lofthouse (JIRA)

Add Active Directory Debugging to User Guide -------------------------------------------- Key: SECURITY-357 URL: https://jira.jboss.org/jira/browse/SECURITY-357 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2.0.3.GA Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.4.GA Reference the following article which describes how to add additional event logging: - http://support.microsoft.com/default.aspx?scid=kb;en-us;314980&sd=tech -- 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

11 years, 6 months

1
5
0 / 0

[JBoss JIRA] Created: (SECURITY-573) Improve handling of IOException thrown from NegotiationAuthenticator

by Marek Posolda (JIRA)

Improve handling of IOException thrown from NegotiationAuthenticator -------------------------------------------------------------------- Key: SECURITY-573 URL: https://issues.jboss.org/browse/SECURITY-573 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2.0.3.GA Environment: JBoss EPP 5.1.GA with SPNEGO support, JBoss Negotiation 2.0.3, commons-http-client 3.1 used as HTTP client Reporter: Marek Posolda Assignee: Darran Lofthouse Fix For: Negotiation_2.0.4 Currently if IOException is thrown from NegotiationAuthenticator (For example from line 123 from statement: NegotiationMessage requestMessage = mf.createMessage(authTokenIS); ) then this exception is never logged but it's catched and ignored in CoyoteAdapter.service. Result is that client receives response code 200 OK and emtpy HTTP response. And there is nothing in server log, which can be used to recognize error. So I need to debug if I want to find the real cause of IO issue. Example for simulating of this issue can be using of Kerberos OID instead of SPNEGO OID as described in Jira SECURITY-572 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (SECURITY-538) Document the AdvancedADLoginModule

by Darran Lofthouse (JIRA)

Document the AdvancedADLoginModule ---------------------------------- Key: SECURITY-538 URL: https://jira.jboss.org/browse/SECURITY-538 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.3.SP4 , Negotiation_2.0.4.GA The AdvancedADLoginModule was added to allow the users primary group to be identified, documentation needs to be added on the use of this login module. -- 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

11 years, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (SECURITY-473) Add documentation for IBM JRE

by Darran Lofthouse (JIRA)

Add documentation for IBM JRE ----------------------------- Key: SECURITY-473 URL: https://jira.jboss.org/jira/browse/SECURITY-473 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Negotiation Affects Versions: Negotiation_2.0.3.SP2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.3.SP3, Negotiation_2.0.4.GA Add documentation for IBM JRE http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/rz... http://www.ibm.com/developerworks/java/jdk/security/50/secguides/jgssDocs... Example: - <application-policy name="host-ibm"> <authentication> <login-module code="com.ibm.security.auth.module.Krb5LoginModule" flag="required"> <module-option name="useKeytab">file:///home/darranl/src/negotiation-as/jboss-5.1.0.GA-vm137/bin/service.keytab</module-option> <module-option name="principal">host/testserver(a)VM137DOMAIN.GSSLAB</module-option> <module-option name="credsType">both</module-option> <module-option name="debug">false</module-option> </login-module> </authentication> </application-policy> Also see JBAS-4969 the property jboss.security.disable.secdomain.option=true needs to be set. -- 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

11 years, 6 months

1
6
0 / 0

[JBoss JIRA] Created: (SECURITY-457) User guide builds incorrectly using Java 6

by Darran Lofthouse (JIRA)

User guide builds incorrectly using Java 6 ------------------------------------------ Key: SECURITY-457 URL: https://jira.jboss.org/jira/browse/SECURITY-457 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2.0.3.SP2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.4.GA The user guide builds incorrectly running Java 6, however Java 5 still works as expected. Suspect XML parsing differences, documentation should be updated to work with Java 6. -- 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

11 years, 6 months

1
4
0 / 0

[JBoss JIRA] (AS7-3377) TS: Check how JDBC drivers are copied

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3377: --------------------------------- Summary: TS: Check how JDBC drivers are copied Key: AS7-3377 URL: https://issues.jboss.org/browse/AS7-3377 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka -- 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

11 years, 6 months

4
13
0 / 0

[JBoss JIRA] (AS7-2105) TS: Put all management tests into one dir (org.jboss.as.test.integration.mgmt)

by Ondrej Zizka (Created) (JIRA)

TS: Put all management tests into one dir (org.jboss.as.test.integration.mgmt) ------------------------------------------------------------------------------ Key: AS7-2105 URL: https://issues.jboss.org/browse/AS7-2105 Project: Application Server 7 Issue Type: Sub-task Reporter: Ondrej Zizka integration/org.jboss.as.test.integration.management and further separated by subsystems/interfaces: org.jboss.as.test.integration.management.cli org.jboss.as.test.integration.management.http org.jboss.as.test.integration.management.api org.jboss.as.test.integration.management.api.messaging Thanks Dominik for pointing out. -- 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

11 years, 6 months

3
4
0 / 0

[JBoss JIRA] (AS7-2176) TS: Check tests workdirs

by Ondrej Zizka (Created) (JIRA)

TS: Check tests workdirs ------------------------ Key: AS7-2176 URL: https://issues.jboss.org/browse/AS7-2176 Project: Application Server 7 Issue Type: Sub-task Reporter: Ondrej Zizka Some tests (also unit tests) have work dirs in ${basedir}, which leaves garbage after running. That should change either to target/work or /tmp/... (consider what's better). -- 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

11 years, 6 months

4
4
0 / 0

[JBoss JIRA] (AS7-2007) Testsuite tasks (tracking)

by Ondrej Zizka (Created) (JIRA)

Testsuite tasks (tracking) -------------------------- Key: AS7-2007 URL: https://issues.jboss.org/browse/AS7-2007 Project: Application Server 7 Issue Type: Task Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka -- 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

11 years, 6 months

10
28
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012