Difference between revisions of "RP Enablement"

Revision as of 11:17, 2 May 2007

Overview

RP Enablement is a family of components that are used to create Relying Party sites. Separate sub-Components in this category have been and will be created to act as Relying Party Agents for different protocol (and/or interaction type) families.

For example the RSS-SSE RP Test App Component is used to test interactions between it and the Higgins Browser Extension.

As of the Higgins 07.04.30 f2f, Higgins will deliver a Relying Party Layer (RPL). The initial focus of RPL will be on defining the requirements for the support and evaluating which open source initiatives may have some complementary technologies/solutions that may be relevant. RPL will provide cross browser and protocol support, while preparing for unknown future protocols. To assure that the Identity Metasystem and the Higgins architecture is successful, it is imperative that RPL usage be as easy as possible.

RPL Requirements

1. Protocol support
   1. CardSpace
   2. OpenID 2.0
   3. yet to be determined
2. Browser Support
   1. IE7
   2. FireFox 2.0 with CS Extension
   3. Opera
3. Develop set of utilities/libraries to assist in RP creation
   1. library type ?
      1. javascript/ecmascript
      2. vbscript/aspx
      3. java classes
      4. c# classes
   2. Generation of Identity Selector Markup activation <object ...
   3. Response Token validation
   4. Response Token disassembly
   5. Response Token claim data accessibility
   6. Generic keystore for RP Cert retrieval

There are a few initiatives underway that may provide a basis for RPL support. Specificially, the Pamela Project, and xmldap.org. Hopefully we can collaborate with them on providing a consistent RPL.

The OSIS

See Also

• Higgins Wiki
• Architecture
• Components