Skip to content
Snippets Groups Projects
Normal view Permalink
README.md 29.1 KiB
Newer Older
Jorge Moratinos's avatar
OpenCAPIF Release 0 documentation
Jorge Moratinos committed
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 
# Test Plan for CAPIF Api Access Control Policy
At this documentation you will have all information and related files and examples of test plan for this API.

## Test Case 1: Retrieve ACL

**Test ID**: ***capif_api_acl-1***

**Description**:
  
  This test case will check that an API Provider can retrieve ACL from CAPIF

**Pre-Conditions**:
  
  * API Provider had a Service API Published on CAPIF
  * API Invoker had a Security Context for Service API published.

**Information of Test**:

  1. Perform [Provider Registration]

  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
     * Send PUT *https://{CAPIF_HOSTNAME}/trustedInvokers/{apiInvokerId}*
     * body [service security body]
     * Use Invoker Certificate

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

**Execution Steps**:
  
  1. Register and onboard Provider at CCF.
  2. Publish a provider API with name service_1
  3. Register and onboard Invoker at CCF
  4. Store signed Certificate
  5. Create Security Context
  6. Provider Get ACL information.
   
**Expected Result**:

  1. ACL Response:
     1. **200 OK** Response.
     2. body returned must accomplish **AccessControlPolicyList** data structure.
     3. apiInvokerPolicies must:
        1. contain only one object.
        2. apiInvokerId must match apiInvokerId registered previously.


## Test Case 2: Retrieve ACL with 2 Service APIs published

**Test ID**: ***capif_api_acl-2***

**Description**:
  
  This test case will check that an API Provider can retrieve ACL from CAPIF for 2 different serviceApis published.

**Pre-Conditions**:
  
  * API Provider had two Service API Published on CAPIF
  * API Invoker had a Security Context for both Service APIs published.

**Information of Test**:

  1. Perform [Provider Registration]

  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. 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
     * Store *serviceApiId*
     * Use APF Certificate
  
  4. Perform [Invoker Onboarding] store apiInvokerId
  5. Discover published APIs
  6. Create Security Context for this Invoker for both published APIs
     * Send PUT *https://{CAPIF_HOSTNAME}/trustedInvokers/{apiInvokerId}*
     * body [service security body]
     * Use Invoker Certificate

  7. Provider Retrieve ACL for serviceApiId1
     * Send GET *https://{CAPIF_HOSTNAME}/access-control-policy/v1/accessControlPolicyList/${serviceApiId1}?aef-id=${aef_id}*
     * Use *serviceApiId* and *aefId*
     * Use AEF Provider Certificate

  8. Provider Retrieve ACL for serviceApiId2
     * Send GET *https://{CAPIF_HOSTNAME}/access-control-policy/v1/accessControlPolicyList/${serviceApiId2}?aef-id=${aef_id}*
     * Use *serviceApiId* and *aefId*
     * Use AEF Provider Certificate

**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 for service_1.
  7. Provider Get ACL information for service_2.
   
**Expected Result**:

  1. ACL Response:
     1. **200 OK** Response.
     2. body returned must accomplish **AccessControlPolicyList** data structure.
     3. apiInvokerPolicies must:
        1. contain one object.
        2. apiInvokerId must match apiInvokerId registered previously.

## Test Case 3: Retrieve ACL with security context created by two different Invokers

**Test ID**: ***capif_api_acl-3***

**Description**:
  
  This test case will check that an API Provider can retrieve ACL from CAPIF containing 2 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.

**Information of Test**:

  1. Perform [Provider Registration]

  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}*
     * Use *serviceApiId* and *aefId*
     * Use AEF Provider Certificate

**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.
   
**Expected Result**:

  1. ACL Response:
     1. **200 OK** Response.
     2. body returned must accomplish **AccessControlPolicyList** data structure.
     3. apiInvokerPolicies must:
        1. Contain two objects.
        2. One object must match with apiInvokerId1 and the other one with apiInvokerId2 an registered previously.
   
