Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adding puml #24

Merged
merged 3 commits into from
Mar 9, 2023
Merged

adding puml #24

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bcd6610
adding puml
DT-DawidWroblewski Feb 24, 2023
3f2bb47
Merge branch 'main' of https://github.com/DT-DawidWroblewski/NumberVe…
DT-DawidWroblewski Feb 24, 2023
4d22029
Update sequenceDiagram.puml
DT-DawidWroblewski Mar 8, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 37 additions & 0 deletions documentation/UML/sequenceDiagram.puml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
@startuml

title "MC Verified MSISDN"

actor "Mobile App\nCustomer" as user
box "Customer's Device"
participant "Developer's App" as mApp
end box

box "MC IDGW"
participant "/authorize" as auth
participant "/token" as token
participant "/userinfo" as userInfo
end box

activate user
user -> mApp: opens Developer's App
activate mApp
mApp -> auth: scope=openid mc_verified_msisdn\n&state={...}\n&{query params defined inside MC specs}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

About the scopes I was told in other working groups that we have to wait till we get into an agreements for scopes in commonalities so we avoid inconsistancy in CAMARA project. What do you think about this point @DT-DawidWroblewski @bigludo7 ?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For me when the scope has been already defined in the standard - Mobile Connect for example - we have to take it as such to avoid confusion for implementation knowing it. I guess this is the case here.

activate auth
auth -> auth: Verified\nMSISDN\nflow
note right: MNO detects device MSISDN\nusing mobile data session details
mApp <- auth: {code} (auth successful)
deactivate auth
mApp -> token: code={code}
activate token
mApp <- token: tokens {id_token, access_token}
deactivate token
mApp -> userInfo: access_token={access_token,msisdn}
activate userInfo
mApp <- userInfo: {"device_msisdn_verified": true}
deactivate userInfo
deactivate mApp
user <- mApp: user inside app


@enduml