Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

RP Enablement

Revision as of 09:33, 14 May 2007 by Mikemci.us.ibm.com (Talk | contribs) (Overview)

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 Enablement Component (RPEC). The initial focus of RPEC 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. RPEC 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 RPEC usage be as easy as possible.

Abbreviations

  1. IdA = Identity Agent/Identity Selector
  2. IdP = Identity Provider
  3. RP = Relying Party
  4. RPEC = Relying Party Enablement Component

Example.jpg

RPEC 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. Generation of Identity Agent Trigger mechanism
      1. <object ...application/x-InformationCard
      2. WSPolicy
      3. Idemix policy
    2. Generation of RP Policy tokens <object ...
    3. Generation of Privacy Statement for IdA retrieval
    4. RP validation of IdA Response Token
    5. RP disassembly of IdA Response Token
    6. RP accessibility to IdA Response Token elements
      1. claim data
      2. issuer
      3. token expiration
      4. public keys
    7. Token PPID validation ( to IdP )
    8. Token timestamp validation
    9. Generic keystore for RP Cert retrieval
    10. WebServer Platforms
      1. Apache
      2. IIS
    11. J2EE Server Platforms
      1. Tomcat
      2. Weblogic
      3. Websphere
      4. JBoss
    12. library type ?
      1. ASP.Net / C#
      2. Java
      3. javascript/ecmascript
      4. PHP

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

See Also

Back to the top