Skip to content

Commit 271930a

Browse files
committed
fixed linting errors
1 parent 9bc7abe commit 271930a

File tree

1 file changed

+29
-10
lines changed

1 file changed

+29
-10
lines changed

code/API_definitions/Application-endpoint-registration.yaml

+29-10
Original file line numberDiff line numberDiff line change
@@ -6,17 +6,36 @@ info:
66
name: Apache 2.0
77
url: https://www.apache.org/licenses/LICENSE-2.0.html
88
description: |
9-
Application endpoint registration allows application developers to register
10-
one or more Application Endpoints, and retrieve, update,and delete those registrations.
11-
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.
9+
Application endpoint registration allows application developers to
10+
register one or more Application Endpoints, and retrieve, update,and
11+
delete those egistrations.
12+
13+
This information can we used for various usecases like optimal end
14+
point discovery to help end users connect to the most most optimal
15+
instance of the application. Addtionally the information can be used
16+
to also monitor the different instance to take decisions from a lifecycle
17+
mangement perspective.
1218
1319
### Authorization and authentication
1420
15-
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.
21+
The "Camara Security and Interoperability Profile" provides details on
22+
how a client requests an access token. Please refer to Identify and
23+
Consent Management
24+
(https://github.com/camaraproject/IdentityAndConsentManagement/)
25+
for the released version of the Profile.
1626
17-
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.
27+
Which specific authorization flows are to be used will be determined
28+
during onboarding process, happening between the API Client and the
29+
Telco Operator exposing the API, taking into account the declared
30+
purpose for accessing the API, while also being subject to the prevailing
31+
legal framework dictated by local legislation.
1832
19-
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.
33+
It is important to remark that in cases where personal user data
34+
is processed by the API, and users can exercise their rights through
35+
mechanisms such as opt-in and/or opt-out, the use of 3-legged access
36+
tokens becomes mandatory. This measure ensures that the API remains in
37+
strict compliance with user privacy preferences and regulatory obligations,
38+
upholding the principles of transparency and user-centric data control.
2039
2140
x-camara-commonalities: 0.4.0
2241

@@ -141,9 +160,9 @@ paths:
141160
components:
142161
securitySchemes:
143162
openId:
144-
description: OpenID Provider Configuration Information
145-
type: openIdConnect
146-
openIdConnectUrl: https://example.com/.well-known/openid-configuration
163+
description: OpenID Provider Configuration Information
164+
type: openIdConnect
165+
openIdConnectUrl: https://example.com/.well-known/openid-configuration
147166
headers:
148167
x-correlator:
149168
description: Correlation id for the different services
@@ -369,4 +388,4 @@ components:
369388
example:
370389
status: 503
371390
code: UNAVAILABLE
372-
message: "application unavailable"
391+
message: "application unavailable"

0 commit comments

Comments
 (0)