Page Comparison

CAPIF stands for common API framework and it was developed by 3GPP to enable a unified Northbound API framework across 3GPP network functions, and to ensure that there is a single and harmonized approach for API development.

...

Register provider domain 

POST http://<CAPIF core URL>/api-provider-management/v1/registrations

Request body: APIProviderEnrolmentDetails

{
    "apiProvDomInfo": "Provider domain",
    "apiProvFuncs": [
        {
            "apiProvFuncInfo": "rApp as APF",
            "apiProvFuncRole": "APF",
            "regInfo": {
                "apiProvPubKey": "APF-PublicKey"
            }
        },
        {
            "apiProvFuncInfo": "rApp as AEF",
            "apiProvFuncRole": "AEF",
            "regInfo": {
                "apiProvPubKey": "AEF-PublicKey"
            }
        },
        {
            "apiProvFuncInfo": "rApp as AMF",
            "apiProvFuncRole": "AMF",
            "regInfo": {
                "apiProvPubKey": "AMF-PublicKey"
            }
        },
        {
            "apiProvFuncInfo": "Gateway as entrypoint AEF",
            "apiProvFuncRole": "AEF",
            "regInfo": {
                "apiProvPubKey": "AEF-Gateway-PublicKey"
            }
        }
    ],
    "regSec": "PSK"
}

Publish a new API

POST http://<CAPIF core URL>/published-apis/v1/APF_id_rApp_as_APF/service-apis

...

{
    "apiName": "example A",
    "description": "Example A API of rApp",
    "aefProfiles": [
        {
            "aefId": "AEF_id_rApp_as_AEF",
            "description": "Example A rApp as AEF",
            "versions": [
                {
                    "apiVersion": "v1",
                    "resources": [
                        {
                            "resourceName": "exampleA",
                            "commType": "REQUEST_RESPONSE",
                            "uri": "/exampleA/subscription/subscription_id_1",
                            "operations": [
                                "GET"
                            ]
                        }
                    ]
                }
            ],
            "protocol": "HTTP_1_1",
			"securityMethods": ["PSK"],
			"interfaceDescriptions": [
				{
				  "ipv4Addr": "string",
				  "port": 65535,
				  "securityMethods": ["PKI"]
				},
				{
				  "ipv4Addr": "string",
				  "port": 65535,
				  "securityMethods": ["PKI"]
				}
			  ]
        }
    ]
}

Onboard API invoker

POST http://<CAPIF core URL>/api-invoker-management/v1/onboardedInvokers

Request body: APIInvokerEnrolmentDetails

{
    "apiInvokerInformation": "rApp as invoker 1",
	 "apiList": [
		{}
	],
    "NotificationDestination": "http://invoker-app:8086/callback",
    "onboardingInformation": {
		"apiInvokerPublicKey": "{PUBLIC_KEY_INVOKER_1}",
		"apiInvokerCertificate": "apiInvokerCertificate"
  },
  "requestTestNotification": true
}

...

Security related information about CAPIF can be found in 3GPP TS 33.122 Security aspects of Common API Framework (CAPIF).

CAPIF establish security requirements for all the interfaces defined in the specification. There are also security requirements that are applicable to all CAPIF entities, such as:

• CAPIF shall provide mechanisms to hide the topology of the PLMN trust domain from the API invokers accessing the service APIs from outside the PLMN trust domain.
• CAPIF shall provide mechanisms to hide the topology of the 3rd party API provider trust domain from the API invokers accessing the service APIs from outside the 3rd party API provider trust domain.
• CAPIF shall provide authorization mechanism for service APIs from the 3rd party API providers.
• CAPIF shall support a common security mechanism for all API implementations to provide confidentiality and integrity protection.

The image below shows the functional security model for CAPIF architecture. CAPIF-1, CAPIF-2, CAPIF-3, CAPIF-4, CAPIF-5 and CAPIF-7 are interfaces that lie within the PLMN trust domain while the CAPIF-1e , CAPIF-2e, CAPIF-3e, CAPIF-4e, CAPIF-5e and CAPIF-7e interfaces are CAPIF core and AEF access points for API Invokers outside of the PLMN trust domain.

