Need for clarification : choosing security key for Response callback of services

For services like /v1/switch-redundant-transmitter-pair-off, /v1/reactivate-transmitters-of-link, /v1/provide-transmitter-status-of-parallel-links we have a callback "Response". In this callback, we send respective response to the "requestor-receive-operation" mentioned in request-body.

As per understanding, the requesting application (data of which is given in request body of the service) may be any application ( same AIPS or any external application). And we need not create any entry in load-file like http-client or operation-client for the request and we will store them in temporary RAM ((Kindly let me know if my understanding is not correct at this point)).

As per above understanding, if the request received is from a different application, we would not know the security key of the requestor-receive-operation and this might lead to unauthorized error response.

Proposal: Security could be removed for the receiving operations. For example: in AIPS :: /v1/receive-power-saving-activation-status, /v1/receive-power-saving-deactivation-status and /v1/receive-transmitter-status-of-parallel-links. Also corresponding receiving services in external applications could be avoided with security key.

Proposal because of the following constraint:

In order for AIPS to know the security key, it should have a operation-client and a link to be created between the operation-client of AIPS and the operation-server of the requesting application. Since, we donot have a operation-client, we could not store the operation-key.
On the other hand, we cannot pass the security key through a REST API, which would lead to security breach.

Kindly let me know your views and correct me if I am wrong.

openBackhaul / AirInterfacePowerSaver

Need for clarification : choosing security key for Response callback of services #114