https://wiki.idesg.org/index.php?action=history&feed=atom&title=Example_Login_ScenarioExample Login Scenario - Revision history2026-05-11T03:53:40ZRevision history for this page on the wikiMediaWiki 1.38.4https://wiki.idesg.org/index.php?title=Example_Login_Scenario&diff=1985&oldid=prevOmaerz: 4 revisions imported: Initial Upload of old pages from IDESG Wiki2018-06-28T03:52:23Z<p>4 revisions imported: Initial Upload of old pages from IDESG Wiki</p>
<p><b>New page</b></p><div>== Example Login Scenario ==<br />
'''Scenario Name''': Using a digital identity to log into an RP<br />
<br />
'''Scenario Description''': User wants to either create an account and an RP or wants to login to an existing account at the RP. RP provides a list of IdPs that it trusts, user selects an IdP. RP redirects the user to the selected IdP's login site, user enters their previously created identity and credential. IdP validates the credential and redirects the user to the RP's site with an identifier that uniquely identifies this user at the IdP.<br />
<br />
'''Corresponds to''': Interactions C and D in [[Example|Example scenario]]<br />
<br />
[[File:Example_LoginScenario.png|700px|Example login scenario]]<br />
<br />
=== Interaction Details ===<br />
More detailed description for the interactions are<br />
<br />
<br />
==== A. User visits RP site, wants to login or open/create an account ====<br />
Parties involved: <br />
Direction of the interaction:<br />
Data: <br />
Sub-scenario: none<br />
<br />
===== Security Considerations =====<br />
===== Privacy Considerations =====<br />
===== Standards Considerations =====<br />
===== UX Considerations =====<br />
===== Policy Considerations =====<br />
<br />
==== B. RP shows a list of IdPs it trusts ====<br />
Parties involved: <br />
Direction of the interaction:<br />
Data: <br />
Sub-scenario: none<br />
<br />
===== Security Considerations =====<br />
===== Privacy Considerations =====<br />
===== Standards Considerations =====<br />
===== UX Considerations =====<br />
===== Policy Considerations =====<br />
<br />
==== C. User selects one IdP ====<br />
Parties involved: <br />
Direction of the interaction:<br />
Data: <br />
Sub-scenario: none<br />
<br />
===== Security Considerations =====<br />
===== Privacy Considerations =====<br />
===== Standards Considerations =====<br />
===== UX Considerations =====<br />
===== Policy Considerations =====<br />
<br />
==== D. RP redirects user to IdP ====<br />
Parties involved: <br />
Direction of the interaction:<br />
Data: <br />
Sub-scenario: none<br />
<br />
===== Security Considerations =====<br />
===== Privacy Considerations =====<br />
===== Standards Considerations =====<br />
===== UX Considerations =====<br />
===== Policy Considerations =====<br />
<br />
==== E. User enters their identity and credential ====<br />
Parties involved: <br />
Direction of the interaction:<br />
Data: <br />
Sub-scenario: none<br />
<br />
===== Security Considerations =====<br />
===== Privacy Considerations =====<br />
===== Standards Considerations =====<br />
===== UX Considerations =====<br />
===== Policy Considerations =====<br />
<br />
==== F. IdP validates identity/credential combination, redirects user to RP along with a unique identifier for the user ====<br />
Parties involved: <br />
Direction of the interaction:<br />
Data: <br />
Sub-scenario: none<br />
<br />
===== Security Considerations =====<br />
===== Privacy Considerations =====<br />
===== Standards Considerations =====<br />
===== UX Considerations =====<br />
===== Policy Considerations =====<br />
<br />
==== G. RP receives unique identifier from IdP ====<br />
Parties involved: <br />
Direction of the interaction:<br />
Data: <br />
Sub-scenario: none<br />
<br />
===== Security Considerations =====<br />
===== Privacy Considerations =====<br />
===== Standards Considerations =====<br />
===== UX Considerations =====<br />
===== Policy Considerations =====<br />
<br />
==== G1. RP stores the unique identifier from IdP in its database (maps to its own account identifier) ====<br />
Parties involved: <br />
Direction of the interaction:<br />
Data: <br />
Sub-scenario: none<br />
<br />
===== Security Considerations =====<br />
===== Privacy Considerations =====<br />
===== Standards Considerations =====<br />
===== UX Considerations =====<br />
===== Policy Considerations =====<br />
<br />
==== H. RP logs user into their account ====<br />
Parties involved: <br />
Direction of the interaction:<br />
Data: <br />
Sub-scenario: none<br />
<br />
===== Security Considerations =====<br />
===== Privacy Considerations =====<br />
===== Standards Considerations =====<br />
===== UX Considerations =====<br />
===== Policy Considerations =====</div>Omaerz