@@ -7,7 +7,7 @@ This configuration could also be fullfilled by enviroment variables (EXAMPLE)
- invoker_folder: The path (relative or absolute) of the folder you want to store your invoker information
- provider_folder:The path (relative or absolute) of the folder you want to store your invoker information
- provider_folder:The path (relative or absolute) of the folder you want to store your provider information
- capif_host:The domain name of your capif host
@@ -29,7 +29,7 @@ This configuration could also be fullfilled by enviroment variables (EXAMPLE)
- AEFs: Number of AEF's you want to onboard as a provider Example:2
- debug_mode: Boolean | If you want to recieve logs from SDK-S6G Example:True/False
- debug_mode: Boolean | If you want to recieve logs from SDK Example:True/False
Mandatory fields no matter the target role to be onboarded, either invoker or provider:
@@ -66,7 +66,7 @@ For using the Publish Api function or the Update function the provider_api_descr
**AefIds fields won't need to fill out the from aefProfiles** array because you would already be configurating this fields by completing publisherAEFsids parameter
**If the publisherAEFsids parameter don't match with the aefProfiles you will recieve an error**
**If the publisherAEFsids parameter don't match with the aefProfiles in your [Api description](../api-samples/provider_api_description_sample.json) you will recieve an error**
@@ -78,9 +78,6 @@ To use this feature it has to be completed `Discover_filter.json` with the param
To run the Invoker Service Discovery Functionality it has to be onboarded as an Invoker before the CAPIF user.
#### **Configuration of Register.json**
In order to use this SDK in a Local enviroment and creating and removing users, its mandatory to fullfill this fields.