Is the Nx Cloud up? Visit our Status Page for the current health and performance of the Nx Cloud.

Status Page

NxCloud with NxWitness API

Answered
Thierry CHAILLAN

We already have a working NxVMS integration (done in C++) and one of our custers ask us to modify our protocol to be able to use the cloud version of the Nx Witness protocol

From what I have been able to research on the subject, it seems that it is a different login mechanism. I've already contact someone of Network Optix to confirm that the NxCloud connection is possible, and it's ok.

We have to use following url type https://{systemId}.relay.vmsproxy.com instead of classic ip, the systemid will be provided by the customer. And we have to update our authentication to integrate the new authentication mechanism with cloudId + user and password.

My customer would also like to have confirmation that the NxCloud integration works well with Nx VMS and Nx SaaS versions. Could you give us some details on this issue because I don't know what is NxSaaS?

It was not possible to retrieve alarms from a NxWitness device until now. I believe this feature was under development, is it available today?

Thanks for your help

Kind regards

Thierry

 

0

Comments

4 comments

Date Votes
  • Ichiro
    • Network Optix team
    Edited

    Hi Thierry CHAILLAN,

    Thank you for your question and for sharing your progress on the integrations! It’s wonderful to hear that you’ve made such significant strides. However, I believe there may be a few clarifications needed, and I’d like to address them below.

    1) **Authentication** 
    We highly recommend that all our partners familiarize themselves with the latest authentication mechanisms. The default authentication now supported across all platforms is the bearer token (OAUTH2). While I’m unsure of the specific mechanism you’ve implemented, we strongly advise extending your implementation to support bearer tokens as soon as possible. This is not only for smoother integration but also to enhance security and compatibility.

    2) **Authentication handler endpoint** 
    It’s important to first identify which endpoint is managing your authentication.

    -If you are using an IP address (either private or public), this means the authentication is being handled by the media server, and you’ll need to use a local username (e.g., admin, test, manager, etc.). In this scenario, it is strongly recommended to use a Bearer Token, which will appear as something like (vms-xxxxx…xxx). However, Digest authentication is also supported if no other options can be chosen.

    If you are using `cloudSystemId.relay.vmsproxy.com`, it’s also connecting to the media server. The cloudSystemId method functions as a relay. Therefore, the authentication will be managed by the media server, and you should use a local username, just as mentioned above, with the option to use either a Bearer Token (recommended) or Digest.

     

    If you are using the Cloud username (xxx@domain.com), then you are asked to interact with the cloud portal only, in your case, it would be nxvms.com. Also, you will see the token is (nxcdb-xxx…xxx). FYI, if you are using Nx Cloud redirection approach, you have to use the bearer token and this is the requirement for this approach.

    3.**Bearer Token Authentication ** 
    Nx Cloud authentication and bearer tokens have been fully available since Nx 5.1, so I recommend starting with this article for details on requesting tokens from the appropriate endpoint using the correct username (local or cloud). You can also find some helpful examples here: [Nx Open Integrations – Authentication Samples]

     

    Thank you, and I hope this helps clarify the process.

    0
  • Thierry CHAILLAN

    Hi,

    Ok the Authentication mechanism is now clear, but I've also these 2 questions

    My customer would like to have confirmation that the NxCloud integration works well with Nx VMS and Nx SaaS versions. Could you give us some details on this issue because I don't know what is NxSaaS?

    It was not possible to retrieve alarms from a NxWitness device until now. I believe this feature was under development, is it available today?

    Thanks for your help

    Kind regards

    Thierry

    0
  • Ichiro
    • Network Optix team

    Hi Thierry CHAILLAN

    Thank you for reaching out.

    Please note that Nx Enterprise (Nx SaaS) has not yet been released and likely it would be available around later this year. However, the API and authentication methods are the same across both versions, so there is no need to maintain separate versions for this.

    Regarding your issue, while it appears to be a general troubleshooting matter, there is limited information provided, and we have not yet seen the details about the “alarms from Nx Witness devices” you mentioned.

     

    First, there are no physical Nx Witness devices, as Nx Witness is a VMS (software). Could you clarify what you mean by “Nx Witness devices”? Are saying the server application?

    Second, it would be helpful to know what kind of alarms you are referring to and what steps you have taken in these specific cases. This is essential information that should be provided upfront if possible.

     

    Also, please note that the post is related to the Nx Cloud API. It might be a good idea to separate the topics and raise another question specifically regarding your “devices or alarms issue.” Thank you for your understanding, and we look forward to your clarification in the other post. 

    Thanks.

    0
  • Thierry CHAILLAN

    OK I'll open another ticket for my alarm questions

    Thanks for your help

    Kind regards

    Thierry

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post