## Test Case 4: Retrieve ACL filtered by api-invoker-id

**Test ID**: ***capif_api_acl-4***

**Description**:
  
  This test case will check that an API Provider can retrieve ACL filtering by apiInvokerId 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.

**Information of Test**:

  1. Perform [Provider Registration]

  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
  
  4. Perform [Invoker Onboarding] store apiInvokerId
  6. Discover published APIs
  7. Create Security Context for this Invoker for both published APIs
     * Send PUT *https://{CAPIF_HOSTNAME}/trustedInvokers/{apiInvokerId}*
     * body [service security body]
     * Use Invoker Certificate

  8. Repeat previous 3 steps in order to have a new Invoker.

  9. Provider Retrieve ACL for serviceApiId
     * Send GET *https://{CAPIF_HOSTNAME}/access-control-policy/v1/accessControlPolicyList/${serviceApiId1}?aef-id=${aef_id}&api-invoker-id={apiInvokerId1}*
     * Use *serviceApiId*, *aefId* and apiInvokerId1
     * Use AEF Provider Certificate

  10. Provider Retrieve ACL for serviceApiId
     * Send GET *https://{CAPIF_HOSTNAME}/access-control-policy/v1/accessControlPolicyList/${serviceApiId1}?aef-id=${aef_id}&api-invoker-id={apiInvokerId2}*
     * Use *serviceApiId*, *aefId* and apiInvokerId2
     * Use AEF Provider Certificate

**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 api-invoker-id.
  7. Provider Get ACL information with query parameter indicating second api-invoker-id.
   
**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 apiInvokerId1.

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

## Test Case 5: Retrieve ACL filtered by supported-features

**Test ID**: ***capif_api_acl-5***

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

**Information of Test**:

  1. Perform [Provider Registration]

  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

**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.
   
**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**:
  
  This test case will check that an API Provider can't retrieve ACL from CAPIF if aef-id is not valid

**Pre-Conditions**:
  
  * API Provider had a Service API Published on CAPIF
  * API Invoker had a Security Context for Service API published.

**Information of Test**:

  1. Perform [Provider Registration]

  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
     * Send PUT *https://{CAPIF_HOSTNAME}/trustedInvokers/{apiInvokerId}*
     * body [service security body]
     * Use Invoker Certificate

  6. Provider Retrieve ACL
     * Send GET *https://{CAPIF_HOSTNAME}/access-control-policy/v1/accessControlPolicyList/${serviceApiId}?aef-id=${AEF_ID_NOT_VALID}*
     * Use *serviceApiId* and *AEF_ID_NOT_VALID*
     * Use AEF Provider Certificate

**Execution Steps**:
  
  1. Register and onboard Provider at CCF.
  2. Publish a provider API with name service_1
  3. Register and onboard Invoker at CCF
  4. Store signed Certificate
  5. Create Security Context
  6. Provider Get ACL information.
   
**Expected Result**:

  1. ACL Response:
     1. **404 Not Found** Response.
     2. body returned must accomplish **Problem Details** data structure.
     3. apiInvokerPolicies must:
        * status **404**
        * title with message "Not Found"
        * 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".


## Test Case 7: Retrieve ACL with service-id not valid

**Test ID**: ***capif_api_acl-7***

**Description**:
  
  This test case will check that an API Provider can't retrieve ACL from CAPIF if service-api-id is not valid

**Pre-Conditions**:
  
  * API Provider had a Service API Published on CAPIF
  * API Invoker had a Security Context for Service API published.

**Information of Test**:

  1. Perform [Provider Registration]

  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
     * Send PUT *https://{CAPIF_HOSTNAME}/trustedInvokers/{apiInvokerId}*
     * body [service security body]
     * Use Invoker Certificate

  6. Provider Retrieve ACL
     * Send GET *https://{CAPIF_HOSTNAME}/access-control-policy/v1/accessControlPolicyList/${NOT_VALID_SERVICE_API_ID}?aef-id=${aef_id}*
     * Use *NOT_VALID_SERVICE_API_ID* and *aef_id*
     * Use AEF Provider Certificate

