Skip to content

Commit

Permalink
Updating mandatory ICM text (#21)
Browse files Browse the repository at this point in the history
  • Loading branch information
RandyLevensalor authored Aug 9, 2024
1 parent 2bda9e7 commit c891a94
Showing 1 changed file with 4 additions and 10 deletions.
14 changes: 4 additions & 10 deletions code/API_definitions/network_access_management.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -50,19 +50,13 @@ info:
# API Functionality
This API allows API clients to manage isolated networks and reboot network access devices.
## Authorization and authentication
### Authorization and authentication
[Camara Security and Interoperability Profile](https://github.com/camaraproject/IdentityAndConsentManagement/blob/main/documentation/CAMARA-Security-Interoperability.md)
provides details on how a client requests an access token.
The "Camara Security and Interoperability Profile" provides details on how a client requests an access token. Please refer to Identify and Consent Management (https://github.com/camaraproject/IdentityAndConsentManagement/) for the released version of the Profile.
Which specific authorization flows are to be used will be determined during onboarding process, happening between
the API Client and the Telco Operator exposing the API, taking into account the declared purpose for accessing the
API, while also being subject to the prevailing legal framework dictated by local legislation.
Which specific authorization flows are to be used will be determined during onboarding process, happening between the API Client and the Telco Operator exposing the API, taking into account the declared purpose for accessing the API, while also being subject to the prevailing legal framework dictated by local legislation.
It is important to remark that in cases where personal user 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 3-legged access tokens becomes mandatory.
This measure ensures that the API remains in strict compliance with user privacy preferences and regulatory
obligations, upholding the principles of transparency and user-centric data control.
It is important to remark that in cases where personal user 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 3-legged access tokens becomes mandatory. This measure ensures that the API remains in strict compliance with user privacy preferences and regulatory obligations, upholding the principles of transparency and user-centric data control.
### Scopes
Scopes are used to protect the service owner's information and privacy. The general format is
Expand Down

0 comments on commit c891a94

Please sign in to comment.