Added supported features default value in common operations and fixed test...

**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.

  If customer want to receive log information then Enhanced Event Report feature must be active.

**Pre-Conditions**:

  1. Register provider and publish one API at CCF

  2. Register Invoker and Onboard Invoker at CCF

  3. Discover published APIs and extract apiIds and apiNames

  4. Subscribe to **SERVICE_API_INVOCATION_SUCCESS** and **SERVICE_API_INVOCATION_FAILURE** event filtering by aefId.

  4. Subscribe to **SERVICE_API_INVOCATION_SUCCESS** and **SERVICE_API_INVOCATION_FAILURE** event filtering by aefId. Enhanced_event_report active at supported features.

  5. Retrieve {subscriberId} and {subscriptionId} from Location Header

  6. Emulate Success and Failure on API invocation of provider by Invoker, using Invocation Logs API.

     2. body [event subscription request body] with:

        1. events: **['SERVICE_API_INVOCATION_SUCCESS','SERVICE_API_INVOCATION_FAILURE']**

        2. eventFilter: only receive events from provider's aefId.

        3. supportedFeatures: binary 0100 -> string **4**

     3. Use **Invoker Certificate**

  7. Create Log Entry emulating provider receive Success and Failure api invocation from invoker:

  6. Create Log Entry emulating provider receive Success and Failure api invocation from invoker:

     1. Send **POST** to **https://{CAPIF_HOSTNAME}/api-invocation-logs/v1/{aefId}/logs**

     2. body [log entry request body] with:

        1. aefId from provider published.

  1. Register provider and publish one API at CCF

  2. Register Invoker and Onboard Invoker at CCF

  3. Discover published APIs and extract apiIds and apiNames

  4. Subscribe to **SERVICE_API_AVAILABLE** and **SERVICE_API_UNAVAILABLE** event filtering by aefId.

  4. Subscribe to **SERVICE_API_AVAILABLE** and **SERVICE_API_UNAVAILABLE** event filtering by aefId. Enhanced_event_report active at supported features.

  5. Retrieve {subscriberId} and {subscriptionId} from Location Header

  6. Provider publish new API.

  7. Provider remove published API.

     2. body [event subscription request body] with:

        1. events: **['SERVICE_API_AVAILABLE','SERVICE_API_UNAVAILABLE']**

        2. eventFilter: only receive events from provider's aefId.

        3. supportedFeatures: binary 0100 -> string **4**

     3. Use **Invoker Certificate**

  6. Publish new Service API at CCF:

  1. Register Provider and publish one API at CCF

  2. Register Invoker and Onboard Invoker at CCF

  3. Discover published APIs and extract apiIds and apiNames

  4. Subscribe to **SERVICE_API_UPDATE** event filtering by aefId.

  4. Subscribe to **SERVICE_API_UPDATE** event filtering by aefId. Enhanced_event_report active at supported features.

  5. Retrieve {subscriberId} and {subscriptionId} from Location Header at event subscription

  6. Provider update information of Service API Published.

     2. body [event subscription request body] with:

        1. events: **['SERVICE_API_UPDATE']**

        2. eventFilter: only receive events from provider's aefId.

        3. supportedFeatures: binary 0100 -> string **4**

     3. Use **Invoker Certificate**

  7. Update published API at CCF:

**Execution Steps**:

  1. Register Provider at CCF

  2. Subscribe Provider to **API_INVOKER_ONBOARDED, API_INVOKER_UPDATED and API_INVOKER_OFFBOARDED** events.

  2. Subscribe Provider to **API_INVOKER_ONBOARDED, API_INVOKER_UPDATED and API_INVOKER_OFFBOARDED** events. Enhanced_event_report active at supported features.

  3. Register Invoker and Onboard Invoker at CCF

  4. Update Onboarding Information at CCF with a minor change on "notificationDestination"

  5. Offboard Invoker

     1. Send **POST** to **https://{CAPIF_HOSTNAME}/capif-events/v1/{subscriberId}/subscriptions**

     2. body [event subscription request body] with:

        1. events: **['API_INVOKER_ONBOARDED', 'API_INVOKER_UPDATED', 'API_INVOKER_OFFBOARDED']**

        2. supportedFeatures: binary 0100 -> string **4**

     3. Use **Provider AMF Certificate**

  4. Perform [invoker onboarding]

  5. Update information of previously onboarded Invoker:

  1. Register Provider at CCF.

  2. Publish a provider API with name **service_1**.

  3. Register Invoker and Onboard Invoker at CCF.

  4. Subscribe Provider to **ACCESS_CONTROL_POLICY_UPDATE** event.

  4. Subscribe Provider to **ACCESS_CONTROL_POLICY_UPDATE** event. Enhanced_event_report active at supported features.

  5. Discover APIs filtered by **aef_id**

  6. Create Security Context for Invoker.

  7. Provider Retrieve ACL

     2. body [event subscription request body] with:

        1. events: **['ACCESS_CONTROL_POLICY_UPDATE']**

        2. eventFilters: apiInvokerIds array with apiInvokerId of invoker

        3. supportedFeatures: binary 0100 -> string **4**

     3. Use **Provider AMF Certificate**

  5. Discover published APIs

  6. Create Security Context for Invoker

  1. Register Provider at CCF.

  2. Publish a provider API with name **service_1**.

  3. Register Invoker and Onboard Invoker at CCF.

  4. Subscribe Invoker to **ACCESS_CONTROL_POLICY_UNAVAILABLE** event.

  4. Subscribe Invoker to **ACCESS_CONTROL_POLICY_UNAVAILABLE** event. Enhanced_event_report active at supported features.

  5. Discover APIs filtered by **aef_id**

  6. Create Security Context for Invoker.

  7. Provider Retrieve ACL.

     2. body [event subscription request body] with:

        1. events: **['ACCESS_CONTROL_POLICY_UNAVAILABLE']**

        2. eventFilters: apiInvokerIds array with apiInvokerId of invoker

        3. supportedFeatures: binary 0100 -> string **4**

     3. Use **Invoker Certificate**

  5. Discover published APIs

  6. Create Security Context for Invoker

     * 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:

  8. Delete Security Context of Invoker by Provider:

     * Send **DELETE** **https://{CAPIF_HOSTNAME}/trustedInvokers/{apiInvokerId}**

     * Use **AEF Certificate**

        1. One Event should be **ACCESS_CONTROL_POLICY_UNAVAILABLE** without **eventDetail**.

        2. One Event should be **API_INVOKER_AUTHORIZATION_REVOKED** without **eventDetail**.

---

## Test Case 13: Creates a new individual CAPIF Event Subscription without supported features attribute.

**Test ID**: ***capif_api_events-13***

**Description**:

  This test case will check error when CAPIF subscriber (Invoker or Publisher) Subscribe to Events without supported features attribute.

**Pre-Conditions**:

  * CAPIF subscriber is pre-authorised (has valid InvokerId or apfId from CAPIF Authority)

**Execution Steps**:

  1. Register Invoker and Onboard Invoker at CCF

  2. Subscribe to Events without supported features

  3. Retrieve {subscriberId} and {subscriptionId} from Location Header

**Information of Test**:

  1. Perform [Invoker Onboarding]

  2. Event Subscription:

     1. Send **POST** to **https://{CAPIF_HOSTNAME}/capif-events/v1/{subscriberId}/subscriptions**

     2. body [event subscription request body]

        1. supportedFeatures NOT PRESENT.

     3. Use **Invoker Certificate**

**Expected Result**:

  1. 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}**

  1. Response to Event Subscription must accomplish:

     1. **400 Bad Request**

     2. Error Response Body must accomplish with **ProblemDetails** data structure with:

        * status 400

        * title with message "Bad Request"

        * detail with message "supportedFeatures not present in request".

        * cause with message "supportedFeatures not present".

---

[invoker onboard request body]: ../api_invoker_management/invoker_details_post_example.json  "API Invoker Request"

# Common Operations

## Default Supported Features

By default all required supported features on POST Request will be present and set to "0" unless test define it with other value. Also it can be set to NONE is we want to test supported features not present.

## Register new user

In order to use OpenCAPIF we must add a new user. This new user can onboard/register any Invokers or Providers.