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 "MultiProtocol Relying Party Enablement"
m |
|||
| Line 1: | Line 1: | ||
| − | + | The relying party enablement code has been architected to support many different authentication protocols and can be implemented on many different application container platforms. The package org.eclipse.higgins.rp.interface contains all the interfaces needed for an API, SPI and other common utility functions. | |
| + | Authentication protocols are implemented through Authentication Protocol Handlers. There should be a new project for each authentication protocol supported. Currently, the only supported authentication protocol handler is the Information Card authentication protocol handler. The authentication protocol handlers depend on a set of SPIs to handle the platform specific implementation. There should be no platform dependent code written into any of the authentication protocol handlers. | ||
| + | |||
| + | Relying Party applications can be configured to use one of the plaform specific implementations and one authentication protocol handler. In the future the code will support applications that want to give users a choice of authentication protocols to gain access to the application. | ||
== See Also == | == See Also == | ||
* [[Extensible authentication protocol RP Website Solution]] | * [[Extensible authentication protocol RP Website Solution]] | ||
Revision as of 16:16, 22 January 2008
The relying party enablement code has been architected to support many different authentication protocols and can be implemented on many different application container platforms. The package org.eclipse.higgins.rp.interface contains all the interfaces needed for an API, SPI and other common utility functions.
Authentication protocols are implemented through Authentication Protocol Handlers. There should be a new project for each authentication protocol supported. Currently, the only supported authentication protocol handler is the Information Card authentication protocol handler. The authentication protocol handlers depend on a set of SPIs to handle the platform specific implementation. There should be no platform dependent code written into any of the authentication protocol handlers.
Relying Party applications can be configured to use one of the plaform specific implementations and one authentication protocol handler. In the future the code will support applications that want to give users a choice of authentication protocols to gain access to the application.