**Execution Steps**:
  
  1. Register and onboard Provider at CCF.
  2. Publish a provider API with name service_1
  3. Register and onboard Invoker at CCF
  4. Store signed Certificate
  5. Create Security Context
  6. Provider Get ACL information.
   
**Expected Result**:

  1. ACL Response:
     1. **404 Not Found** Response.
     2. body returned must accomplish **Problem Details** data structure.
     3. apiInvokerPolicies must:
        * status **404**
        * title with message "Not Found"
        * 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".

## Test Case 8: Retrieve ACL with service-api-id and aef-id not valid

**Test ID**: ***capif_api_acl-8***

**Description**:
  
  This test case will check that an API Provider can't retrieve ACL from CAPIF if service-api-id and aef-id are not valid

**Pre-Conditions**:
  
  * API Provider had a Service API Published on CAPIF
  * API Invoker had a Security Context for Service API published.

**Information of Test**:

  1. Perform [Provider Registration]

  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
     * Send PUT *https://{CAPIF_HOSTNAME}/trustedInvokers/{apiInvokerId}*
     * body [service security body]
     * Use Invoker Certificate

  6. Provider Retrieve ACL
     * Send GET *https://{CAPIF_HOSTNAME}/access-control-policy/v1/accessControlPolicyList/${NOT_VALID_SERVICE_API_ID}?aef-id=${AEF_ID_NOT_VALID}*
     * Use *NOT_VALID_SERVICE_API_ID* and *aef_id*
     * Use AEF Provider Certificate

**Execution Steps**:
  
  1. Register and onboard Provider at CCF.
  2. Publish a provider API with name service_1
  3. Register and onboard Invoker at CCF
  4. Store signed Certificate
  5. Create Security Context
  6. Provider Get ACL information.
   
**Expected Result**:

  1. ACL Response:
     1. **404 Not Found** Response.
     2. body returned must accomplish **Problem Details** data structure.
     3. apiInvokerPolicies must:
        * status **404**
        * title with message "Not Found"
        * 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".


## Test Case 9: Retrieve ACL without SecurityContext created previously by Invoker

**Test ID**: ***capif_api_acl-9***

**Description**:
  
  This test case will check that an API Provider can't retrieve ACL if no invoker had requested Security Context to CAPIF

**Pre-Conditions**:

  * API Provider had a Service API Published on CAPIF
  * API Invoker created but no Security Context for Service API published had been requested.

**Information of Test**:

  1. Perform [Provider Registration]

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

**Execution Steps**:
  
  1. Register and onboard Provider at CCF.
  2. Publish a provider API with name service_1
  3. Register and onboard Invoker at CCF
  4. Store signed Certificate
  5. Create Security Context
  6. Provider Get ACL information.
   
**Expected Result**:

  1. ACL Response:
     1. **404 Not Found** Response.
     2. body returned must accomplish **Problem Details** data structure.
     3. apiInvokerPolicies must:
        * status **404**
        * title with message "Not Found"
        * 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".

## Test Case 10: Retrieve ACL filtered by api-invoker-id not present

**Test ID**: ***capif_api_acl-10***

**Description**:
  
  This test case will check that an API Provider get not found response if filter by not valid api-invoker-id doesn't match any registered ACL.

**Pre-Conditions**:
  
  * API Provider had a Service API Published on CAPIF
  * API Invoker had a Security Context for Service API published.

**Information of Test**:

  1. Perform [Provider Registration]

  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
     * Send PUT *https://{CAPIF_HOSTNAME}/trustedInvokers/{apiInvokerId}*
     * body [service security body]
     * Use Invoker Certificate

  6. Provider Retrieve ACL
     * Send GET *https://{CAPIF_HOSTNAME}/access-control-policy/v1/accessControlPolicyList/${serviceApiId}?aef-id=${aef_id}&api-invoker-id={NOT_VALID_API_INVOKER_ID}*
     * Use *serviceApiId*, *aefId* and *NOT_VALID_API_INVOKER_ID*
     * Use AEF Provider Certificate

