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

ISS Browser UI Use Cases

ISSB1 – Signon to a website that supports CardSpaceTM as an authentication mechanism from a MacOS machine using a self asserted i-card (e.g. login-in name and password, no STS involved)

ISSB2 – Signon to a website that supports CardSpace as an authentication mechanism from a MacOS machine using a managed i-card ,where the the user does not need to provide additional informaino in order to get the token.

ISSB3 – Signon to a website that supports CardSpace as an authentication mechanism from a MacOS machine using a managed i-card ,where a name and password are required in order to get the token.

ISSB4 – Signon to a website that supports CardSpace as an authentication mechanism from a Linux machine using a managed i-card ,where a name and password are required in order to get the token.

ISSB5 - Signonto a website that supports OpenID as an authentication mechanism.

ISSB6 - Signonto a website that supports CardSpace as an authentication mechanism, the card contains name and age. A token is generated that specifies that the person is over 21. Provide mechanism that determines when this cashed token can be reused.

ISSB7 – Signon to a website that supports CardSpace as an authentication mechanism from a Windows Vista machine using a self issued i-card

ISSB8 – Signon to a website that supports CardSpace as an authentication mechanism from a Windows Vista machine using a managed i-card

ISSB9 – John has CardSpace authenticated accounts on his employer’s employee benefits system and a dating service. When he points his browser to his employer’s website, he needs to choose the correct i-card for authentication from among his i-cards supporting CardSpace authentication.

ISSB10 – John is a Second Life enthusiast. He visits Second Life multiple times a day. Second Life uses a simple user name/password authentication mechanism. The next time John points his browser to Second Life, he is automatically authenticated and logged in. John doesn’t want to have to choose from among all his i-cards that use name/password authentication each time he visits Second Life.

ISSB11 – The global software company Jane works for has problems with piracy. In order to access her project’s CVS system, she needs to provide both a user name and password and enter a number from her RSA security key fob.

ISSB12 – Jane’s job and social life style require her to access hundreds of different systems each week. These systems in turn utilize a dozen different authentication methods. When she points her browser to a site that authenticates using user name and password, she has 25 different i-cards that could potentially satisfy the site’s authentication challenge. She quickly navigates to and selects the correct card

ISSB13 – Jane’s job and social life style require her to access hundreds of different systems each week. These systems in turn utilize a dozen different authentication methods. When she points her browser for the first time to a site that authenticates using user name and password, though she has 25 different i-cards that could potentially satisfy the site’s authentication challenge, the system automatically creates a new card with a unique password so that if her account at this site is compromised, she doesn’t compromise any of her other accounts usihng this authentication method.

Back to the top