August 2009 - jboss-identity-issues

[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-178) Move the WS-Trust code from API to core

by Anil Saldhana (JIRA)

Move the WS-Trust code from API to core --------------------------------------- Key: JBID-178 URL: https://jira.jboss.org/jira/browse/JBID-178 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Affects Versions: IDFED-1.0.0.beta1 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: IDFED-1.0.0.beta2 The API should be classes that the developer uses. The WS-Trust client api certainly falls here. Currently the ws-trust code including the plugins need to go into core. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBID-179) Fix JBossSTSUnitTestCase

by Anil Saldhana (JIRA)

Fix JBossSTSUnitTestCase ------------------------ Key: JBID-179 URL: https://jira.jboss.org/jira/browse/JBID-179 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Affects Versions: IDFED-1.0.0.beta1 Reporter: Anil Saldhana Assignee: Stefan Guilhen Fix For: IDFED-1.0.0.beta2 please look for TODO with this jira issue -- 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
1
0 / 0

[JBoss JIRA] Deleted: (JBID-166) Create a single cached JAXBContext for the object models

by Anil Saldhana (JIRA)

[ https://jira.jboss.org/jira/browse/JBID-166?page=com.atlassian.jira.plugi... ] Anil Saldhana deleted JBID-166: ------------------------------- > Create a single cached JAXBContext for the object models > -------------------------------------------------------- > > Key: JBID-166 > URL: https://jira.jboss.org/jira/browse/JBID-166 > Project: JBoss Identity > Issue Type: Sub-task > Reporter: Anil Saldhana > Assignee: Anil Saldhana > -- 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
0
0 / 0

[JBoss JIRA] Created: (JBID-181) Remove KeyStoreUtil from bindings

by Anil Saldhana (JIRA)

Remove KeyStoreUtil from bindings --------------------------------- Key: JBID-181 URL: https://jira.jboss.org/jira/browse/JBID-181 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Affects Versions: IDFED-1.0.0.beta1 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: IDFED-1.0.0.beta2 It exists in API -- 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-184) STS: OpenID Token Provider

by Anil Saldhana (JIRA)

STS: OpenID Token Provider -------------------------- Key: JBID-184 URL: https://jira.jboss.org/jira/browse/JBID-184 Project: JBoss Identity Issue Type: Feature Request Components: Identity-Federation Reporter: Anil Saldhana Assignee: Anil Saldhana Since the STS can provide security tokens, we can add an OpenID Token Provider. -- 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
0
0 / 0

[JBoss JIRA] Created: (JBID-183) REST based STS

by Anil Saldhana (JIRA)

REST based STS -------------- Key: JBID-183 URL: https://jira.jboss.org/jira/browse/JBID-183 Project: JBoss Identity Issue Type: Feature Request Components: Identity-Federation Reporter: Anil Saldhana Assignee: Anil Saldhana Investigate and provide a REST based STS. Since an STS theoretically services XML based requests, there should be no real dependence on SOAP. -- 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
0
0 / 0

[JBoss JIRA] Created: (JBID-162) signature encoding/decoding not correct for HTTP_POST binding

by Marcel Kolsteren (JIRA)

signature encoding/decoding not correct for HTTP_POST binding ------------------------------------------------------------- Key: JBID-162 URL: https://jira.jboss.org/jira/browse/JBID-162 Project: JBoss Identity Issue Type: Bug Reporter: Marcel Kolsteren Assignee: Anil Saldhana An interoperability test between a JBID-based Service Provider and an OpenSSO-based Identity Provider revealed a problem with the signature encoding/decoding in JBID. When posting a message, JBID places the signature and the signature algorithm in separate hidden fields in the form. According to the SAMLv2 spec, this is not correct. When using HTTP-POST binding, the signature should be encoded as part of the XML message (<ds:Signature> element). Separate encoding of the signature is intended for the HTTP-Redirect profile only (because of space concerns). -- 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
3
0 / 0

[JBoss JIRA] Created: (JBID-182) Seam authentication filter: signature validation still based on HTTP/Redirect binding

by Marcel Kolsteren (JIRA)

Seam authentication filter: signature validation still based on HTTP/Redirect binding ------------------------------------------------------------------------------------- Key: JBID-182 URL: https://jira.jboss.org/jira/browse/JBID-182 Project: JBoss Identity Issue Type: Bug Affects Versions: IDFED-1.0.0.beta1 Reporter: Marcel Kolsteren Assignee: Marcel Kolsteren Fix For: IDFED-1.0.0.beta2 The Seam authentication filter still expects incoming signatures to be in the HTTP/Redirect style: the signature and signature algorithm are not read from the XML message, but from separate parameters. Now that JBID-162 has been fixed, the Seam authentication filter should read the signature info from the XML message. -- 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
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-identity-issues August 2009