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 "Org.eclipse.higgins.iss"
(→Overview) |
(→Service) |
||
| Line 4: | Line 4: | ||
==Service== | ==Service== | ||
* [[ISS API]] | * [[ISS API]] | ||
| − | * Requirement: | + | * Requirement: ISS need to run in both normal and headless modes. Headless mode means that a web or rich client UI is not available, and that all (if any) matching i-cards should be returned based on a given "input" policy |
| + | |||
==See Also== | ==See Also== | ||
* [[ISS Web UI]] | * [[ISS Web UI]] | ||
Revision as of 16:01, 16 October 2006
Overview
ISS negotiates between relying party and identity provider(s) in order for the user to gain access to the services at the relying party. It does this by finding matches between the claims required by policy of the relying party and the claims in available i-cards. As controlled by the policy on these i-cards it uses the ISS UI & HBX Support component to provide a consistent user interface for the selection and release of claims under the supervision of the user. It keeps track of which relying sites and/or services to which the user has released Digital Identities and/or other identity information.
Service
- ISS API
- Requirement: ISS need to run in both normal and headless modes. Headless mode means that a web or rich client UI is not available, and that all (if any) matching i-cards should be returned based on a given "input" policy