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.
Difference between revisions of "RP Enablement"
(→Overview) |
(→Overview) |
||
| Line 26: | Line 26: | ||
## Opera | ## Opera | ||
# Develop set of utilities/libraries to assist in RP creation | # Develop set of utilities/libraries to assist in RP creation | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
## Generation of Identity Agent Trigger mechanism <object ... | ## Generation of Identity Agent Trigger mechanism <object ... | ||
## Generation of RP Policy tokens <object ... | ## Generation of RP Policy tokens <object ... | ||
| Line 48: | Line 43: | ||
### Websphere | ### Websphere | ||
### JBoss | ### JBoss | ||
| − | + | ## library type ? | |
| + | ### ASP.Net / C# | ||
| + | ### Java | ||
| + | ### javascript/ecmascript | ||
| + | ### PHP | ||
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. | 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. | ||
Revision as of 11:34, 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.
Abbreviations
- IdA = Identity Agent/Identity Selector
- IdP = Identity Provider
- RP = Relying Party
- RPL = Relying Party Layer
RPL Requirements
- Protocol support
- CardSpace
- OpenID 2.0
- yet to be determined
- Browser Support
- IE7
- FireFox 2.0 with CS Extension
- Opera
- Develop set of utilities/libraries to assist in RP creation
- Generation of Identity Agent Trigger mechanism <object ...
- Generation of RP Policy tokens <object ...
- Generation of Privacy Statement for IdA retrieval
- IdA Response Token validation
- IdA Response Token disassembly
- IdA Response Token claim data accessibility
- Token PPID validation ( to IdP )
- Token timestamp validation
- Generic keystore for RP Cert retrieval
- WebServer Platforms
- Apache
- IIS
- J2EE Server Platforms
- Tomcat
- Weblogic
- Websphere
- JBoss
- library type ?
- ASP.Net / C#
- Java
- javascript/ecmascript
- PHP
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.