July 2009 - jboss-identity-issues

[JBoss JIRA] Created: (JBID-95) Event API implementation

by Boleslaw Dawidowicz (JIRA)

Event API implementation ------------------------ Key: JBID-95 URL: https://jira.jboss.org/jira/browse/JBID-95 Project: JBoss Identity Issue Type: Feature Request Components: IDM Reporter: Boleslaw Dawidowicz Assignee: Boleslaw Dawidowicz Fix For: 1.0.0.CR1 -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBID-98) Create initial IDM documentation based on current wiki

by Boleslaw Dawidowicz (JIRA)

Create initial IDM documentation based on current wiki ------------------------------------------------------ Key: JBID-98 URL: https://jira.jboss.org/jira/browse/JBID-98 Project: JBoss Identity Issue Type: Feature Request Components: IDM Reporter: Boleslaw Dawidowicz Assignee: Boleslaw Dawidowicz Fix For: 1.0.0.GA Creat docbook documentaion based on current wiki content -- 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, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBID-140) JBoss STS - add a ClaimsHandler interface that allows for pluggable claims interpreters

by Stefan Guilhen (JIRA)

JBoss STS - add a ClaimsHandler interface that allows for pluggable claims interpreters --------------------------------------------------------------------------------------- Key: JBID-140 URL: https://jira.jboss.org/jira/browse/JBID-140 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 A WS-Trust request may contain a set of claims that must be included in the issued token. The claims syntax is not specified, so it must be inferred from the Dialect attribute of the Claims element. We must create a ClaimsHandler or ClaimsProvider interface in the STS system to allow for pluggable configuration of claim handlers. A possible default implementation could handle claims as specified by the Identity Metasystem Interoperability 1.0 (http://docs.oasis-open.org/imi/ns/identity-200810) and use the JBoss IDM API to obtain the necessary information. The configuration of the ClaimsHandlers would be similar to the TokeProviders and should also allow for the specification of general properties: <ClaimsHandlers> <ClaimsHandler HandlerClass="...." ClaimsDialect="http://...."> <Property name="prop" value="value"/> </ClaimsHandler> </ClaimsHandler> -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBID-138) JBoss STS - implement proof-of-possession token logic

by Stefan Guilhen (JIRA)

JBoss STS - implement proof-of-possession token logic ----------------------------------------------------- Key: JBID-138 URL: https://jira.jboss.org/jira/browse/JBID-138 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 The WS-Trust specification defines the concept of a proof-of-possession token, that is, a token that can be used to verify the association between a security token and a subject. We must add support for proof tokens, both symmetric (secret key) and assymetric (certificate based). The proof must no only be included in the WS-Trust response, but also in the security tokens being generated by each token provider. Once this has been implemented, we must change the SAML20TokenProvider so it adds the appropriate proof token to the assertion being created. -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBID-40) SAML2: Logout Profile

by Anil Saldhana (JIRA)

SAML2: Logout Profile --------------------- Key: JBID-40 URL: https://jira.jboss.org/jira/browse/JBID-40 Project: JBoss Identity Issue Type: Feature Request Components: Identity-Federation Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: 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, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBID-141) JBoss STS - add logging to the STS classes

by Stefan Guilhen (JIRA)

JBoss STS - add logging to the STS classes ------------------------------------------ Key: JBID-141 URL: https://jira.jboss.org/jira/browse/JBID-141 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 We need to log the important events in the STS classes using the appropriate log levels. -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBID-152) IDP should return attributes of caller such as email address

by Anil Saldhana (JIRA)

IDP should return attributes of caller such as email address ------------------------------------------------------------ Key: JBID-152 URL: https://jira.jboss.org/jira/browse/JBID-152 Project: JBoss Identity Issue Type: Feature Request Components: Identity-Federation Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: IDFED-1.0.0.beta1 The IDP should be configurable to return attributes of the subject such as email address etc that can be read from DB, LDAP etc. This feature will require attribute providers to be plugged in. -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBID-137) JBoss STS - improve the configuration to allow for general properties to be specified for each token provider

by Stefan Guilhen (JIRA)

JBoss STS - improve the configuration to allow for general properties to be specified for each token provider ------------------------------------------------------------------------------------------------------------- Key: JBID-137 URL: https://jira.jboss.org/jira/browse/JBID-137 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 JBoss STS does not currently provide a way to specify general properties for a token provider. A token provider may be configurable (for example, a provider may take an URL of a third-party service or repository) and the configuration schema must be changed to allow the specification of properties. The token providers should also be associated with the token element (namespace and local name) besides the token type. The reason for doing this is that validation/renewing/cancellation requests do not specify the token type explicitly so it must be inferred by the token element. The only way for the STS to figure out which provider should be used to validate the token is by having an association between token elements and providers. Something like: <TokenProvider ProviderClass="...." TokenType="..." TokenNamespace="urn:...." TokenName="Assertion"> <Property name="..." value="..."/> <Property name="..." vluae="..."/> </TokenProvider> A final note about configuration is about the need for the TruststoreAlias attribute of the ServiceProvider. The alias of each service provider can be configured through the ValidatingAlias element of KeyProvider, so we may just make the TruststoreAlias attribute optional. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBID-115) Liberty ID-WSF 2.0 JAXB object model

by Anil Saldhana (JIRA)

Liberty ID-WSF 2.0 JAXB object model ------------------------------------ Key: JBID-115 URL: https://jira.jboss.org/jira/browse/JBID-115 Project: JBoss Identity Issue Type: Sub-task Components: Identity-Federation Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: IDFED-1.0.0.beta1 Use the xsds to generate the JAXB object model in the idfed model workspace. -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBID-60) Liberty ID-WSF

by Anil Saldhana (JIRA)

Liberty ID-WSF -------------- Key: JBID-60 URL: https://jira.jboss.org/jira/browse/JBID-60 Project: JBoss Identity Issue Type: Feature Request Components: Identity-Federation Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: 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, 4 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-identity-issues July 2009