-
Notifications
You must be signed in to change notification settings - Fork 21
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.
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
adding puml #24
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Dawid - This is helpful.
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} |
There was a problem hiding this comment.
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 ?
There was a problem hiding this comment.
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.
fixing typo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For me this is good pending @monamok point.
Thanks
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} |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good for me
uml sequence diagram for MC Number Verify