Skip to content

Commit

Permalink
fixed linting errors
Browse files Browse the repository at this point in the history
  • Loading branch information
maheshc01 committed Nov 11, 2024
1 parent 9bc7abe commit 271930a
Showing 1 changed file with 29 additions and 10 deletions.
39 changes: 29 additions & 10 deletions code/API_definitions/Application-endpoint-registration.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -6,17 +6,36 @@ info:
name: Apache 2.0
url: https://www.apache.org/licenses/LICENSE-2.0.html
description: |
Application endpoint registration allows application developers to register
one or more Application Endpoints, and retrieve, update,and delete those registrations.
This information can we used for various usecases like optimal end point discovery to help end users connect to the most most optimal instance of the application. Addtionally the information can be used to also monitor the different instance to take decisions from a lifecycle mangement perspective.
Application endpoint registration allows application developers to

Check failure on line 9 in code/API_definitions/Application-endpoint-registration.yaml

View workflow job for this annotation

GitHub Actions / MegaLinter

9:71 [trailing-spaces] trailing spaces
register one or more Application Endpoints, and retrieve, update,and

Check failure on line 10 in code/API_definitions/Application-endpoint-registration.yaml

View workflow job for this annotation

GitHub Actions / MegaLinter

10:73 [trailing-spaces] trailing spaces
delete those egistrations.
This information can we used for various usecases like optimal end

Check failure on line 13 in code/API_definitions/Application-endpoint-registration.yaml

View workflow job for this annotation

GitHub Actions / MegaLinter

13:71 [trailing-spaces] trailing spaces
point discovery to help end users connect to the most most optimal

Check failure on line 14 in code/API_definitions/Application-endpoint-registration.yaml

View workflow job for this annotation

GitHub Actions / MegaLinter

14:71 [trailing-spaces] trailing spaces
instance of the application. Addtionally the information can be used

Check failure on line 15 in code/API_definitions/Application-endpoint-registration.yaml

View workflow job for this annotation

GitHub Actions / MegaLinter

15:73 [trailing-spaces] trailing spaces
to also monitor the different instance to take decisions from a lifecycle

Check failure on line 16 in code/API_definitions/Application-endpoint-registration.yaml

View workflow job for this annotation

GitHub Actions / MegaLinter

16:78 [trailing-spaces] trailing spaces
mangement perspective.
### Authorization and authentication
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.
The "Camara Security and Interoperability Profile" provides details on

Check failure on line 21 in code/API_definitions/Application-endpoint-registration.yaml

View workflow job for this annotation

GitHub Actions / MegaLinter

21:75 [trailing-spaces] trailing spaces
how a client requests an access token. Please refer to Identify and

Check failure on line 22 in code/API_definitions/Application-endpoint-registration.yaml

View workflow job for this annotation

GitHub Actions / MegaLinter

22:72 [trailing-spaces] trailing spaces
Consent Management

Check failure on line 23 in code/API_definitions/Application-endpoint-registration.yaml

View workflow job for this annotation

GitHub Actions / MegaLinter

23:23 [trailing-spaces] trailing spaces
(https://github.com/camaraproject/IdentityAndConsentManagement/)

Check failure on line 24 in code/API_definitions/Application-endpoint-registration.yaml

View workflow job for this annotation

GitHub Actions / MegaLinter

24:69 [trailing-spaces] trailing spaces
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.
x-camara-commonalities: 0.4.0

Expand Down Expand Up @@ -141,9 +160,9 @@ paths:
components:
securitySchemes:
openId:
description: OpenID Provider Configuration Information
type: openIdConnect
openIdConnectUrl: https://example.com/.well-known/openid-configuration
description: OpenID Provider Configuration Information
type: openIdConnect
openIdConnectUrl: https://example.com/.well-known/openid-configuration
headers:
x-correlator:
description: Correlation id for the different services
Expand Down Expand Up @@ -369,4 +388,4 @@ components:
example:
status: 503
code: UNAVAILABLE
message: "application unavailable"
message: "application unavailable"

0 comments on commit 271930a

Please sign in to comment.