RTSP Credentials not accepting special characters

Accelerated Computing Intelligent Video Analytics Visual AI Agent
1

We are trying out the brev.dev launchable for the VSS AI Blueprint. While the launchable worked generally, there were some specific limitations that we came across during our testing.

For the live video summarization feature, we cannot use special characters within the password field. We have some cameras whose RTSP streams have special characters in their password fields that we cannot add to the application.

System Information

  • Hardware Platform (GPU model and numbers) : brev.dev launchable on CRUSOE ( 8xL40S )
  • System Memory : 128 GiB ( unconfirmed )
  • Ubuntu Version : unknown
  • NVIDIA GPU Driver Version : unknown
  • Issue Type : Bug

Steps to Reproduce

  • Run VSS brev.dev launchable
  • Under Live Video Feed Summarization tab, input an authenticated RTSP stream URL
  • Under Credentials, use a password with special characters.
1 Like
3

please refer to the doc for how to use live stream. could you try the complete uri with password field? then please make sure the uri can be played by VLC or other players. Here is a sample of RTSP uri:

rtsp://username:password@!@192.168.1.108:15667/cam/realmonitor?channel=30&subtype=0

if it still can’t work, could you share the complete uri? you can delete the IP information or use the forum private email (forum avatar-> personal messages->new message).

4

I have the same problem. The blueprint is unable to process if the password for the RTSP stream has an “@” sign within it.

ERROR: (.‘.b.o.d.y.’.,. .‘.p.a.s.s.w.o.r.d.’.): String should match pattern ‘[1]*$’ (input: “pwd@1245”).

*pwd shown above is an example:

  1. A-Za-z0-9_.-"’ , ↩︎

1 Like
8

Yes. We cannot support some special characters like “@” in the password. Because we end up concatenating the rtsp url, username, and passwords into one full url, these special characters can lead to misjudgments.

9

Our client cameras who have over 1000s of camera, it would not make sense for them to change the password because their passwords have special char like @. This needs to be addressed. It would also be good to have access to the source code, so we could resolve these issues.

10

In theory, as long as you deploy successfully, the source code is in the corresponding docker. Like if you modify the UI, you can customize via_demo_client.py and related files in vss-engine container image.
About the password issue, you can refer to this Special characters in url must be escaped.

11

Ah, my bad. I should have thought about escaping the special characters. I will try escaping the characters and get back.

However, I do not think URL encoding would work

The regular expression does not accept % character, so I am skeptical whether URL encoding would work ( for example : replace @ with %40, ! with %21, etc ).

12

( I am sorry I forgot to report the results of my experiment with the password. )

We cannot use passwords with special characters in the RTSP credentials UI.
However, the work-around for that is to create a fully qualified stream URL in the format rtsp://<username>:<password>@<stream-url> and use that in the RTSP stream URL field.

<password> with special characters ( especially : or @ ) should be URL-encoded so that it does not interfere with the stream URL. Then the stream gets accepted and starts the summarisation process.

13

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.