User management service to enable the management of the user profile.
Story: User/Group Management and Microsoft SSO #3
Goal:
Allow a user to unmap an authentication identity from a user profile.
Actors:
- User
- System
Prerequisites:
- User "A" profile exists in the system and has relationship with identity "A" and identity "B".
- User "A" is authenticated in system.
Actions:
- User "A" selects "manage user profile" menu.
- System displays "manager user profile" menu.
- User "A" selects "manage mapped identities" menu item.
- System displays list of mapped identities with hyperlink to "delete identity" for each mapped identity.
- User "A" selects identity "B".
- System displays "delete confirmation" message.
- Users "A" selects confirm delete.
- System deletes identity "B".
Notes:
- The "manage mapped identities" menu item will only display if two or more identities have relationships with User "A".
- Creating a user profile will likely include storing user and authentication information, and storing each set of information in a database table makes the most sense. There is an expectation that an individual will have the opportunity to authenticate with multiple IdPs and will want the same user profile to be active regardless of IdP used to authenticate. It is, therefore, reasonable to have a relationship cardinality of
many auth entries to one user profile entry.
- An authentication identity can only be mapped to one user profile at a time.

Mockups:

User management service to enable the management of the user profile.
Story: User/Group Management and Microsoft SSO #3
Goal:
Allow a user to unmap an authentication identity from a user profile.
Actors:
Prerequisites:
Actions:
Notes:
many auth entriestoone user profile entry.Mockups: