Hi! The most supported way would be to create a third party application configured as a confidential client with client credentials authentication.
This will generate a service user and a client ID + secret pair. Using our OAuth token endpoint, you can retrieve a token for the service user in your function. Then you can use that bearer token in any subsequent API calls.
You will need to give the service user permission to do the ontology editing that you would like the action to accomplish.
We are trying to orchestrate Ontology Edits. Therefore it is neccesary that a call to @Function can trigger different @OntologyEditFunctions.
Calling an OntolgoyEditFunction via a “normal function” does not yield an edit in the ontology. You have to call the action itself to get the change in an Ontology Object.
Or am I missing soemthing?