Capif aef security api (#5)

PR:

AEF security implementation within the provider api publication and invoker,
Documentation updated,
Fixed little mistakes related to renaming, loading initial data, etc,
Tests modified,
License Apache 2 for ETSI added.

---------

Co-authored-by: JorgeEcheva26 <jorge.echevarriauribarri.practicas@telefonica.es>
Co-authored-by: Daniel García <daniel.garciasanchez@telefonica.com>

LICENSE

@@ -13,4 +13,206 @@ Unless required by applicable law or agreed to in writing, software
 distributed under the License is distributed on an “AS IS” BASIS,
 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
-limitations under the License.
\ No newline at end of file
+limitations under the License.
+
+Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2022 Telefónica Innovación Digital, Fogus Innovations & Services P.C. and ETSI.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

README.md

@@ -74,7 +74,6 @@ For that purpose Network Apps play 2 different roles when interacting with CAPIF
 
   - AEF(API Exposing Function), is responsible for the exposure of the service APIs. Assuming that API Invokers are authorized by the CCF, AEF validates the authorization and subsequently provides the direct communication entry points to the service APIs. AEF may also authorize API invokers and record the invocations in log files.One provider can have multiple AEFs
 
-
 OpenCAPIF SDK brings a set of functions to integrate with the 5G Core's function CAPIF, as defined in [3GPP Technical Specification (TS) 29.222 V18.5.0 Common API Framework for 3GPP Northbound APIs](https://www.etsi.org/deliver/etsi_ts/129200_129299/129222/18.05.00_60/ts_129222v180500p.pdf). This section shows the mapping between the Python functions available in this SDK and the CAPIF OpenAPI APIs defined the reference standard:
 
 | **3GPP CAPIF API**                                    | **OpenCAPIF SDK function**                                  | **Description**                                             |
@@ -95,7 +94,6 @@ OpenCAPIF SDK brings a set of functions to integrate with the 5G Core's function
 | /{apfId}/service-apis (GET)            | [get_all_services()](./doc/sdk_full_documentation.md#get-all-services)                                          | Retrieves a list of all available service APIs for a specific `apfId`            |
 | /aef-security/v1/check-authentication (POST)            | [check_authentication()](./doc/sdk_full_documentation.md#check_authentication)                                          | This custom operation allows the API invoker to confirm the `supported_features` from the API exposing function(AEF)            |
 
-
 NOTE: Above mentioned CAPIF APIs are defined in these 3GPP references:
 - [CAPIF Invoker API specification](https://github.com/jdegre/5GC_APIs/blob/Rel-18/TS29222_CAPIF_API_Invoker_Management_API.yaml)
 - [CAPIF Provider API specification](https://github.com/jdegre/5GC_APIs/blob/Rel-18/TS29222_CAPIF_API_Provider_Management_API.yaml)

config/capif_sdk_config.json

@@ -9,6 +9,10 @@
   "invoker": {
     "invoker_folder": "",
     "capif_callback_url": "",
+    "supported_features":"",
+    "check_authorization":{
+      "ip":"",
+      "port":""
     "cert_generation": {
       "csr_common_name": "",
       "csr_organizational_unit": "",
@@ -17,7 +21,6 @@
       "csr_state_or_province_name": "",
       "csr_country_name": "",
       "csr_email_address": ""
-
     },
     "discover_filter": {
       "api-name": "",

doc/sdk_configuration.md

@@ -37,7 +37,7 @@ When configuring the SDK as a **Network App Invoker**, the following fields must
 **Optional:**
 To enable the discovery of specific APIs, the fields under [`discover_filter`](#configuration-of-discover_filter) can be configured.
 
-To use `check_authentication()` it is required to fill the `ip` and `port` variables within the `check_authentication` variable
+To use check_authentication() it will be required to fill up the `ip` and `port` parameters within the `check_authentication` variable.
 
 ### Network App Provider
 
@@ -92,6 +92,7 @@ This file can also be populated using [environment variables](../samples/envirom
 - `api_description_path`: The path to the [ServiceAPIDescription](https://github.com/jdegre/5GC_APIs/blob/Rel-18/TS29222_CAPIF_Publish_Service_API.yaml) JSON file.
 - `check_authentication`: The `ip` and `port` of the target Provider's AEF to get their supported features from.
 
+
 ## Configuration via `capif_sdk_register.json`
 
 To use this SDK in a local environment for creating and removing users, the following fields must be populated. Note that this feature is not included in the SDK, but instructions can be found in the [CAPIF official repository](https://labs.etsi.org/rep/ocf/capif/-/tree/REL1?ref_type=heads).

doc/sdk_full_documentation.md

@@ -17,7 +17,6 @@ Before using the SDK, the following steps should be completed:
 
 ![GENERAL CAPIF USAGE FLOW](./images/flows_updated_opencapif.jpg)
 
-
 The repository provides two modes for utilizing the OpenCAPIF SDK:
 
 1. **Development Mode**: The SDK can be imported directly into code for development purposes. Sample applications using the SDK are available in the [network_app_samples](../network_app_samples/) folder.
@@ -32,7 +31,6 @@ The repository provides two modes for utilizing the OpenCAPIF SDK:
 
 As outlined in the [Network App developers section](../README.md), the OpenCAPIF SDK supports two primary roles:
 
-
 - [Provider Network App](#provider-network-app)
     - [Important Information for Providers](#important-information-for-providers)
     - [Provider Onboarding](#provider-onboarding)
@@ -70,8 +68,6 @@ All the configuration values are available within the object capif_provider_conn
 
 The provider_capif_ids variable stores the `provider_service_ids.json` content in a dictionary form.
 
-The provider_capif_ids variable stores the `provider_capif_ids.json` content in a dictionary form.
-
 ### Provider Onboarding
 
 OpenCAPIF SDK references:
@@ -92,7 +88,13 @@ The SDK streamlines API publishing with the option to select specific APFs and A
 
 ### Service Deletion
 
-OpenCAPIF SDK references:
+**Required SDK inputs**:
+- publisher_apf_id
+- publisher_aefs_ids
+
+The SDK simplifies the process of publishing an API in CAPIF, with the option to select specific APFs and AEFs. Before publishing, ensure you’ve [onboarded as a provider](#provider-onboarding).
+
+**Required SDK inputs**:
 - **Function**: `unpublish_service()`
 - **Script**: `provider_unpublish_api.py`
 
@@ -125,10 +127,9 @@ Retrieve information on a previously published service, stored in `service_recei
 - publisher_apf_id
 
 ### Get All Services
-Retrieve information on all previously published services, stored in `service_received.json`. Onboarding and service publication are required.
+Retrieve information about all previously published services in `service_received.json`. Ensure you are [onboarded as a provider](#provider-onboarding) and have [published services](#services-publishing).
 
 **Required SDK input**:
-
 - publisher_apf_id
 
 ![Provider_publish](./images/flows_provider_publish_functions.jpg)
@@ -145,7 +146,6 @@ The provider must be onboarded before using these features.
 
 ## Invoker Network App
 
-
 The OpenCAPIF SDK enables efficient implementation of invoker functionality for Network App. This section details the SDK features related to CAPIF invokers.
 
 ### Important Information for Invokers

network_app_samples/network_app_invoker_sample/capif_sdk_config_sample.json

@@ -9,6 +9,11 @@
   "invoker":{
     "invoker_folder": "/Users/IDB0128/Documents/OpenCapif/test_invoker_certificate_folder",
     "capif_callback_url": "http://localhost:5000",
+    "supported_features":"fffffff",
+    "check_authentication":{
+      "ip":"",
+      "port":""
+    },
     "cert_generation":{
       "csr_common_name": "invoker",
       "csr_organizational_unit": "test_app_ou",

network_app_samples/network_app_invoker_sample/network_app_invoker.py

@@ -89,13 +89,19 @@ if __name__ == "__main__":
     capif_connector = capif_invoker_connector(config_file=capif_sdk_config_path)
     capif_connector.onboard_invoker()
     print("INVOKER ONBOARDING COMPLETED")
-
     # Now, with the certificates available, proceed with discovery
     discoverer = service_discoverer(config_file=capif_sdk_config_path)
     discoverer.discover()
-
     while True:
         discoverer.get_tokens()
+        
+        details = discoverer.invoker_capif_details
+        tamaño = len(details["registered_security_contexes"])
+        ip = details["registered_security_contexes"][tamaño-1]["aef_profiles"][0]["ip"]
+        port = details["registered_security_contexes"][tamaño-1]["aef_profiles"][0]["port"]
+        discoverer.check_authentication["ip"] = ip
+        discoverer.check_authentication["port"] = port
+        discoverer.check_authentication()
 
         # Load API details from the JSON file
         token = discoverer.token

network_app_samples/network_app_provider_sample/capif_sdk_config_sample.json

@@ -9,6 +9,10 @@
   "invoker":{
     "invoker_folder": "",
     "capif_callback_url": "",
+    "check_authentication":{
+      "ip":"",
+      "port":""
+    },
     "cert_generation":{
       "csr_common_name": "",
       "csr_organizational_unit": "",