Skip to content
Snippets Groups Projects

Resolve "remove capif_api_acl-5 from testplan and reorder documentation"

Merged Resolve "remove capif_api_acl-5 from testplan and reorder documentation"
OCF-Doc41-remove-capif_api_acl-5-from-testplan-and-reorder-documentation into develop
Merged Jorge Moratinos requested to merge OCF-Doc41-remove-capif_api_acl-5-from-testplan-and-reorder-documentation into develop
Compare
and
2 files
+ 20
− 88
Compare changes
  • Side-by-side
  • Inline
Files
2
doc/testing/testplan/api_access_control_policy/README.md
+ 18
− 88
@@ -243,80 +243,10 @@ At this documentation you will have all information and related files and exampl
@@ -243,80 +243,10 @@ At this documentation you will have all information and related files and exampl
1. Contain one objects.
1. Contain one objects.
2. Object must match with **apiInvokerId2**.
2. Object must match with **apiInvokerId2**.
## Test Case 5: Retrieve ACL filtered by supported-features
**Test ID**: ***capif_api_acl-5***
## Test Case 5: Retrieve ACL with aef-id not valid
**Description**:
**CURRENTLY NOT SUPPORTED FEATURE**
This test case will check that an API Provider can retrieve ACL filtering by supportedFeatures from CAPIF containing 1 objects.
**Pre-Conditions**:
* API Provider had a Service API Published on CAPIF
* Two API Invokers had a Security Context for same Service API published by provider.
**Execution Steps**:
1. Register and onboard Provider at CCF.
2. Publish a provider API with name **service_1** and **service_2**
3. Register and onboard Invoker at CCF
4. Store signed Certificate
5. Create Security Context
6. Provider Get ACL information with query parameter indicating first supported-features.
7. Provider Get ACL information with query parameter indicating second supported-features.
**Information of Test**:
1. Perform [Provider Registration]
**Test ID**: ***capif_api_acl-5***
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**
* Store **serviceApiId**
* Use **APF Certificate**
3. Perform [Invoker Onboarding] store apiInvokerId
4. Discover published APIs
5. Create Security Context for this Invoker for both published APIs
* Send **PUT** **https://{CAPIF_HOSTNAME}/trustedInvokers/{apiInvokerId}**
* body [service security body]
* Use **Invoker Certificate**
6. Repeat previous 3 steps in order to have a new Invoker.
7. Provider Retrieve ACL for serviceApiId
* Send **GET** **https://{CAPIF_HOSTNAME}/access-control-policy/v1/accessControlPolicyList/${serviceApiId1}?aef-id=${aef_id}&supported-features={apiInvokerId1}**
* Use **serviceApiId**, **aefId** and **apiInvokerId1**
* Use **AEF Provider Certificate**
8. Provider Retrieve ACL for serviceApiId
* Send **GET** **https://{CAPIF_HOSTNAME}/access-control-policy/v1/accessControlPolicyList/${serviceApiId1}?aef-id=${aef_id}&supported-features={apiInvokerId2}**
* Use **serviceApiId**, **aefId** and **apiInvokerId2**
* Use **AEF Provider Certificate**
**Expected Result**:
1. ACL Response:
1. **200 OK** Response.
2. body returned must accomplish **AccessControlPolicyList** data structure.
3. **apiInvokerPolicies** must:
1. Contain one objects.
2. Object must match with supportedFeatures1.
2. ACL Response:
1. **200 OK** Response.
2. body returned must accomplish **AccessControlPolicyList** data structure.
3. **apiInvokerPolicies** must:
1. Contain one objects.
2. Object must match with supportedFeatures1.
## Test Case 6: Retrieve ACL with aef-id not valid
**Test ID**: ***capif_api_acl-6***
**Description**:
**Description**:
@@ -370,9 +300,9 @@ At this documentation you will have all information and related files and exampl
@@ -370,9 +300,9 @@ At this documentation you will have all information and related files and exampl
* cause with message "Wrong id".
* cause with message "Wrong id".
## Test Case 7: Retrieve ACL with service-id not valid
## Test Case 6: Retrieve ACL with service-id not valid
**Test ID**: ***capif_api_acl-7***
**Test ID**: ***capif_api_acl-6***
**Description**:
**Description**:
@@ -425,9 +355,9 @@ At this documentation you will have all information and related files and exampl
@@ -425,9 +355,9 @@ At this documentation you will have all information and related files and exampl
* detail with message "No ACLs found for the requested service: {service_api_id}, aef_id: {aef_id}, invoker: {api_invoker_id} and supportedFeatures: {supported_features}".
* detail with message "No ACLs found for the requested service: {service_api_id}, aef_id: {aef_id}, invoker: {api_invoker_id} and supportedFeatures: {supported_features}".
* cause with message "Wrong id".
* cause with message "Wrong id".
## Test Case 8: Retrieve ACL with service-api-id and aef-id not valid
## Test Case 7: Retrieve ACL with service-api-id and aef-id not valid
**Test ID**: ***capif_api_acl-8***
**Test ID**: ***capif_api_acl-7***
**Description**:
**Description**:
@@ -481,9 +411,9 @@ At this documentation you will have all information and related files and exampl
@@ -481,9 +411,9 @@ At this documentation you will have all information and related files and exampl
* cause with message "Wrong id".
* cause with message "Wrong id".
## Test Case 9: Retrieve ACL without SecurityContext created previously by Invoker
## Test Case 8: Retrieve ACL without SecurityContext created previously by Invoker
**Test ID**: ***capif_api_acl-9***
**Test ID**: ***capif_api_acl-8***
**Description**:
**Description**:
@@ -532,9 +462,9 @@ At this documentation you will have all information and related files and exampl
@@ -532,9 +462,9 @@ At this documentation you will have all information and related files and exampl
* detail with message "No ACLs found for the requested service: {NOT_VALID_SERVICE_API_ID}, aef_id: {AEF_ID_NOT_VALID}, invoker: {api_invoker_id} and supportedFeatures: {supported_features}".
* detail with message "No ACLs found for the requested service: {NOT_VALID_SERVICE_API_ID}, aef_id: {AEF_ID_NOT_VALID}, invoker: {api_invoker_id} and supportedFeatures: {supported_features}".
* cause with message "Wrong id".
* cause with message "Wrong id".
## Test Case 10: Retrieve ACL filtered by api-invoker-id not present
## Test Case 9: Retrieve ACL filtered by api-invoker-id not present
**Test ID**: ***capif_api_acl-10***
**Test ID**: ***capif_api_acl-9***
**Description**:
**Description**:
@@ -587,9 +517,9 @@ At this documentation you will have all information and related files and exampl
@@ -587,9 +517,9 @@ At this documentation you will have all information and related files and exampl
* detail with message "No ACLs found for the requested service: {NOT_VALID_SERVICE_API_ID}, aef_id: {AEF_ID_NOT_VALID}, invoker: {api_invoker_id} and supportedFeatures: {supported_features}".
* detail with message "No ACLs found for the requested service: {NOT_VALID_SERVICE_API_ID}, aef_id: {AEF_ID_NOT_VALID}, invoker: {api_invoker_id} and supportedFeatures: {supported_features}".
* cause with message "Wrong id".
* cause with message "Wrong id".
## Test Case 11: Retrieve ACL with APF Certificate
## Test Case 10: Retrieve ACL with APF Certificate
**Test ID**: ***capif_api_acl-11***
**Test ID**: ***capif_api_acl-10***
**Description**:
**Description**:
@@ -641,9 +571,9 @@ At this documentation you will have all information and related files and exampl
@@ -641,9 +571,9 @@ At this documentation you will have all information and related files and exampl
* detail with message "Role not authorized for this API route".
* detail with message "Role not authorized for this API route".
* cause with message "Certificate not authorized".
* cause with message "Certificate not authorized".
## Test Case 12: Retrieve ACL with AMF Certificate
## Test Case 11: Retrieve ACL with AMF Certificate
**Test ID**: ***capif_api_acl-12***
**Test ID**: ***capif_api_acl-11***
**Description**:
**Description**:
@@ -695,9 +625,9 @@ At this documentation you will have all information and related files and exampl
@@ -695,9 +625,9 @@ At this documentation you will have all information and related files and exampl
* detail with message "Role not authorized for this API route".
* detail with message "Role not authorized for this API route".
* cause with message "Certificate not authorized".
* cause with message "Certificate not authorized".
## Test Case 13: Retrieve ACL with Invoker Certificate
## Test Case 12: Retrieve ACL with Invoker Certificate
**Test ID**: ***capif_api_acl-13***
**Test ID**: ***capif_api_acl-12***
**Description**:
**Description**:
@@ -749,9 +679,9 @@ At this documentation you will have all information and related files and exampl
@@ -749,9 +679,9 @@ At this documentation you will have all information and related files and exampl
* detail with message "Role not authorized for this API route".
* detail with message "Role not authorized for this API route".
* cause with message "Certificate not authorized".
* cause with message "Certificate not authorized".
## Test Case 14: No ACL for invoker after be removed
## Test Case 13: No ACL for invoker after be removed
**Test ID**: ***capif_api_acl-14***
**Test ID**: ***capif_api_acl-13***
**Description**:
**Description**: