User-centric identity management using trusted modules

Using a Smartphone to Access Personalized Web Services on a Workstation

“…The architecture from [13] is used because it meets several security and privacy requirements. It allows for selective disclosure of attributes and their properties: these are only released if allowed by the access policy.…”

“…In addition, some identity management systems (e.g. [13], [1]) rely on the secure computing environment of trusted modules.…”

“…(c) the minimum revalidation time. The architecture in [13] provides a revocation strategy where every so often the trusted module contacts a trusted third party -the revalidation service, thereby revalidating itself. If the revocation status is OK, the revalidation time on the card is set to the current time.…”

“…For authentication and attribute assertion, the prototype uses the architecture presented in [13]. It is a privacy-friendly, user-centric federated identity management approach which relies on a trusted module.…”

“…This functionality is related to the identity management architecture presented in [13]. For instance, the application shows the user to which service provider the trusted module is about to authenticate.…”