Skip to content
Open
Changes from all commits
Commits
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
4 changes: 4 additions & 0 deletions code/API_definitions/number-recycling.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,10 @@
In cases where personal data is processed by the API and users can exercise their rights through mechanisms such as opt-in and/or opt-out, the use of three-legged access tokens is mandatory. This ensures that the API remains in compliance with privacy regulations, upholding the principles of transparency and user-centric privacy-by-design.
<!-- CAMARA:MANDATORY:authorization-and-authentication:END -->

Note: If sending an authentication message in CIBA is based on the MSISDN and the MSISDN was reassigned to a new subscriber, then
this defeats the purpose of the number recycling API which is to determine whether the MSISDN was reassigned.
If the ASP and the CSP know at onboarding time that User consent is not needed, then JWT-Bearer-Flow with tel-prefix is recommended to be used with number recycling.

# Identifying the phone number from the access token

This API requires the API consumer to identify a phone number as the subject of the API as follows:
Expand Down Expand Up @@ -180,7 +184,7 @@
responses:
Generic200:
description: OK
headers:

Check warning on line 187 in code/API_definitions/number-recycling.yaml

View workflow job for this annotation

GitHub Actions / validation / Validate

Component may be unused

[S-211] Potentially unused component has been detected. | Suggestion: Remove the component if it is obsolete, or reference it from the API definition.
x-correlator:
$ref: '../common/CAMARA_common.yaml#/components/headers/x-correlator'
content:
Expand Down