I have an ip camera that streams into my wowza streaming engine.
Therefore i created a stream file with the follwoing url in it: “rtsp://camuser:password@154.13.16.19/media/video1”.
My question is, is there any way to avoid putting the username and password in the streamfile url but defining it somewhere else. I tried it in source security tab. but it seems like, source security works only for encoders and not for ip cameras ?
pls correct me if i am wrong ! Thank you all
Hi,
The Source Security authentication options are for encoders that are pushing the streams to the Wowza Streaming Engine software. As you’re pulling the stream, the username and password are not set on the Wowza Streaming Engine software side as this is what’s used to start the stream and you already have access. Instead, the username and password are on the camera side and therefore the Source Security authentication in the Manager does not apply.
In short, yes, the username and password do need to be added to the URL within the .stream file for authenticating on the camera side for IP camera sources using the RTSP protocol.
Regards,
Jason Hilton
Senior Technical Support Engineer
WOWZA | The solution you start with, the partner you scale with.
Hallo Jason
Really appreciate your answer. thank you.
I am using REST API to update the stream file. For now, I have to add the username and password to the url i send over REST API. Is there any way to not giving the username and password in the url that will send over the rest api ? like, is it possible to somewhere in Wowza Streaming Enging manager or in any config file to define the usernamen and password that my cameras have and then sending only the camera url without username and password over rest api ?
Hi Sam,
If you’re creating the .stream file from scratch, using the REST API, then yes, adding the correct authentication so that it works is going to be a requirement.
If you have an existing .stream file, you could edit this using the REST API but this will likely include the authentication in the URL even if the .stream file is just being edited.
If you’re concerned about the security of sending this over the REST API, you can configure this to work over SSL to make it more secure.
However, using the REST API isn’t your only option. If this is a concern, you could consider creating the .stream file with a text editor and then copy this over to the server using an FTP client or some other method.
Regards,
Jason Hilton
Senior Technical Support Engineer
WOWZA | The solution you start with, the partner you scale with.
