Comments on: WSFED: Claims Transformation provides simple federated Attribute Service http://identity-des.com/2007/06/11/wsfed-simple-attribute-services/ Thoughts on the reuse of digital identities through federation Tue, 06 Jan 2009 06:02:50 +0000 http://wordpress.org/?v=2.6.3 By: Mark Wahl http://identity-des.com/2007/06/11/wsfed-simple-attribute-services/#comment-31 Mark Wahl Thu, 14 Jun 2007 15:23:26 +0000 http://identity-des.com/2007/06/11/wsfedsimple-attribute-services/#comment-31 "I believe that a minor syntax modification to the WS-Federation 1.1 specification could provide a labeling or grouping mechanism to address your concern." Cool, thanks. “I believe that a minor syntax modification to the WS-Federation 1.1 specification could provide a labeling or grouping mechanism to address your concern.”

Cool, thanks.

]]> By: Don Schmidt http://identity-des.com/2007/06/11/wsfed-simple-attribute-services/#comment-30 Don Schmidt Thu, 14 Jun 2007 06:30:40 +0000 http://identity-des.com/2007/06/11/wsfedsimple-attribute-services/#comment-30 Mark, I am pleased you found the post informative. Thank you for your comment and the detailed explanation on your own site. I believe that a minor syntax modification to the WS-Federation 1.1 specification could provide a labeling or grouping mechanism to address your concern. I will suggest that your observation be submitted as an issue to the WSFED TC for resolution by the members. Mark, I am pleased you found the post informative. Thank you for your comment and the detailed explanation on your own site. I believe that a minor syntax modification to the WS-Federation 1.1 specification could provide a labeling or grouping mechanism to address your concern. I will suggest that your observation be submitted as an issue to the WSFED TC for resolution by the members.

]]> By: Mark Wahl http://identity-des.com/2007/06/11/wsfed-simple-attribute-services/#comment-29 Mark Wahl Wed, 13 Jun 2007 15:50:19 +0000 http://identity-des.com/2007/06/11/wsfedsimple-attribute-services/#comment-29 Thanks for this post. One aspect I had difficulty with is how a recipient of the metadata would distinguish between a situation of there being two separate Attribute Services in an AttributeServiceEndpoint (in which a recipient would potentially need to contact both to get all the attributes), and a single Attribute Service with two separate URIs in an AttributeServiceEndpoint (in which a recipient would only need to contact one URI to get all the attributes; perhaps the service is replicated or multi-homed). http://www.ldap.com/1/commentary/wahl/20070612_01.shtml Thanks for this post. One aspect I had difficulty with is how a recipient of the metadata would distinguish between a situation of there being two separate Attribute Services in an AttributeServiceEndpoint (in which a recipient would potentially need to contact both to get all the attributes), and a single Attribute Service with two separate URIs in an AttributeServiceEndpoint (in which a recipient would only need to contact one URI to get all the attributes; perhaps the service is replicated or multi-homed). http://www.ldap.com/1/commentary/wahl/20070612_01.shtml

]]>