Resources
- Identity Use Cases & Scenarios.
- FIDIS Deliverables.
- Identity of Identity.
- Interoperability.
- Profiling.
- Forensic Implications.
- HighTechID.
- D3.1: Overview on IMS.
- D3.2: A study on PKI and biometrics.
- D3.3: Study on Mobile Identity Management.
- D3.5: Workshop on ID-Documents.
- D3.6: Study on ID Documents.
- D3.7: A Structured Collection on RFID Literature.
- D3.8: Study on protocols with respect to identity and identification – an insight on network protocols and privacy-aware communication.
- D3.9: Study on the Impact of Trusted Computing on Identity and Identity Management.
- D3.10: Biometrics in identity management.
- D3.11: Report on the Maintenance of the IMS Database.
- D3.15: Report on the Maintenance of the ISM Database.
- D3.17: Identity Management Systems – recent developments.
- D12.1: Integrated Workshop on Emerging AmI Technologies.
- D12.2: Study on Emerging AmI Technologies.
- D12.3: A Holistic Privacy Framework for RFID Applications.
- D12.4: Integrated Workshop on Emerging AmI.
- D12.5: Use cases and scenarios of emerging technologies.
- D12.6: A Study on ICT Implants.
- D12.7: Identity-related Crime in Europe – Big Problem or Big Hype?.
- D12.10: Normality Mining: Results from a Tracking Study.
- Privacy and legal-social content.
- Mobility and Identity.
- Other.
- IDIS Journal.
- FIDIS Interactive.
- Press & Events.
- In-House Journal.
- Booklets
- Identity in a Networked World.
- Identity R/Evolution.
D3.9: Study on the Impact of Trusted Computing on Identity and Identity Management
Scenario Description
The scenario is based on the notions mentioned in section 8.4.3, but refers also to other parts of the deliverable. It emphasizes the need for cross identification of users between different identity domains.
Fig7: Identification across different Identifier Domains [140]
In this scenario, there exist two Identifier Domains, IDom1 and IDom2. In each identifier domain, there is a Service Provider (SP) and an Identity Provider (IP). The IP can issue identity credentials to a user who wants to gain access to the service inside the same identifier domain.
In principle, an SP in IDom1 can validate credentials that have been issued only by an IP inside the same IDom1. However, in certain business use cases, an SP in IDom2 should be also able to validate credentials issued by an IP in IDom2. For that, this SP should be able to verify the trustworthiness of the IP in IDom2, and whether the authentication policy allows this IP to issue this kind of credentials which are valid for both identifier domains.
30 / 38 |