**Execution Steps**:
  
  1. Register and onboard Provider at CCF.
  2. Publish a provider API with name service_1
  3. Register and onboard Invoker at CCF
  4. Store signed Certificate
  5. Create Security Context
  6. Provider Get ACL information.
   
**Expected Result**:

  1. ACL Response:
     1. **404 Not Found** Response.
     2. body returned must accomplish **Problem Details** data structure.
     3. apiInvokerPolicies must:
        * status **404**
        * title with message "Not Found"
        * 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".

## Test Case 11: Retrieve ACL with APF Certificate

**Test ID**: ***capif_api_acl-11***

**Description**:

  This test case will check that an API Provider can't retrieve ACL from CAPIF using APF Certificate

**Pre-Conditions**:

  * API Provider had a Service API Published on CAPIF
  * API Invoker had a Security Context for Service API published.

**Information of Test**:

  1. Perform [Provider Registration]

  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
     * Send PUT *https://{CAPIF_HOSTNAME}/trustedInvokers/{apiInvokerId}*
     * body [service security body]
     * Use Invoker Certificate

  6. Provider Retrieve ACL
     * Send GET *https://{CAPIF_HOSTNAME}/access-control-policy/v1/accessControlPolicyList/${serviceApiId}?aef-id=${aef_id}*
     * Use *serviceApiId* and *aefId*
     * Use APF Provider Certificate

**Execution Steps**:

  1. Register and onboard Provider at CCF.
  2. Publish a provider API with name service_1
  3. Register and onboard Invoker at CCF
  4. Store signed Certificate
  5. Create Security Context
  6. Provider Get ACL information.

**Expected Result**:

  1. Response to Logging Service must accomplish:
     1. **401 Unauthorized**
     2. Error Response Body must accomplish with **ProblemDetails** data structure with:
        * status 401
        * title with message "Unauthorized"
        * detail with message "Role not authorized for this API route".
        * cause with message "Certificate not authorized".

## Test Case 12: Retrieve ACL with AMF Certificate

**Test ID**: ***capif_api_acl-12***

**Description**:

  This test case will check that an API Provider can't retrieve ACL from CAPIF using AMF Certificate

**Pre-Conditions**:

  * API Provider had a Service API Published on CAPIF
  * API Invoker had a Security Context for Service API published.

**Information of Test**:

  1. Perform [Provider Registration]

  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
     * Send PUT *https://{CAPIF_HOSTNAME}/trustedInvokers/{apiInvokerId}*
     * body [service security body]
     * Use Invoker Certificate

  6. Provider Retrieve ACL
     * Send GET *https://{CAPIF_HOSTNAME}/access-control-policy/v1/accessControlPolicyList/${serviceApiId}?aef-id=${aef_id}*
     * Use *serviceApiId* and *aefId*
     * Use AMF Provider Certificate

**Execution Steps**:

  1. Register and onboard Provider at CCF.
  2. Publish a provider API with name service_1
  3. Register and onboard Invoker at CCF
  4. Store signed Certificate
  5. Create Security Context
  6. Provider Get ACL information.

**Expected Result**:

  1. Response to Logging Service must accomplish:
     1. **401 Unauthorized**
     2. Error Response Body must accomplish with **ProblemDetails** data structure with:
        * status 401
        * title with message "Unauthorized"
        * detail with message "Role not authorized for this API route".
        * cause with message "Certificate not authorized".

## Test Case 13: Retrieve ACL with Invoker Certificate

**Test ID**: ***capif_api_acl-13***

**Description**:

  This test case will check that an API Provider can't retrieve ACL from CAPIF using Invoker Certificate

**Pre-Conditions**:

  * API Provider had a Service API Published on CAPIF
  * API Invoker had a Security Context for Service API published.

