Repository navigation
Update UML flows #116
Description
Activity
Following last meeting discussion, proposal should follow:
- Not to include a new UML since CAMARA is only dedicated to provide API specification, integration with additional scenarios is part of the
- To include note stating that the current UML is only example and that indirect scenarios are also considered/allowed:
Note that the diagram shows just an example of a direct integration from developer's application and MNO's authserver and API, other scenarios of indirect integration via Aggregator/Channel Partner should also be considered. Specific authorization flows may apply, as defined by e.g. GSMA OGW
- Include reference to those auth diagrams when published by GSMA(expected in september)
@ECORMAC is this ok for you?
@jgarciahospital, your suggestion is good, a note indicating that the current UML is only an example and that indirect scenarios are also consided/allowed will clear up some confusion.
- added a commit that references this issue
on Sep 5, 2024
Problem description
The UML flows do not show an aggregator / channel partner (https://github.com/camaraproject/NumberVerification/blob/main/documentation/API_documentation/assets/uml_v0.3.jpg). Flows were created related to the securing the authorize endpoint using mechs in RFC 9101 (see issue#93: #93) which included an aggregator. This issue has been put on hold due to ICM deciding to not include aspects related to RFC 9101 in the Fall meta release.
Expected action
Update existing UML flows to also show aggregator.
Additional context