Authentication and authorization are required for both API invokers that lie within the PLMN trust domain and API invokers that lie outside of the PLMN trust domain. For an API invoker that is outside of the PLMN trust domain, the CAPIF core function in coordination with the API exposing function utilizes the CAPIF-1e, CAPIF-2e and the CAPIF-3 interfaces to onboard, authenticate and authorize the API invoker prior to granting access to CAPIF services.

Security procedures for API invoker onboarding

The API invoker and the CAPIF core function shall establish a secure session.

With a secure session established, the API Invoker sends an Onboard API Invoker Request message to the CAPIF core function. The Onboard API Invoker Request message carries an onboard credential obtained during pre-provisioning of the onboard enrolment information.

The CAPIF core function shall respond with an Onboard API invoker response message. The response shall include the CAPIF core function assigned API invoker ID, API invoker's certificate and the API invoker Onboard_Secret (generated by the CAPIF core function provided by keycloak).

Security method negotiation

The API invoker and the CAPIF core function shall negotiate a security method that shall be used by the API invoker and the API exposing function for CAPIF-2e interface authentication and protection.

As a pre-condition the API invoker must be onboarded with the CAPIF core function.

After successful mutual authentication on CAPIF-1e interface, the API invoker may send CAPIF-2/2e security capability information to the CAPIF core function in the Security Method Request message, indicating the list of security methods that it supports for each AEF.

The CAPIF core function shall select a security method to be used over CAPIF-2/2e reference point for each requested AEF, taking into account the information sent by the API invoker and send a Security Method Response message to the API invoker indicating the selected security method for each AEF.

Build CAPIF core

Anchor
buildcapif buildcapif

Download the following repos:

git clone "https://gerrit.o-ran-sc.org/r/nonrtric/plt/sme" 

To build the application, go into the repo and run the following command:

cd sme/capifcore
go build

    
To run the unit tests for the application, run the following command:

go test ./...

The application can also be built as a Docker image, by using the following command. Use the version found in the file container-tag.yaml.

docker build -t o-ran-sc/nonrtric-plt-capifcore:<image-version> .

Run CAPIF core

Anchor
runcapif runcapif

The CAPIF core needs one configuration file for keycloak including information about keycloak host (url, port and authentication for admin user) and realms. Before using CAPIF API invoker management, an invoker realm must be created in keycloak. Make sure it is created before running CAPIF core. After creating the realm in keycloak, set the name in the keycloak.yaml configuration file.

# Keycloak configurations
authorizationServer:
  host: "keycloak"
  port: "8080"
  admin:
    user: "admin"
    password: "secret"
  realms:
   master: "master"
   invokerrealm: "invokerrealm"

...

There are a number of environment variables that could be set when starting the application, however they have values by default so there is no need to set them unless specific values are needed.

• -port <port (default 8090)>
• -secPort <Secure port (default 4433)>
• -chartMuseumUrl <URL to ChartMuseum>
• -repoName <Helm repo name (default capifcore)>
• -loglevel <log level (default Info)>
• -certPath <Path to certificate>
• -keyPath <Path to private key>

To run the Core Function from the command line, run the following commands from this folder. For the parameter `chartMuseumUrl`, if it is not provided CAPIF Core will not do any Helm integration, i.e. try to start any Halm chart when publishing a service.

 ./capifcore [-port <port (default 8090)>] [-secPort <Secure port (default 4433)>] [-chartMuseumUrl <URL to ChartMuseum>] [-repoName <Helm repo name (default capifcore)>] [-loglevel <log level (default Info)>] [-certPath <Path to certificate>] [-keyPath <Path to private key>] 

...

docker-compose up

NOTE! In the configuration file in configs/keycloak.yaml when running locally the host value must be set to localhost (Eg. host: "localhost") and when using docker-compose set value to keycloak (Eg. host:"keycloak")