November 2009 - jboss-identity-issues

[JBoss JIRA] Created: (JBID-212) JBoss STS - implement renew logic

by Stefan Guilhen (JIRA)

JBoss STS - implement renew logic --------------------------------- Key: JBID-212 URL: https://jira.jboss.org/jira/browse/JBID-212 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Affects Versions: IDFED-1.0.0.beta3 Reporter: Stefan Guilhen Assignee: Stefan Guilhen Fix For: IDENTITY-1.0.0.CR1 WS-Trust specification has the concept of token renewal, in which a security token (possibly expired) is replaced by a newer version (new expiration date and possibly updated information). The security token service must implement this concept, allowing for tokens to be renewed. -- 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBID-213) JBoss STS - implement cancel logic

by Stefan Guilhen (JIRA)

JBoss STS - implement cancel logic ---------------------------------- Key: JBID-213 URL: https://jira.jboss.org/jira/browse/JBID-213 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Affects Versions: IDFED-1.0.0.beta3 Reporter: Stefan Guilhen Assignee: Stefan Guilhen Fix For: IDFED-1.0.0.CR1 WS-Trust specification defines the concept of token cancellation. The STS must be able to process cancel requests to invalidate tokens - that is, a token that has been cancelled cannot be considered valid in subsequent validate requests. -- 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBID-139) JBoss STS - implement token encryption logic

by Stefan Guilhen (JIRA)

JBoss STS - implement token encryption logic -------------------------------------------- Key: JBID-139 URL: https://jira.jboss.org/jira/browse/JBID-139 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Affects Versions: IDFED-1.0.0.alpha3 Reporter: Stefan Guilhen Assignee: Stefan Guilhen Fix For: IDFED-1.0.0.alpha4 When the EncryptToken property is set to true, the STS must encrypt the issued token using the service provider PKC. If either the service provider or its PKC is not available (a request can be made without specifying the target service provider) we should log a warn message and leave the token unencrypted. -- 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

15 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBID-218) SignatuteValidationHandler ignores validation results

by Anil Saldhana (JIRA)

SignatuteValidationHandler ignores validation results ----------------------------------------------------- Key: JBID-218 URL: https://jira.jboss.org/jira/browse/JBID-218 Project: JBoss Identity Issue Type: Bug Components: Identity-Federation Reporter: Anil Saldhana Assignee: Anil Saldhana Priority: Critical Fix For: IDFED-1.0.0.GA Marcel's feedback. -- 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBID-216) STSSecurityHandler: Refactor and have the security token be passed to this handler via the SOAPMessageContext instead of subclassing

by Daniel Bevenius (JIRA)

STSSecurityHandler: Refactor and have the security token be passed to this handler via the SOAPMessageContext instead of subclassing ------------------------------------------------------------------------------------------------------------------------------------ Key: JBID-216 URL: https://jira.jboss.org/jira/browse/JBID-216 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Affects Versions: IDFED-1.0.0.beta3 Reporter: Daniel Bevenius Assignee: Daniel Bevenius Priority: Minor Currently the STSSecurityHeader is abstract and concrete implementations are expected to implement two methods that return the QName of the Security element and that of the security token that this handler can handle. I think that this was perhaps not a good choice on my part and a better choice would be to push this responsibility to a different handler that would have the responsibility to extract the security token and set that token in the SOAPMessageContext in a known location. This should make this more extendable and less brittle (no subclassing). Users that want to extract a different security token, or simply a different version, only need to change/implement a handler and extract the correct security token and set it in the context. -- 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBID-215) STSSecurityHandler: Enable the username/password to be retreived from the SOAPMessageContext.

by Daniel Bevenius (JIRA)

STSSecurityHandler: Enable the username/password to be retreived from the SOAPMessageContext. --------------------------------------------------------------------------------------------- Key: JBID-215 URL: https://jira.jboss.org/jira/browse/JBID-215 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Affects Versions: IDFED-1.0.0.CR1 Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: IDENTITY-1.0.0.CR1 Currently the STSSecurityHandler can only take its configuration from a properties file. This includes the username/password. I previously thought that this was alright but Anil pointed out there might be token providers that require the callers credentials. The task should add the ability for a handler earlier in the handlerchain to extract the username/password from whatever location and set these values in the SOAPMessageContext using constants defined in the STSSecurityHandler: ** * Constant that can be used by handlers to set the username in the SOAPMessageContext. */ public static final String USERNAME_MSG_CONTEXT_PROPERTY = "org.jboss.identity.federation.core.wstrust.handlers.username"; /** * Constant that can be used by handlers to set the password in the SOAPMessageContext. */ public static final String PASSWORD_MSG_CONTEXT_PROPERTY = "org.jboss.identity.federation.core.wstrust.handlers.password"; So both of these options will be available and precedence will be given to any values in the SOAPMessageContext. -- 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBID-173) IDM::Ensure log.isTraceEnabled usage

by Anil Saldhana (JIRA)

IDM::Ensure log.isTraceEnabled usage ------------------------------------ Key: JBID-173 URL: https://jira.jboss.org/jira/browse/JBID-173 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: IDFED-1.0.0.beta1 -- 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

15 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBID-96) Make hibernate xml mappings for annotated entities

by Boleslaw Dawidowicz (JIRA)

Make hibernate xml mappings for annotated entities -------------------------------------------------- Key: JBID-96 URL: https://jira.jboss.org/jira/browse/JBID-96 Project: JBoss Identity Issue Type: Feature Request Components: IDM Reporter: Boleslaw Dawidowicz Assignee: Boleslaw Dawidowicz Fix For: 1.0.0.GA Hibernate entities should use mappings in xml instead of annotations. This will benefit in the future with more flexible fixes and configuration changes in case of database compatibility issues. -- 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

15 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBID-214) SamlCredential: assertionToElement should throw ProcessingException

by Daniel Bevenius (JIRA)

SamlCredential: assertionToElement should throw ProcessingException ------------------------------------------------------------------- Key: JBID-214 URL: https://jira.jboss.org/jira/browse/JBID-214 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Reporter: Daniel Bevenius Assignee: Daniel Bevenius Priority: Minor Fix For: IDENTITY-1.0.0.CR1 I'd like to revert the signature of this method back to throwing ProcessingException which is compatible with the current code in the ESB project. This is really just so that the identity jars can be updated without impact, for example, if SOA-P choose to use a later version of JBoss Identity than the ESB project is using. If we later want to change this then that is fine but a change will be required in the ESB project so it would be better to wait until the next release. -- 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBID-91) LDAP based circle of trust configuration store

by Anil Saldhana (JIRA)

LDAP based circle of trust configuration store ---------------------------------------------- Key: JBID-91 URL: https://jira.jboss.org/jira/browse/JBID-91 Project: JBoss Identity Issue Type: Feature Request Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: 1.0.0.CR1 This will require custom ldap schemas. References: http://linuxgazette.net/130/peterson.html https://www.opends.org/1.2/page/HowToExtendTheLDAPSchema http://blogs.sun.com/indira/entry/using_openldap_as_user_data http://blogs.sun.com/indira/resource/OpenLDAP.schema -- 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

15 years, 1 month

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-identity-issues November 2009