Skip to content

Commit 243cfdb

Browse files
authored
Merge pull request #213 from camaraproject/fix207&209
Remove sequence diagram image in the yaml and instead refer to ICM
2 parents 432dde8 + e66502b commit 243cfdb

File tree

1 file changed

+8
-21
lines changed

1 file changed

+8
-21
lines changed

code/API_definitions/number-verification.yaml

Lines changed: 8 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,9 @@ info:
2424
2525
# The Authentication Request
2626
27+
**For NumberVerification the API provider guarantees that there is no user interaction.** Would user interaction be needed the authorization server returns an error.
28+
Authentication methods such as SMS OTP or user/password are incompatible, as the goal is to validate the mobile phone number that is accessing the App.
29+
2730
## Authentication Request with a temporary token
2831
2932
If the API Consumer has a TS.43 temporary token created on the mobile device then this API works over all connections e.g. WiFi taking advantage of the SIM-Based authentication.
@@ -38,6 +41,9 @@ info:
3841
If the API Consumer does not have a TS.43 temporary token then the API Consumer must use OpenId Connect Authorization Code Flow as described in the current release of [CAMARA APIs Access and User Consent Management](https://github.com/camaraproject/IdentityAndConsentManagement).
3942
For this method of authentication to work, the device must be connected to the mobile network.
4043
44+
The API Consumer should use the request parameter prompt=none in the Authentication Request, as described in **[OIDC Connect](https://openid.net/specs/openid-connect-core-1_0.html#AuthRequest)**, ensuring no user interaction.
45+
The API Provider implies the request parameter prompt=none in the Authentication Request for this API.
46+
4147
# Resources and Operations overview
4248
4349
This API currently provides two endpoints which both require a **3-legged token** obtained by using one of the two methods indicated in _The Authentication Request_ section. This therefore **excludes** using, for example, SMS/OTP or user/password as an authentication method:
@@ -46,25 +52,6 @@ info:
4652
It compares the received phone number with the user's phone number associated to the access token in order to respond **true/false**.
4753
- The /device-phone-number endpoint returns the phone number associated by the network operator with the SIM in the end user's device.
4854
49-
# Sequence Diagram
50-
51-
The following sequence diagram shows an example of a direct integration into the developer's application and the API Provider's Authorization Server and API for the case that no temporary token is available.
52-
53-
![UML Sequence Diagram](https://raw.githubusercontent.com/camaraproject/NumberVerification/r2.4/documentation/API_documentation/assets/uml_v0.3.jpg)
54-
55-
**Implementation Details:**
56-
57-
- **(1):** Authentication must be automatic without any user interactions.
58-
Authentication methods such as SMS OTP or user/password are incompatible, as the goal is to validate the mobile phone number that is accessing the App.
59-
60-
The API Consumer should use the request parameter prompt=none in the Authentication Request, as described in **[OIDC Connect](https://openid.net/specs/openid-connect-core-1_0.html#AuthRequest)**, ensuring no user interaction.
61-
62-
The API Provider implies the request parameter prompt=none in the Authentication Request for this API.
63-
64-
- **(2):** The way in which the phone number is retrieved depends upon the implementation.
65-
For example, the access token may be a self-contained encrypted JWT, and so the API provider can decrypt and identify phone number directly from the access token.
66-
Other implementations might retrieve the phone number associated with the access token from their Authorization Server.
67-
6855
# Authorization and authentication
6956
7057
The "Camara Security and Interoperability Profile" provides details of how an API consumer requests an access token. Please refer to [Identity and Consent Management](https://github.com/camaraproject/IdentityAndConsentManagement/) for the released version of the profile.
@@ -83,7 +70,7 @@ info:
8370
8471
As a specific rule, error `501 - NOT_IMPLEMENTED` can be only a possible error response if it is explicitly documented in the API.
8572
86-
version: 2.1.0-rc.1
73+
version: wip
8774
x-camara-commonalities: 0.6
8875
license:
8976
name: Apache 2.0
@@ -92,7 +79,7 @@ externalDocs:
9279
description: Project documentation at CAMARA
9380
url: https://github.com/camaraproject/NumberVerification
9481
servers:
95-
- url: '{apiRoot}/number-verification/v2rc1'
82+
- url: '{apiRoot}/number-verification/vwip'
9683
variables:
9784
apiRoot:
9885
default: http://localhost:9091

0 commit comments

Comments
 (0)