How do you represent this Single Sign-On (SSO) picture using UML?
We can find an example of this kind on the Internet:
Here are the steps that happen if you want to access Trello by using your Google account:
- User requests access: Use the Trello login web page and select Google account as a login method.
- Redirection to IdP: Trello redirects the user to the Google login page.
- Login page served: The user is served with the Google login page.
- Credentials entered: The user enters their Google credentials.
- SSO Server verification: Google sends authentication info to the SSO Authorization server
- Authentication at IdP: The Authorization server returns the auth token (SAML) if the credentials are valid.
- Access granted: Google sends the auth token to the Trello
- Validate token: In the last step, Trello sends the token to the Google Authorization server to validate it
- Token valid: If the token is valid, Trello will allow access to the user and store the session for future interactions
- Allow access
Source: HOW DOES SINGLE SIGN-ON (SSO) WORK? – BY DR MILAN MILANOVIĆ
The author expressed this as a graphic as a diagram above.
In the attached document you will find this diagram expressed as a communication diagram, a sequence diagram and a component diagram.
SSO Model – UML Communications Diagram
Diagram above SSO Model – UML Communications Diagram id an UML version similar to original SSO Model by Milan Milanovic.
Communication Diagrams – Communication Diagrams show interactions through an architectural view where the arcs between the communicating Lifelines are decorated with description of the passed Messages and their sequencing.
3. SSO Model – UML Sequence Diagram
Sequence Diagrams – The most common variant is the Sequence Diagram that focuses on the Message interchange between a number of Lifelines.
4. SSO Model Architecture HLD – UML Component Diagram
The components that communicate with each other form the above architecture.
Comments are Closed