AMF as NF Producer
The AMF as an NF producer provides multiple services to the peer NFs. The following scenarios are processed for a successful communication to be established:
-
The AMF must get registered with the NRF for a successful communication.
-
Based on the configuration, the AMF Rest-EP must send the oauth2Required field set in the NF Service profile in the NF registration toward the NRF.
-
The signing algorithm used to encrypt the token at the NRF must be configured using access-token-jws-algo . Currently, the following three algorithms are supported:
-
HS256—Where the shared secret key is provided at AMF.
-
RS256—Where private or public key is provided depending on the configuration at NRF.
-
ES256—Where private or public key is provided depending on the configuration at NRF.
-
-
The AMF token validation is done by using a shared secret key or public key. It can be configured using access-token-jws-key .