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

doc/testing/testplan/api_auditing_service/README.md

+63 −63
Original line number Diff line number Diff line
@@ -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**:

doc/testing/testplan/api_discover_service/README.md

+57 −57
Original line number Diff line number Diff line
@@ -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.

doc/testing/testplan/api_events_service/README.md

+15 −15

File changed.

Preview size limit exceeded, changes collapsed.

doc/testing/testplan/api_invoker_management/README.md

+15 −15

File changed.

Preview size limit exceeded, changes collapsed.

doc/testing/testplan/api_logging_service/README.md

+27 −27

File changed.

Preview size limit exceeded, changes collapsed.