[Action Required] Migrate Your Nx API Integration from Digest to Bearer Token Authentication
Pinned Featured Answered
Hi
If you have built an integration against the Nx REST API using Digest Authentication, you need to take action. Digest Authentication is being removed from Nx Witness, and we want to give you plenty of lead time to make the switch.
What's Happening
Digest Authentication was deprecated in Nx Witness 5.0 (June 2022) when we introduced Bearer Token authentication as the secure replacement. We are now actively removing Digest support:
- Nx Media Server 6.1: Digest is disabled by default at High security level. Standard security level: Digest still works, for now.
- Nx Media Server 6.2+: Full removal planned. Digest will not be available at any security level. Exact version TBD.
What You Need to Do
Migrate your integration to Bearer Token authentication. In short:
- POST to /rest/v4/login/sessions to obtain a Bearer token and a logout token.
- Pass the Bearer token in the Authorization: Bearer <token> header on subsequent requests.
- DELETE to /rest/v4/login/tickets/{token} with the logout token to close the session cleanly.
All communication must be over HTTPS. Bearer Tokens cannot be sent over plain HTTP. For code-level implementation details, see the official documentation:
Authentication through the REST API
Your Input Matters — Migration Path Survey
We know migration takes time, and we are not going to pull the plug without a plan. We are evaluating several interim options and we want to know which would be most useful for your situation.
TAKE THE SURVEY NOW!
-
what will happen to RTSP streaming?
Currently, in our v6.1, RTSP streams work *only* with digest (Name/Pwd) authentication.
We tried submitting bearer token as HTTP header with RTSP URL, got 403.
Maybe because it is not supported in 6.1 but will be supported in 6.2? Or - will RTSP still accept digest authentication in 6.2?
Please clarify.
0 -
Thank you for pointing this out. This is a known issue that our team is has resolved, and will be fixed in the upcoming version 6.2 release.
Regarding the plans to deprecate the Digest feature: while our long-term goal is to remove it, internal discussions are still ongoing regarding the exact timeline, implementation details, and alternative solutions.
Because these decisions aren’t finalized, your input is incredibly valuable to us. I highly encourage you to fill out our survey so the team can take your specific use case and feedback into consideration.Kind regards.
0
Please sign in to leave a comment.
Comments
2 comments