CAPIF (invoker )testing issue

[miumiu1111]

hello, I am working with testing capif files by using the curl method. I registered invoker and provider and I got an access token , I got certificate too. Now when i am trying go to next step onboard an Invoker and provider it gives to me this problem {"status":401, "title":"Unauthorized" ,"detail":"Role not authorized for this API route", "cause":"User role must be invoker"}{"status":401, "title":"Unauthorized" ,"detail":"User not authorized", "cause":"Certificate not authorized"}{"status":401, "title":"Unauthorized" ,"detail":"Role not authorized for this API route", "cause":"User role must be invoker"} Please , if someone has solution guide me ! Thanks a lot

[qriuspanda]

Hello,
You need to use access token of invoker and ca.crt with request when you are onboarding invoker. It seems that you are using access token of provider.

[miumiu1111]

helloo, I want to make a note that when working with Invoker, I use the access token of the Invoker. However, I am still trying to figure out what I am doing wrong. Additionally, while working on this project, I have decided to focus more on the NEF. I will write updates here if I have any successful developments.Thank you ! ))

[qriuspanda]

I am also working on NEF with CAPIF.
Do you have any insight on How will NEF verify the access token it got from CAPIF, when API Invoker invokes any NEF-API with access token and NEF is acting as AEF?

[sxarism]

Hello all!
This repo and the version of the code are not used anymore.
This open-source implementation of CAPIF software is now supported by ETSI. You can find all the necessary information (documentation, code etc) here, in the official site of OpenCAPIF Software Development Group.

Hope to see you there!