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

Difference between revisions of "Identity Services Overview"

 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
 
 
__NOTOC__
 
__NOTOC__
 
 
[[Image:Higgins.juggle.PNG]]
 
[[Image:Higgins.juggle.PNG]]
 +
 +
The following IdP and RP solutions were developed for [[Higgins 1.0]] and/or planned for [[Higgins 1.1]]
  
 
== Identity Providers ==
 
== Identity Providers ==
  
* [[STS IdP]] - The STS IdP is a pluggable solution that issues information cards and creates claims tokens (credentials) for those cards. This extensible service is available as a complete deployable "solution". The WS-Trust IdP leverages the IdAS layer to plug into a variety of data sources. It can also be extended to support new token types and new network protocols by developing plugins to the framework itself.
+
The following sub-projects enable websites to issue i-cards.
  
* [[SAML2 IdP]] - supports the SP-initiated SSO profile and issues SAML 2.0 Assertions.
+
* [[STS IdP]] - The STS IdP is a pluggable solution that issues information cards and creates claims tokens (credentials) for those cards. This extensible service is available as a complete deployable "solution". The WS-Trust IdP leverages the IdAS layer to plug into a variety of data sources. It can also be extended to support new token types and new network protocols by developing plugins to the framework itself.
  
For Higgins 1.1, The [[SAML2 IdP]] had been enhanced so that in addition to authenticating users against a Higgins IdAS Context, it can also authenticate users with an information card. Note that it does not yet issue cards.
+
* [[SAML2 IdP 1.1]] - supports the SP-initiated SSO profile and issues SAML 2.0 Assertions. For Higgins 1.1, The [[SAML2 IdP]] had been enhanced so that in addition to authenticating users against a Higgins IdAS Context, it can also authenticate users with an information card. Note that it does not yet issue cards.
  
 
== RP Code ==
 
== RP Code ==
  
* [[Extensible Protocol RP Website 1.0]] - provides the Java code so that a web application can support authentication using an Information Card. The security token that is returned to the Relying Party site is verified and the identity attributes from the token are made available to the web application.
+
The following sub-project enables a website to accept i-cards for login and other purposes.
  
[[Category: Higgins Solutions]]
+
* [[Extensible Protocol RP Website 1.1]] - provides the Java code so that a web application can support authentication using an Information Card. The security token that is returned to the Relying Party site is verified and the identity attributes from the token are made available to the web application.

Latest revision as of 13:29, 20 August 2014

Higgins.juggle.PNG

The following IdP and RP solutions were developed for Higgins 1.0 and/or planned for Higgins 1.1

Identity Providers

The following sub-projects enable websites to issue i-cards.

  • STS IdP - The STS IdP is a pluggable solution that issues information cards and creates claims tokens (credentials) for those cards. This extensible service is available as a complete deployable "solution". The WS-Trust IdP leverages the IdAS layer to plug into a variety of data sources. It can also be extended to support new token types and new network protocols by developing plugins to the framework itself.
  • SAML2 IdP 1.1 - supports the SP-initiated SSO profile and issues SAML 2.0 Assertions. For Higgins 1.1, The SAML2 IdP had been enhanced so that in addition to authenticating users against a Higgins IdAS Context, it can also authenticate users with an information card. Note that it does not yet issue cards.

RP Code

The following sub-project enables a website to accept i-cards for login and other purposes.

  • Extensible Protocol RP Website 1.1 - provides the Java code so that a web application can support authentication using an Information Card. The security token that is returned to the Relying Party site is verified and the identity attributes from the token are made available to the web application.

Back to the top