**Information of Test**:

  1. Perform [Provider Registration]

  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
     * Send PUT *https://{CAPIF_HOSTNAME}/trustedInvokers/{apiInvokerId}*
     * body [service security body]
     * Use Invoker Certificate

  6. Provider Retrieve ACL
     * Send GET *https://{CAPIF_HOSTNAME}/access-control-policy/v1/accessControlPolicyList/${serviceApiId}?aef-id=${aef_id}*
     * Use *serviceApiId* and *aefId*
     * Use Invoker Certificate

**Execution Steps**:

  1. Register and onboard Provider at CCF.
  2. Publish a provider API with name service_1
  3. Register and onboard Invoker at CCF
  4. Store signed Certificate
  5. Create Security Context
  6. Provider Get ACL information.

**Expected Result**:

  1. Response to Logging Service must accomplish:
     1. **401 Unauthorized**
     2. Error Response Body must accomplish with **ProblemDetails** data structure with:
        * status 401
        * title with message "Unauthorized"
        * detail with message "Role not authorized for this API route".
        * cause with message "Certificate not authorized".

## Test Case 14: No ACL for invoker after be removed

**Test ID**: ***capif_api_acl-14***

**Description**:

  This test case will check that ACLs are removed after invoker is removed.

**Pre-Conditions**:

  * API Provider had a Service API Published on CAPIF
  * API Invoker had a Security Context for Service API published and ACL is present

**Information of Test**:

  1. Perform [Provider Registration]

  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
     * Send PUT *https://{CAPIF_HOSTNAME}/trustedInvokers/{apiInvokerId}*
     * body [service security body]
     * Use Invoker Certificate

  6. Provider Retrieve ACL
     * Send GET *https://{CAPIF_HOSTNAME}/access-control-policy/v1/accessControlPolicyList/${serviceApiId}?aef-id=${aef_id}&api-invoker-id={api-invoker-id}*
     * Use *serviceApiId*, *aefId* and *api-invoker-id*
     * Use AEF Provider Certificate
  7. Remove Invoker from CAPIF
  8. Provider Retrieve ACL
     * Send GET *https://{CAPIF_HOSTNAME}/access-control-policy/v1/accessControlPolicyList/${serviceApiId}?aef-id=${aef_id}&api-invoker-id={api-invoker-id}*
     * Use *serviceApiId*, *aefId* and *api-invoker-id*
     * Use AEF Provider Certificate

**Execution Steps**:
  
  1. Register and onboard Provider at CCF.
  2. Publish a provider API with name service_1
  3. Register and onboard Invoker at CCF
  4. Store signed Certificate
  5. Create Security Context
  6. Provider Get ACL information of invoker.
  7. Remove Invoker from CAPIF.
  8. Provider Get ACL information of invoker.
   
**Expected Result**:
  1. ACL Response:
     1. **200 OK** Response.
     2. body returned must accomplish **AccessControlPolicyList** data structure.
     3. apiInvokerPolicies must:
        1. contain only one object.
        2. apiInvokerId must match apiInvokerId registered previously.

  2. ACL Response:
     1. **404 Not Found** Response.
     2. body returned must accomplish **Problem Details** data structure.
     3. apiInvokerPolicies must:
        * status **404**
        * title with message "Not Found"
        * detail with message "No ACLs found for the requested service: {NOT_VALID_SERVICE_API_ID}, aef_id: {AEF_ID_NOT_VALID}, invoker: None and supportedFeatures: None".
        * cause with message "Wrong id".



[service api description]: ../api_publish_service/service_api_description_post_example.json  "Service API Description Request"
[publisher register body]: ../api_publish_service/publisher_register_body.json  "Publish register Body"
[service security body]: ../api_security_service/service_security.json  "Service Security Request"
[security notification body]: ./security_notification.json  "Security Notification Request"
[access token req body]: ./access_token_req.json  "Access Token Request"
[example]: ./access_token_req.json  "Access Token Request Example"
[invoker onboarding]: ../common_operations/README.md#register-an-invoker "Invoker Onboarding"
[provider registration]: ../common_operations/README.md#register-a-provider "Provider Registration"