Hello,
I have query on TMF 642 alarm notification callback URL. I have gone through the doc and found the snippet like below for registration.
POST /api/hub
Accept: application/json
{"callback": "http://in.listener.com"}
My querries:
- Can the callback URL support for "HTTPS" as well or it is always plain HTTP? I see mostly HTTP.
- If the alarm listener (receiver) system wants to ensure the authenticity of the sender and expects the data to be encrypted for security reason we need the mechanism to supported in the sender side. We want to have the alarm listener exposes the authentication for sender and provides token for authorization. Alarm sender needs to authenticate and obtain the token and post the data. Is there any mechanism existing today to handle this kind of use case.
Sorry if this kind of query is answered else where. I couldn't find in brief search.
Your response is greatly appreciated.
Thanks,
Rajesh
------------------------------
Rajesh I V
Cisco Systems
------------------------------