Skip to content
Snippets Groups Projects
Commit e51a6044 authored by Jorge Moratinos's avatar Jorge Moratinos
Browse files

Updated bold texts and some other minor standarization issues with tests plan

parent 6e393011
No related branches found
No related tags found
1 merge request!12Resolve "Change order of sections in tests to improve readability"
......@@ -16,29 +16,29 @@ At this documentation you will have all information and related files and exampl
* Invoker exist in CAPIF
* Log Entry exist in CAPIF
**Execution Steps**:
1. Register Provider and Invoker CCF
2. Publish Service
3. Create Log Entry
4. Get Log Entry
**Information of Test**:
1. Perform [provider onboarding], [invoker onboarding]
2. Publish Service API at CCF:
- Send Post to ccf_publish_url https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis
- body [service api description] with apiName service_1
- Use APF Certificate
- Send **POST** to ccf_publish_url **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis**
- body [service api description] with apiName **service_1**
- Use **APF Certificate**
3. Create Log Entry:
- Send POST to *https://{CAPIF_HOSTNAME}/api-invocation-logs/v1/{aefId}/logs*
- Send **POST** to **https://{CAPIF_HOSTNAME}/api-invocation-logs/v1/{aefId}/logs**
- body [log entry request body]
- Use AEF Certificate
- Use **AEF Certificate**
4. Get Log:
1. Send GET to *https://{CAPIF_HOSTNAME}/logs/v1/apiInvocationLogs?aef-id={aefId}&api-invoker-id={api-invoker-id}*
2. Use AMF Certificate
**Execution Steps**:
1. Register Provider and Invoker CCF
2. Publish Service
3. Create Log Entry
4. Get Log Entry
1. Send **GET** to **https://{CAPIF_HOSTNAME}/logs/v1/apiInvocationLogs?aef-id={aefId}&api-invoker-id={api-invoker-id}**
2. Use **AMF Certificate**
**Expected Result**:
......@@ -63,23 +63,23 @@ At this documentation you will have all information and related files and exampl
* Service exist in CAPIF
* Invoker exist in CAPIF
**Execution Steps**:
1. Register Provider and Invoker CCF
2. Publish Service
3. Get Log Entry
**Information of Test**:
1. Perform [provider onboarding], [invoker onboarding]
2. Publish Service API at CCF:
- Send Post to ccf_publish_url https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis
- body [service api description] with apiName service_1
- Use APF Certificate
4. Get Log:
1. Send GET to *https://{CAPIF_HOSTNAME}/logs/v1/apiInvocationLogs?aef-id={aefId}&api-invoker-id={api-invoker-id}*
2. Use AMF Certificate
- Send **POST** to ccf_publish_url **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis**
- body [service api description] with apiName **service_1**
- Use **APF Certificate**
**Execution Steps**:
1. Register Provider and Invoker CCF
2. Publish Service
3. Get Log Entry
3. Get Log:
1. Send **GET** to **https://{CAPIF_HOSTNAME}/logs/v1/apiInvocationLogs?aef-id={aefId}&api-invoker-id={api-invoker-id}**
2. Use **AMF Certificate**
**Expected Result**:
......@@ -106,29 +106,29 @@ At this documentation you will have all information and related files and exampl
* Invoker exist in CAPIF
* Log Entry exist in CAPIF
**Execution Steps**:
1. Register Provider and Invoker CCF
2. Publish Service
3. Create Log Entry
4. Get Log Entry
**Information of Test**:
1. Perform [provider onboarding], [invoker onboarding]
2. Publish Service API at CCF:
- Send Post to ccf_publish_url https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis
- body [service api description] with apiName service_1
- Use APF Certificate
- Send **POST** to ccf_publish_url **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis**
- body [service api description] with apiName **service_1**
- Use **APF Certificate**
3. Create Log Entry:
- Send POST to *https://{CAPIF_HOSTNAME}/api-invocation-logs/v1/{aefId}/logs*
- Send **POST** to **https://{CAPIF_HOSTNAME}/api-invocation-logs/v1/{aefId}/logs**
- body [log entry request body]
- Use AEF Certificate
- Use **AEF Certificate**
4. Get Log:
1. Send GET to *https://{CAPIF_HOSTNAME}/logs/v1/apiInvocationLogs
2. Use AMF Certificate
**Execution Steps**:
1. Register Provider and Invoker CCF
2. Publish Service
3. Create Log Entry
4. Get Log Entry
1. Send **GET** to **https://{CAPIF_HOSTNAME}/logs/v1/apiInvocationLogs**
2. Use **AMF Certificate**
**Expected Result**:
......@@ -156,29 +156,29 @@ At this documentation you will have all information and related files and exampl
* Invoker exist in CAPIF
* Log Entry exist in CAPIF
**Execution Steps**:
1. Register Provider and Invoker CCF
2. Publish Service
3. Create Log Entry
4. Get Log Entry
**Information of Test**:
1. Perform [provider onboarding], [invoker onboarding]
2. Publish Service API at CCF:
- Send Post to ccf_publish_url https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis
- body [service api description] with apiName service_1
- Use APF Certificate
- Send **POST** to ccf_publish_url **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis**
- body [service api description] with apiName **service_1**
- Use **APF Certificate**
3. Create Log Entry:
- Send POST to *https://{CAPIF_HOSTNAME}/api-invocation-logs/v1/{aefId}/logs*
- Send **POST** to **https://{CAPIF_HOSTNAME}/api-invocation-logs/v1/{aefId}/logs**
- body [log entry request body]
- Use AEF Certificate
- Use **AEF Certificate**
4. Get Log:
1. Send GET to *https://{CAPIF_HOSTNAME}/logs/v1/apiInvocationLogs?aef-id={aefId}&api-invoker-id={api-invoker-id}&api-version={v1}*
2. Use AMF Certificate
**Execution Steps**:
1. Register Provider and Invoker CCF
2. Publish Service
3. Create Log Entry
4. Get Log Entry
1. Send **GET** to **https://{CAPIF_HOSTNAME}/logs/v1/apiInvocationLogs?aef-id={aefId}&api-invoker-id={api-invoker-id}&api-version={v1}**
2. Use **AMF Certificate**
**Expected Result**:
......@@ -205,29 +205,29 @@ At this documentation you will have all information and related files and exampl
* Invoker exist in CAPIF
* Log Entry exist in CAPIF
**Execution Steps**:
1. Register Provider and Invoker CCF
2. Publish Service
3. Create Log Entry
4. Get Log Entry
**Information of Test**:
1. Perform [provider onboarding], [invoker onboarding]
2. Publish Service API at CCF:
- Send Post to ccf_publish_url https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis
- body [service api description] with apiName service_1
- Use APF Certificate
- Send **POST** to ccf_publish_url **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis**
- body [service api description] with apiName **service_1**
- Use **APF Certificate**
3. Create Log Entry:
- Send POST to *https://{CAPIF_HOSTNAME}/api-invocation-logs/v1/{aefId}/logs*
- Send **POST** to **https://{CAPIF_HOSTNAME}/api-invocation-logs/v1/{aefId}/logs**
- body [log entry request body]
- Use AEF Certificate
- Use **AEF Certificate**
4. Get Log:
1. Send GET to *https://{CAPIF_HOSTNAME}/logs/v1/apiInvocationLogs?aef-id={aefId}&api-invoker-id={api-invoker-id}&api-version={v58}*
2. Use AMF Certificate
**Execution Steps**:
1. Register Provider and Invoker CCF
2. Publish Service
3. Create Log Entry
4. Get Log Entry
1. Send **GET** to **https://{CAPIF_HOSTNAME}/logs/v1/apiInvocationLogs?aef-id={aefId}&api-invoker-id={api-invoker-id}&api-version={v58}**
2. Use **AMF Certificate**
**Expected Result**:
......
......@@ -19,13 +19,13 @@ At this documentation you will have all information and related files and exampl
1. Perform [Provider Registration] and [Invoker Onboarding]
2. Publish Service API at CCF:
* Send Post to ccf_publish_url *https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis*
* body [service api description] with apiName service_1
* Use APF Certificate
* Send **POST** to ccf_publish_url **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis**
* body [service api description] with apiName **service_1**
* Use **APF Certificate**
3. Request Discover Published APIs:
* Send GET to *https://{CAPIF_HOSTNAME}/service-apis/v1/allServiceAPIs?api-invoker-id={apiInvokerId}*
* Send **GET** to **https://{CAPIF_HOSTNAME}/service-apis/v1/allServiceAPIs?api-invoker-id={apiInvokerId}**
* Param api-invoker-id is mandatory
* Use Invoker Certificate
* Use **Invoker Certificate**
**Execution Steps**:
......@@ -39,14 +39,14 @@ At this documentation you will have all information and related files and exampl
1. **201 Created**
2. Response Body must follow **ServiceAPIDescription** data structure with:
* apiId
3. Response Header **Location** must be received with URI to new resource created, following this structure: *{apiRoot}/published-apis/v1/{apfId}/service-apis/{serviceApiId}*
3. Response Header **Location** must be received with URI to new resource created, following this structure: **{apiRoot}/published-apis/v1/{apfId}/service-apis/{serviceApiId}**
2. Response to Onboard request must accomplish:
1. **201 Created**
2. Response Body must follow **APIInvokerEnrolmentDetails** data structure with:
* apiInvokerId
* onboardingInformation->apiInvokerCertificate must contain the public key signed.
3. Response Header **Location** must be received with URI to new resource created, following this structure: *{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}*
3. Response Header **Location** must be received with URI to new resource created, following this structure: **{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}**
3. Response to Discover Request By Invoker:
1. **200 OK** response.
2. Response body must follow **DiscoveredAPIs** data structure:
......@@ -69,13 +69,13 @@ At this documentation you will have all information and related files and exampl
1. Perform [Provider Registration] and [Invoker Onboarding]
2. Publish Service API at CCF:
* Send Post to ccf_publish_url *https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis*
* body [service api description] with apiName service_1
* Use APF Certificate
* Send **POST** to ccf_publish_url **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis**
* body [service api description] with apiName **service_1**
* Use **APF Certificate**
3. Request Discover Published APIs by no invoker entity:
* Send GET to *https://{CAPIF_HOSTNAME}/service-apis/v1/allServiceAPIs?api-invoker-id={apiInvokerId}*
* Send **GET** to **https://{CAPIF_HOSTNAME}/service-apis/v1/allServiceAPIs?api-invoker-id={apiInvokerId}**
* Param api-invoker-id is mandatory
* Use not Invoker Certificate
* Use not **Invoker Certificate**
**Execution Steps**:
......@@ -89,14 +89,14 @@ At this documentation you will have all information and related files and exampl
1. **201 Created**
2. Response Body must follow **ServiceAPIDescription** data structure with:
* apiId
3. Response Header **Location** must be received with URI to new resource created, following this structure: *{apiRoot}/published-apis/v1/{apfId}/service-apis/{serviceApiId}*
3. Response Header **Location** must be received with URI to new resource created, following this structure: **{apiRoot}/published-apis/v1/{apfId}/service-apis/{serviceApiId}**
2. Response to Onboard request must accomplish:
1. **201 Created**
2. Response Body must follow **APIInvokerEnrolmentDetails** data structure with:
* apiInvokerId
* onboardingInformation->apiInvokerCertificate must contain the public key signed.
3. Response Header **Location** must be received with URI to new resource created, following this structure: *{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}*
3. Response Header **Location** must be received with URI to new resource created, following this structure: **{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}**
3. Response to Discover Request By no invoker entity:
1. **401 Unauthorized**
......@@ -123,13 +123,13 @@ At this documentation you will have all information and related files and exampl
1. Perform [Provider Registration] and [Invoker Onboarding]
2. Publish Service API at CCF:
* Send Post to ccf_publish_url *https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis*
* body [service api description] with apiName service_1
* Use APF Certificate
* Send **POST** to ccf_publish_url **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis**
* body [service api description] with apiName **service_1**
* Use **APF Certificate**
3. Request Discover Published APIs with not valid apiInvoker:
* Send GET to *https://{CAPIF_HOSTNAME}/service-apis/v1/allServiceAPIs?api-invoker-id={INVOKER_NOT_REGISTERED}*
* Send **GET** to **https://{CAPIF_HOSTNAME}/service-apis/v1/allServiceAPIs?api-invoker-id={INVOKER_NOT_REGISTERED}**
* Param api-invoker-id is mandatory
* Using invoker certificate
* Using **Invoker Certificate**
**Execution Steps**:
......@@ -143,14 +143,14 @@ At this documentation you will have all information and related files and exampl
1. **201 Created**
2. Response Body must follow **ServiceAPIDescription** data structure with:
* apiId
3. Response Header **Location** must be received with URI to new resource created, following this structure: *{apiRoot}/published-apis/v1/{apfId}/service-apis/{serviceApiId}*
3. Response Header **Location** must be received with URI to new resource created, following this structure: **{apiRoot}/published-apis/v1/{apfId}/service-apis/{serviceApiId}**
2. Response to Onboard request must accomplish:
1. **201 Created**
2. Response Body must follow **APIInvokerEnrolmentDetails** data structure with:
* apiInvokerId
* onboardingInformation->apiInvokerCertificate must contain the public key signed.
3. Response Header **Location** must be received with URI to new resource created, following this structure: *{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}*
3. Response Header **Location** must be received with URI to new resource created, following this structure: **{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}**
3. Response to Discover Request By Invoker:
1. **404 Not Found**
......@@ -179,25 +179,25 @@ At this documentation you will have all information and related files and exampl
1. Perform [Provider Registration] and [Invoker Onboarding]
2. Publish Service API at CCF:
* Send Post to ccf_publish_url *https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis*
* body [service api description] with apiName service_1
* Use APF Certificate
* Send **POST** to ccf_publish_url **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis**
* body [service api description] with apiName **service_1**
* Use **APF Certificate**
3. Publish Service API at CCF:
* Send Post to ccf_publish_url *https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis*
* body [service api description] with apiName service_2
* Use APF Certificate
* Send **POST** to ccf_publish_url **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis**
* body [service api description] with apiName **service_2**
* Use **APF Certificate**
4. Request Discover Published APIs filtering by api-name:
* Send GET to ccf_discover_url *https://{CAPIF_HOSTNAME}/service-apis/v1/allServiceAPIs?api-invoker-id={apiInvokerId}&api-name=service_1*
* Send **GET** to ccf_discover_url **https://{CAPIF_HOSTNAME}/service-apis/v1/allServiceAPIs?api-invoker-id={apiInvokerId}&api-name=**service_1**
* Param api-invoker-id is mandatory
* Using invoker certificate
* filter by api-name service_1
* Using **Invoker Certificate**
* filter by api-name **service_1**
**Execution Steps**:
1. Register Provider at CCF, store certificates and Publish Service API service_1 and service_2 at CCF
1. Register Provider at CCF, store certificates and Publish Service API **service_1** and **service_2** at CCF
2. Register Invoker and Onboard Invoker at CCF
3. Discover Service APIs by Invoker.
4. Discover filtered by api-name service_1 Service APIs by Invoker
4. Discover filtered by api-name **service_1** Service APIs by Invoker
**Expected Result**:
......@@ -205,13 +205,13 @@ At this documentation you will have all information and related files and exampl
1. **201 Created**
2. Response Body must follow **ServiceAPIDescription** data structure with:
* apiId
3. Response Header **Location** must be received with URI to new resource created, following this structure: *{apiRoot}/published-apis/v1/{apfId}/service-apis/{serviceApiId}*
3. Response Header **Location** must be received with URI to new resource created, following this structure: **{apiRoot}/published-apis/v1/{apfId}/service-apis/{serviceApiId}**
2. Response to Onboard request must accomplish:
1. **201 Created**
2. Response Body must follow **APIInvokerEnrolmentDetails** data structure with:
* apiInvokerId
* onboardingInformation->apiInvokerCertificate must contain the public key signed.
3. Response Header **Location** must be received with URI to new resource created, following this structure: *{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}*
3. Response Header **Location** must be received with URI to new resource created, following this structure: **{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}**
3. Response to Discover Request By Invoker:
1. **200 OK** response.
2. Response body must follow **DiscoveredAPIs** data structure:
......@@ -219,7 +219,7 @@ At this documentation you will have all information and related files and exampl
4. Response to Discover Request By Invoker:
1. **200 OK** response.
2. Response body must follow **DiscoveredAPIs** data structure:
* Check if DiscoveredAPIs contains only Service API published with api-name service_1
* Check if DiscoveredAPIs contains only Service API published with api-name **service_1**
## Test Case 5: Discover Published service APIs by registered API Invoker filtered with no match
......@@ -240,22 +240,22 @@ At this documentation you will have all information and related files and exampl
1. Perform [Provider Registration] and [Invoker Onboarding]
2. Publish Service API at CCF:
* Send Post to ccf_publish_url *https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis*
* body [service api description] with apiName service_1
* Use APF Certificate
* Send **POST** to ccf_publish_url **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis**
* body [service api description] with apiName **service_1**
* Use **APF Certificate**
3. Publish Service API at CCF:
* Send Post to ccf_publish_url *https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis*
* body [service api description] with apiName service_2
* Use APF Certificate
* Send **POST** to ccf_publish_url **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis**
* body [service api description] with apiName **service_2**
* Use **APF Certificate**
4. Request Discover Published APIs filtering by api-name not published:
* Send GET to ccf_discover_url *https://{CAPIF_HOSTNAME}/service-apis/v1/allServiceAPIs?api-invoker-id={apiInvokerId}&api-name=NOT_VALID_NAME*
* Send **GET** to ccf_discover_url **https://{CAPIF_HOSTNAME}/service-apis/v1/allServiceAPIs?api-invoker-id={apiInvokerId}&api-name=NOT_VALID_NAME**
* Param api-invoker-id is mandatory
* Using invoker certificate
* Using **Invoker Certificate**
* filter by api-name NOT_VALID_NAME
**Execution Steps**:
1. Register Provider at CCF, store certificates and Publish Service API service_1 and service_2 at CCF
1. Register Provider at CCF, store certificates and Publish Service API **service_1** and **service_2** at CCF
2. Register Invoker and Onboard Invoker at CCF
3. Discover Service APIs by Invoker.
4. Discover filtered by api-name not published Service APIs by Invoker
......@@ -266,13 +266,13 @@ At this documentation you will have all information and related files and exampl
1. **201 Created**
2. Response Body must follow **ServiceAPIDescription** data structure with:
* apiId
3. Response Header **Location** must be received with URI to new resource created, following this structure: *{apiRoot}/published-apis/v1/{apfId}/service-apis/{serviceApiId}*
3. Response Header **Location** must be received with URI to new resource created, following this structure: **{apiRoot}/published-apis/v1/{apfId}/service-apis/{serviceApiId}**
2. Response to Onboard request must accomplish:
1. **201 Created**
2. Response Body must follow **APIInvokerEnrolmentDetails** data structure with:
* apiInvokerId
* onboardingInformation->apiInvokerCertificate must contain the public key signed.
3. Response Header **Location** must be received with URI to new resource created, following this structure: *{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}*
3. Response Header **Location** must be received with URI to new resource created, following this structure: **{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}**
3. Response to Discover Request By Invoker:
1. **200 OK** response.
2. Response body must follow **DiscoveredAPIs** data structure:
......@@ -304,21 +304,21 @@ At this documentation you will have all information and related files and exampl
1. Perform [Provider Registration] and [Invoker Onboarding]
2. Publish Service API at CCF:
* Send Post to ccf_publish_url *https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis*
* body [service api description] with apiName service_1
* Use APF Certificate
* Send **POST** to ccf_publish_url **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis**
* body [service api description] with apiName **service_1**
* Use **APF Certificate**
3. Publish Service API at CCF:
* Send Post to ccf_publish_url *https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis*
* body [service api description] with apiName service_2
* Use APF Certificate
* Send **POST** to ccf_publish_url **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis**
* body [service api description] with apiName **service_2**
* Use **APF Certificate**
4. Request Discover Published APIs not filtered:
* Send GET to ccf_discover_url *https://{CAPIF_HOSTNAME}/service-apis/v1/allServiceAPIs?api-invoker-id={apiInvokerId}*
* Send **GET** to ccf_discover_url **https://{CAPIF_HOSTNAME}/service-apis/v1/allServiceAPIs?api-invoker-id={apiInvokerId}**
* Param api-invoker-id is mandatory
* Using invoker certificate
* Using **Invoker Certificate**
**Execution Steps**:
1. Register Provider at CCF, store certificates and Publish Service API service_1 and service_2 at CCF
1. Register Provider at CCF, store certificates and Publish Service API **service_1** and **service_2** at CCF
2. Register Invoker and Onboard Invoker at CCF
3. Discover Service APIs by Invoker.
4. Discover without filter by Invoker
......@@ -329,14 +329,14 @@ At this documentation you will have all information and related files and exampl
1. **201 Created**
2. Response Body must follow **ServiceAPIDescription** data structure with:
* apiId
3. Response Header **Location** must be received with URI to new resource created, following this structure: *{apiRoot}/published-apis/v1/{apfId}/service-apis/{serviceApiId}*
3. Response Header **Location** must be received with URI to new resource created, following this structure: **{apiRoot}/published-apis/v1/{apfId}/service-apis/{serviceApiId}**
2. Response to Onboard request must accomplish:
1. **201 Created**
2. Response Body must follow **APIInvokerEnrolmentDetails** data structure with:
* apiInvokerId
* onboardingInformation->apiInvokerCertificate must contain the public key signed.
3. Response Header **Location** must be received with URI to new resource created, following this structure: *{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}*
3. Response Header **Location** must be received with URI to new resource created, following this structure: **{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}**
3. Response to Discover Request By Invoker:
1. **200 OK** response.
......
......@@ -189,7 +189,7 @@ At this documentation you will have all information and related files and exampl
2. Response to Event Subscription must accomplish:
1. 201 Created
2. The URI of the created resource shall be returned in the "Location" HTTP header, following this structure: *{apiRoot}/capif-events/{apiVersion}/{subscriberId}/subscriptions/{subscriptionId}
2. The URI of the created resource shall be returned in the "Location" HTTP header, following this structure: **{apiRoot}/capif-events/{apiVersion}/{subscriberId}/subscriptions/{subscriptionId}**
3. Response Body must follow **EventSubscription** data structure.
3. Event Subscriptions are stored in CAPIF Database
......@@ -226,12 +226,12 @@ At this documentation you will have all information and related files and exampl
1. Perform [Invoker Onboarding]
2. Event Subscription:
1. Send **POST** to https://{CAPIF_HOSTNAME}/capif-events/v1/{subscriberId}/subscriptions
1. Send **POST** to **https://{CAPIF_HOSTNAME}/capif-events/v1/{subscriberId}/subscriptions**
2. body [event subscription request body]
3. Use **Invoker Certificate**
3. Remove Event Subcription with not valid subscriber:
1. Send **DELETE** to to https://{CAPIF_HOSTNAME}/capif-events/v1/{subcriberId}/subscriptions/{SUBSCRIPTION_ID_NOT_VALID}
1. Send **DELETE** to to **https://{CAPIF_HOSTNAME}/capif-events/v1/{subcriberId}/subscriptions/{SUBSCRIPTION_ID_NOT_VALID}**
2. Use **Invoker Certificate**
**Expected Result**:
......@@ -263,7 +263,7 @@ At this documentation you will have all information and related files and exampl
**Description**:
This test case will check that a CAPIF Invoker subscribed to SERVICE_API_INVOCATION_SUCCESS and SERVICE_API_INVOCATION_FAILURE, receive the notification when AEF send to logging service result of invocations to their APIs.
This test case will check that a CAPIF Invoker subscribed to SERVICE_API_INVOCATION_SUCCESS and SERVICE_API_INVOCATION_FAILURE, receive the notification when AEF Send **TO** logging service result of invocations to their APIs.
**Pre-Conditions**:
......@@ -290,7 +290,7 @@ At this documentation you will have all information and related files and exampl
* Send **POST** to ccf_publish_url **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis**
* body [service api description] with apiName **service_1**
* Store **serviceApiId**
* Use APF Certificate
* Use **APF Certificate**
3. Perform [invoker onboarding]
4. Discover published APIs:
......@@ -312,7 +312,7 @@ At this documentation you will have all information and related files and exampl
3. apiId of published API
4. apiName of published API
5. 200 and 400 results in two logs.
3. Use AEF Certificate
3. Use **AEF Certificate**
**Expected Result**:
......@@ -399,8 +399,8 @@ At this documentation you will have all information and related files and exampl
2. Mock Server received messages must accomplish:
1. **Two Events have been received**.
2. Validate received events follow **EventNotification** data structure, with **apiIds** in **eventDetail** parameter.
1. One should be **SERVICE_API_AVAILABLE** apiId of service_2 published API.
2. The other one must be **SERVICE_API_UNAVAILABLE** apiId of service_1 published API.
1. One should be **SERVICE_API_AVAILABLE** apiId of **service_2** published API.
2. The other one must be **SERVICE_API_UNAVAILABLE** apiId of **service_1** published API.
---
## Test Case 8: Invoker subscribe to Service API Update
......@@ -453,7 +453,7 @@ At this documentation you will have all information and related files and exampl
7. Update published API at CCF:
* Send **PUT** to resource URL **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis/{serivceApiId}**
* body [service api description] with overrided **apiName** to **service_1_modified**
* body [service api description] with overrided **apiName** to **service_1**_modified**
* Use **APF Certificate**
**Expected Result**:
......@@ -465,7 +465,7 @@ At this documentation you will have all information and related files and exampl
2. Response to Update Published Service API:
1. **200 OK**
2. Response Body must follow **ServiceAPIDescription** data structure with:
* apiName **service_1_modified**
* apiName **service_1**_modified**
3. Mock Server received messages must accomplish:
1. **One Event has been received**.
2. Validate received events follow **EventNotification** data structure, with **serviceAPIDescriptions** in **eventDetail** parameter.
......@@ -578,7 +578,7 @@ At this documentation you will have all information and related files and exampl
6. Create Security Context for Invoker
* Send **PUT** **https://{CAPIF_HOSTNAME}/trustedInvokers/{apiInvokerId}**
* body [service security body]
* Use Invoker Certificate
* Use **Invoker Certificate**
7. Provider Retrieve ACL
* Send **GET** **https://{CAPIF_HOSTNAME}/access-control-policy/v1/accessControlPolicyList/${serviceApiId}?aef-id=${aef_id}**
* Use **serviceApiId** and **aefId**
......@@ -648,14 +648,14 @@ At this documentation you will have all information and related files and exampl
6. Create Security Context for Invoker
* Send **PUT** **https://{CAPIF_HOSTNAME}/trustedInvokers/{apiInvokerId}**
* body [service security body]
* Use Invoker Certificate
* Use **Invoker Certificate**
7. Provider Retrieve ACL
* Send **GET** **https://{CAPIF_HOSTNAME}/access-control-policy/v1/accessControlPolicyList/${serviceApiId}?aef-id=${aef_id}**
* Use **serviceApiId** and **aefId**
* Use **AEF Provider Certificate**
3. Delete Security Context of Invoker by Provider:
* Send **DELETE** **https://{CAPIF_HOSTNAME}/trustedInvokers/{apiInvokerId}**
* Use **AEF certificate**
* Use **AEF Certificate**
**Expected Result**:
......@@ -721,11 +721,11 @@ At this documentation you will have all information and related files and exampl
6. Create Security Context for Invoker
* Send **PUT** **https://{CAPIF_HOSTNAME}/trustedInvokers/{apiInvokerId}**
* body [service security body]
* Use Invoker Certificate
* Use **Invoker Certificate**
7. Revoke Authorization by Provider:
* Send **POST** **https://{CAPIF_HOSTNAME}/trustedInvokers/{apiInvokerId}/delete**
* body [security notification body]
* Using AEF Certificate.
* Using **AEF Certificate**.
**Expected Result**:
......
......@@ -26,10 +26,10 @@ At this documentation you will have all information and related files and exampl
* Retrieve **access_token** and the urls needed for next requests from response body [user_getauth_response_body_example]
3. Onboard Invoker:
* Send POST to *https://{CAPIF_HOSTNAME}/api-invoker-management/v1/onboardedInvokers*
* Send **POST** to **https://{CAPIF_HOSTNAME}/api-invoker-management/v1/onboardedInvokers**
* Reference Request Body: [invoker onboarding body]
* "onboardingInformation"->"apiInvokerPublicKey": must contain public key generated by Invoker.
* Send at Authorization Header the Bearer access_token obtained previously (Authorization:Bearer ${access_token})
* Send in Authorization Header the Bearer access_token obtained previously (Authorization:Bearer ${access_token})
**Execution Steps**:
......@@ -44,7 +44,7 @@ At this documentation you will have all information and related files and exampl
2. Response Body must follow **APIInvokerEnrolmentDetails** data structure with:
* apiInvokerId
* onboardingInformation->apiInvokerCertificate must contain the public key signed.
3. Response Header **Location** must be received with URI to new resource created, following this structure: *{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}*
3. Response Header **Location** must be received with URI to new resource created, following this structure: **{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}**
## Test Case 2: Onboard NetApp Already onboarded
......@@ -65,10 +65,10 @@ At this documentation you will have all information and related files and exampl
1. Perform [Invoker Onboarding]
2. Repeat Onboard Invoker:
* Send POST to *https://{CAPIF_HOSTNAME}/api-invoker-management/v1/onboardedInvokers*
* Send **POST** to **https://{CAPIF_HOSTNAME}/api-invoker-management/v1/onboardedInvokers**
* Reference Request Body: [invoker onboarding body]
* "onboardingInformation"->"apiInvokerPublicKey": must contain public key generated by Invoker.
* Send at Authorization Header the Bearer access_token obtained previously (Authorization:Bearer ${access_token})
* Send in Authorization Header the Bearer access_token obtained previously (Authorization:Bearer ${access_token})
**Execution Steps**:
......@@ -84,7 +84,7 @@ At this documentation you will have all information and related files and exampl
2. Response Body must follow **APIInvokerEnrolmentDetails** data structure with:
* apiInvokerId
* onboardingInformation->apiInvokerCertificate must contain the public key signed.
3. Response Header **Location** must be received with URI to new resource created, following this structure: *{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}*
3. Response Header **Location** must be received with URI to new resource created, following this structure: **{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}**
2. Response to Second Onboard of NetApp must accomplish:
1. **403 Forbidden**
2. Error Response Body must accomplish with **ProblemDetails** data structure with:
......@@ -112,7 +112,7 @@ At this documentation you will have all information and related files and exampl
1. Perform [Invoker Onboarding]
2. Update information of previously onboarded Invoker:
* Send PUT to *https://{CAPIF_HOSTNAME}/api-invoker-management/v1/onboardedInvokers/{onboardingId}*
* Send **PUT** to **https://{CAPIF_HOSTNAME}/api-invoker-management/v1/onboardedInvokers/{onboardingId}**
* Reference Request Body is: [put invoker onboarding body]
* "notificationDestination": "*http://host.docker.internal:8086/netapp_new_callback*",
......@@ -130,7 +130,7 @@ At this documentation you will have all information and related files and exampl
2. Response Body must follow **APIInvokerEnrolmentDetails** data structure with:
* apiInvokerId
* onboardingInformation->apiInvokerCertificate must contain the public key signed.
3. Response Header **Location** must be received with URI to new resource created, following this structure: *{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}*
3. Response Header **Location** must be received with URI to new resource created, following this structure: **{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}**
2. Response to Update Request (PUT) with minor change must contain:
1. **200 OK** response.
2. notificationDestination on response must contain the new value
......@@ -154,7 +154,7 @@ At this documentation you will have all information and related files and exampl
1. Perform [Invoker Onboarding]
2. Update information of not onboarded Invoker:
* Send PUT to *https://{CAPIF_HOSTNAME}/api-invoker-management/v1/onboardedInvokers/{INVOKER_NOT_REGISTERED}*
* Send **PUT** to **https://{CAPIF_HOSTNAME}/api-invoker-management/v1/onboardedInvokers/{INVOKER_NOT_REGISTERED}**
* Reference Request Body is: [put invoker onboarding body]
**Execution Steps**:
......@@ -195,7 +195,7 @@ At this documentation you will have all information and related files and exampl
1. Perform [Invoker Onboarding]
2. Offboard:
* Send Delete to *https://{CAPIF_HOSTNAME}/api-invoker-management/v1/onboardedInvokers/{onboardingId}*
* Send **DELETE** to **https://{CAPIF_HOSTNAME}/api-invoker-management/v1/onboardedInvokers/{onboardingId}**
**Execution Steps**:
......@@ -229,7 +229,7 @@ At this documentation you will have all information and related files and exampl
1. Perform [Invoker Onboarding]
2. Offboard:
* Send Delete to *https://{CAPIF_HOSTNAME}/api-invoker-management/v1/onboardedInvokers/{INVOKER_NOT_REGISTERED}*
* Send **DELETE** to **https://{CAPIF_HOSTNAME}/api-invoker-management/v1/onboardedInvokers/{INVOKER_NOT_REGISTERED}**
**Execution Steps**:
......@@ -266,16 +266,16 @@ At this documentation you will have all information and related files and exampl
2. Create {public_key_2}
3. Update information of previously onboarded Invoker:
* Send PUT to *https://{CAPIF_HOSTNAME}/api-invoker-management/v1/onboardedInvokers/{onboardingId}*
* Send **PUT** to **https://{CAPIF_HOSTNAME}/api-invoker-management/v1/onboardedInvokers/{onboardingId}**
* Reference Request Body is: [put invoker onboarding body]
* ["onboardingInformation"]["apiInvokerPublicKey"]: {public_key_2},
* Store new certificate.
4. Update information of previously onboarded Invoker Using new certificate:
* Send PUT to *https://{CAPIF_HOSTNAME}/api-invoker-management/v1/onboardedInvokers/{onboardingId}*
* Send **PUT** to **https://{CAPIF_HOSTNAME}/api-invoker-management/v1/onboardedInvokers/{onboardingId}**
* Reference Request Body is: [put invoker onboarding body]
* "notificationDestination": "*http://host.docker.internal:8086/netapp_new_callback*",
* Use new invoker certificate
* Use new **Invoker Certificate**
**Execution Steps**:
......@@ -292,7 +292,7 @@ At this documentation you will have all information and related files and exampl
2. Response Body must follow **APIInvokerEnrolmentDetails** data structure with:
* apiInvokerId
* onboardingInformation->apiInvokerCertificate must contain the public key signed.
3. Response Header **Location** must be received with URI to new resource created, following this structure: *{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}*
3. Response Header **Location** must be received with URI to new resource created, following this structure: **{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}**
2. Response to Update Request (PUT) with new public key:
1. **200 OK** response.
2. apiInvokerCertificate with new certificate on response -> store to use.
......
......@@ -20,14 +20,14 @@ At this documentation you will have all information and related files and exampl
1. Perform [provider onboarding] and [invoker onboarding]
2. Publish Service API at CCF:
- Send Post to ccf_publish_url https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis
- body [service api description] with apiName service_1
- Use APF Certificate
- Send **POST** to ccf_publish_url **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis**
- body [service api description] with apiName **service_1**
- Use **APF Certificate**
3. Log Entry:
1. Send POST to *https://{CAPIF_HOSTNAME}/api-invocation-logs/v1/{aefId}/logs*
1. Send **POST** to **https://{CAPIF_HOSTNAME}/api-invocation-logs/v1/{aefId}/logs**
2. body [log entry request body]
3. Use AEF Certificate
3. Use **AEF Certificate**
**Execution Steps**:
1. Register Provider and Invoker CCF
......@@ -42,7 +42,7 @@ At this documentation you will have all information and related files and exampl
* aefId
* apiInvokerId
* logs
3. Response Header **Location** must be received with URI to new resource created, following this structure: *{apiRoot}/api-invocation-logs/v1/{aefId}/logs/{logId}*
3. Response Header **Location** must be received with URI to new resource created, following this structure: **{apiRoot}/api-invocation-logs/v1/{aefId}/logs/{logId}**
......@@ -66,14 +66,14 @@ At this documentation you will have all information and related files and exampl
1. Perform [provider onboarding] and [invoker onboarding]
2. Publish Service API at CCF:
- Send Post to ccf_publish_url https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis
- body [service api description] with apiName service_1
- Use APF Certificate
- Send **POST** to ccf_publish_url **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis**
- body [service api description] with apiName **service_1**
- Use **APF Certificate**
3. Log Entry:
1. Send POST to *https://{CAPIF_HOSTNAME}/api-invocation-logs/v1/{not-valid-aefId}/logs*
1. Send **POST** to **https://{CAPIF_HOSTNAME}/api-invocation-logs/v1/{not-valid-aefId}/logs**
2. body [log entry request body]
3. Use AEF Certificate
3. Use **AEF Certificate**
**Execution Steps**:
1. Register Provider and Invoker CCF
......@@ -107,14 +107,14 @@ At this documentation you will have all information and related files and exampl
1. Perform [provider onboarding] and [invoker onboarding]
2. Publish Service API at CCF:
- Send Post to ccf_publish_url https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis
- body [service api description] with apiName service_1
- Use APF Certificate
- Send **POST** to ccf_publish_url **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis**
- body [service api description] with apiName **service_1**
- Use **APF Certificate**
3. Log Entry:
1. Send POST to *https://{CAPIF_HOSTNAME}/api-invocation-logs/v1/{aefId}/logs*
1. Send **POST** to **https://{CAPIF_HOSTNAME}/api-invocation-logs/v1/{aefId}/logs**
2. body [log entry request body with serviceAPI apiName apiId not valid]
3. Use AEF Certificate
3. Use **AEF Certificate**
**Execution Steps**:
1. Register Provider and Invoker CCF
......@@ -150,14 +150,14 @@ At this documentation you will have all information and related files and exampl
1. Perform [provider onboarding] and [invoker onboarding]
2. Publish Service API at CCF:
- Send Post to ccf_publish_url https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis
- body [service api description] with apiName service_1
- Use APF Certificate
- Send **POST** to ccf_publish_url **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis**
- body [service api description] with apiName **service_1**
- Use **APF Certificate**
3. Log Entry:
1. Send POST to *https://{CAPIF_HOSTNAME}/api-invocation-logs/v1/{aefId}/logs*
1. Send **POST** to **https://{CAPIF_HOSTNAME}/api-invocation-logs/v1/{aefId}/logs**
2. body [log entry request body with invokerId not valid]
3. Use AEF Certificate
3. Use **AEF Certificate**
**Execution Steps**:
1. Register Provider and Invoker CCF
......@@ -172,7 +172,7 @@ At this documentation you will have all information and related files and exampl
3. For each **apiProvFuncs**, we must check:
1. **apiProvFuncId** is set
2. **apiProvCert** under **regInfo** is set properly
5. Location Header must contain the new resource URL *{apiRoot}/api-provider-management/v1/registrations/{registrationId}*
5. Location Header must contain the new resource URL **{apiRoot}/api-provider-management/v1/registrations/{registrationId}**
2. Response to Logging Service must accomplish:
1. **404 Not Found**
......@@ -204,14 +204,14 @@ At this documentation you will have all information and related files and exampl
1. Perform [provider onboarding] and [invoker onboarding]
2. Publish Service API at CCF:
- Send Post to ccf_publish_url https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis
- body [service api description] with apiName service_1
- Use APF Certificate
- Send **POST** to ccf_publish_url **https://{CAPIF_HOSTNAME}/published-apis/v1/{apfId}/service-apis**
- body [service api description] with apiName **service_1**
- Use **APF Certificate**
3. Log Entry:
1. Send POST to *https://{CAPIF_HOSTNAME}/api-invocation-logs/v1/{aefId}/logs*
1. Send **POST** to **https://{CAPIF_HOSTNAME}/api-invocation-logs/v1/{aefId}/logs**
2. body [log entry request body with bad aefId]
3. Use AEF Certificate
3. Use **AEF Certificate**
**Execution Steps**:
1. Register Provider and Invoker CCF
......
......@@ -25,7 +25,7 @@ At this documentation you will have all information and related files and exampl
3. Register Provider:
* Send POST *https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations*
* Send **POST** **https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations**
* body [provider request body]
* Authentication Bearer with access_token
* Store each cert in a file with according name.
......@@ -43,7 +43,7 @@ At this documentation you will have all information and related files and exampl
3. For each **apiProvFuncs**, we must check:
1. **apiProvFuncId** is set
2. **apiProvCert** under **regInfo** is set properly
5. Location Header must contain the new resource URL *{apiRoot}/api-provider-management/v1/registrations/{registrationId}*
5. Location Header must contain the new resource URL **{apiRoot}/api-provider-management/v1/registrations/{registrationId}**
## Test Case 2: Register Api Provider Already registered
......@@ -69,7 +69,7 @@ At this documentation you will have all information and related files and exampl
3. Register Provider:
* Send POST *https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations*
* Send **POST** **https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations**
* body [provider request body]
* Authentication Bearer with access_token
* Store each cert in a file with according name.
......@@ -118,14 +118,14 @@ At this documentation you will have all information and related files and exampl
3. Register Provider:
* Send POST *https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations*
* Send **POST** **https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations**
* body [provider request body]
* Authentication Bearer with access_token
* Get Resource URL from Location
4. Update Provider:
* Send PUT to Resource URL returned at registration *https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations/{registrationId}*
* Send **PUT** to Resource URL returned at registration **https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations/{registrationId}**
* body [provider request body] with apiProvDomInfo set to ROBOT_TESTING_MOD
* Use AMF Certificate.
......@@ -141,7 +141,7 @@ At this documentation you will have all information and related files and exampl
1. Register Provider:
1. **201 Created** response.
2. body returned must accomplish **APIProviderEnrolmentDetails** data structure.
3. Location Header must contain the new resource URL *{apiRoot}/api-provider-management/v1/registrations/{registrationId}*
3. Location Header must contain the new resource URL **{apiRoot}/api-provider-management/v1/registrations/{registrationId}**
2. Update Provider:
......@@ -174,14 +174,14 @@ At this documentation you will have all information and related files and exampl
3. Register Provider:
* Send POST *https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations*
* Send **POST** **https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations**
* body [provider request body]
* Authentication Bearer with access_token
* Store each cert in a file with according name.
4. Update Not Registered Provider:
* Send PUT *https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations/{API_PROVIDER_NOT_REGISTERED}*
* Send **PUT** **https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations/{API_PROVIDER_NOT_REGISTERED}**
* body [provider request body]
* Use AMF Certificate.
......@@ -198,7 +198,7 @@ At this documentation you will have all information and related files and exampl
* status 404
* title with message "Not Found"
* detail with message "Not Exist Provider Enrolment Details".
* cause with message "Not found registrations to send this api provider details".
* cause with message "Not found registrations to Send **THIS** api provider details".
## Test Case 5: Partially Update Registered Api Provider
......@@ -224,14 +224,14 @@ At this documentation you will have all information and related files and exampl
3. Register Provider:
* Send POST *https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations*
* Send **POST** **https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations**
* body [provider request body]
* Authentication Bearer with access_token
* Store each cert in a file with according name.
4. Partial update provider:
* Send PATCH *https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations/{registrationId}*
* Send **PATCH** **https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations/{registrationId}**
* body [provider request patch body]
* Use AMF Certificate.
......@@ -272,14 +272,14 @@ At this documentation you will have all information and related files and exampl
3. Register Provider:
* Send POST *https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations*
* Send **POST** **https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations**
* body [provider request body]
* Authentication Bearer with access_token
* Store each cert in a file with according name.
4. Partial update Provider:
* Send PATCH *https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations/{API_API_PROVIDER_NOT_REGISTERED}*
* Send **PATCH** **https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations/{API_API_PROVIDER_NOT_REGISTERED}**
* body [provider request patch body]
* Use AMF Certificate.
......@@ -299,7 +299,7 @@ At this documentation you will have all information and related files and exampl
* status 404
* title with message "Not Found"
* detail with message "Not Exist Provider Enrolment Details".
* cause with message "Not found registrations to send this api provider details".
* cause with message "Not found registrations to Send **THIS** api provider details".
## Test Case 7: Delete Registered Api Provider
......@@ -325,14 +325,14 @@ At this documentation you will have all information and related files and exampl
3. Register Provider:
* Send POST *https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations*
* Send **POST** **https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations**
* body [provider request body]
* Authentication Bearer with access_token
* Store each cert in a file with according name.
4. Delete registered provider:
* Send DELETE *https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations/{registrationId}*
* Send **DELETE** **https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations/{registrationId}**
* Use AMF Certificate.
**Execution Steps**:
......@@ -370,14 +370,14 @@ At this documentation you will have all information and related files and exampl
3. Register Provider:
* Send POST *https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations*
* Send **POST** **https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations**
* body [provider request body]
* Authentication Bearer with access_token
* Store each cert in a file with according name.
4. Delete registered provider at Provider Management:
* Send DELETE *https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations/{API_PROVIDER_NOT_REGISTERED}*
* Send **DELETE** **https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations/{API_PROVIDER_NOT_REGISTERED}**
* Use AMF Certificate.
**Execution Steps**:
......@@ -393,7 +393,7 @@ At this documentation you will have all information and related files and exampl
* status 404
* title with message "Not Found"
* detail with message "Not Exist Provider Enrolment Details".
* cause with message "Not found registrations to send this api provider details".
* cause with message "Not found registrations to Send **THIS** api provider details".
[provider request body]: ./provider_details_post_example.json "API Provider Enrolment Request"
......
This diff is collapsed.
This diff is collapsed.
......@@ -51,7 +51,7 @@ The steps to register a new user at Register Service are:
* Send **POST** to **https://{CAPIF_HOSTNAME}/api-invoker-management/v1/onboardedInvokers**
* Reference Request Body: [invoker onboarding body]
* "onboardingInformation"->"apiInvokerPublicKey": must contain public key generated by Invoker.
* Send at Authorization Header the Bearer access_token obtained previously (Authorization:Bearer ${access_token})
* Send in Authorization Header the Bearer access_token obtained previously (Authorization:Bearer ${access_token})
### Checks to ensure onboarding
......@@ -64,7 +64,7 @@ The steps to register a new user at Register Service are:
2. Response Body must follow **APIInvokerEnrolmentDetails** data structure with:
* apiInvokerId
* onboardingInformation->apiInvokerCertificate must contain the public key signed.
3. Response Header **Location** must be received with URI to new resource created, following this structure: *{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}*
3. Response Header **Location** must be received with URI to new resource created, following this structure: **{apiRoot}/api-invoker-management/{apiVersion}/onboardedInvokers/{onboardingId}**
### Example Flow
![Flow](../../../images/flows/07_Invoker_Onboarding.png)
......@@ -81,9 +81,9 @@ The steps to register a new user at Register Service are:
3. Register Provider:
* Send POST *https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations*
* Send **POST** **https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations**
* body [provider request body]
* Send at Authorization Header the Bearer access_token obtained previously (Authorization:Bearer ${access_token})
* Send in Authorization Header the Bearer access_token obtained previously (Authorization:Bearer ${access_token})
* Store each cert in a file with according name.
### Checks to ensure provider registration
......@@ -100,7 +100,7 @@ The steps to register a new user at Register Service are:
3. For each **apiProvFuncs**, we must check:
1. **apiProvFuncId** is set
2. **apiProvCert** under **regInfo** is set properly
4. Location Header must contain the new resource URL *{apiRoot}/api-provider-management/v1/registrations/{registrationId}*
4. Location Header must contain the new resource URL **{apiRoot}/api-provider-management/v1/registrations/{registrationId}**
### Example Flow
![Flow](../../../images/flows/07_Invoker_Onboarding.png)
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment