• SEARCH
  • DOWNLOADS
  • MY ACCOUNT
  • Buy (0)
  • CONTACT
  • Free Trial
Wowza Logo
  • PRODUCTS
    • Products

      • Wowza ClearCaster
      • Facebook Live appliance
      • Wowza Streaming Cloud
      • Cloud streaming services
      • Wowza Streaming Engine
      • Streaming server software
      • Wowza GoCoder & SDK
      • Mobile capture and encoding app
    • Capabilities

      • CDN
      • Ultra Low Latency
      • SRT
      • Player
      • WebRTC
      • Live Transcoding
      • See All Capabilities
  • DOCS & APIS

      Docs & APIs

      • Getting Started
      • User Guides
      • Technical Articles
      • Video Tutorials
      • API & SDK Docs
  • SOLUTIONS
    • Streaming Types

      • Live Video Streaming
      • Video on Demand
      • Audio-Only Streaming
      • IP Camera Streaming
      • VR and 360° Streaming
      • Chat
    • Industries

      • Broadcast & OTT
      • Education
      • Enterprise
      • Government
      • Live Events
      • Live Sports
      • Religious Organizations
    • Streaming Solutions

      • MediaDS—Integrated Streaming Device
      • Streaming Service Providers
      • Live Mobile Broadcasting
  • PRICING
    • Wowza ClearCaster

      • Facebook Live appliance
      • Starting at $2,995
      • Add to Cart
      • Request a Demo
    • Wowza Streaming Cloud

      • Cloud streaming services
      • Starter Plan: $49/month
      • Add to Cart
      • See All Plans
    • Wowza Streaming Engine

      • Streaming server software
      • Annual Plan: $65/month
      • Add to Cart
      • See All Plans
    • Wowza GoCoder SDK

      • SDK for mobile streaming
      • Talk to a Streaming Expert
      • Contact Us
      • Free Trial
  • RESOURCES

      Resources

      • Blog
      • Case Studies
      • Webinars
      • Videos
      • Podcasts
      • Test Players
      • Developer Tools
  • SUPPORT
    • Support

      • Forums
      • Software Updates
      • Open a Support Ticket
    • Plans & Services

      • Support Plans
      • Advisory Services
      • Live Event Support
  • My Account
  • Buy (0)
  • SEARCH
  • Ask a question
  • Forums
    • Wowza ClearCaster
    • Wowza Streaming Engine
    • Wowza Streaming Cloud
    • Wowza Player
    • Wowza GoCoder SDK
    • Wowza Developer Dojo
    • Topics
    • Questions
    • Users
    • Badges
  • Sign in
  • Community Home /
  • Wowza Streaming Engine /
  • Live Streaming and Encoders /
avatar image
Question by Michael Wills · Nov 06, 2010 at 06:50 AM · live streaming and encoders

Restreaming an authenticated RTSP stream through Wowza Pro

As noted in this thread, adding a username:password to the url is simple.

rtsp://username:password@[camera-ip-address]:554/axis-media/media.amp

However is there any way to allow Wowza to use basic or (better) digest authentication instead of having the password in the URL? The reason is two-fold: better security and passwords that have characters that need encoding. The Axis camera will deny requests with urlencoded passwords as seen in the output of openRTSP. When authenticating via digest authentication and testing through openRTSP I can connect and record without an issue. Is there a way for Wowza to support digest authentication or even basic authentication where the username:password does not have to be in the url?

Thanks!

Michael
Comment

People who like this

0 Show 0
10 |600 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

2 Replies

· Add your reply
  • Sort: 
avatar image

Answer by Roger Littin · Nov 06, 2010 at 09:52 PM

The User:password in the url is basic authentication.

The RTP / Authentication / PublishMethod only works for streams that are initiated from the encoder so that will not work with Axis cameras.

If what you want to achieve is to hide the username & passwords from the user, you can use any of the following methods.

1. Use *.stream files. This is a simple text file on the server which contains the rtsp url. The player plays the stream file.

2. Use the StreamNameAlias plug-in.

3. Create a custom module that implements the IMediaStreamNameAliasProvider(2) interface. Use the resolveStreamAlias method to resolve the correct rtsp url. Make sure that the resolvePlayAlias method returns a valid name.
Comment

People who like this

0 Show 1 · Share
10 |600 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image Michael Wills · Nov 06, 2010 at 04:16 PM 0
Share
Hi Roger,

Basic authentication has been approved so far for this application so that is fine and I currently have it set up using a *.stream file. The issue seems to be how Wowza parses and passes the authentication data on to the Axis camera. The password contains a character that is not url safe and so must be url encoded in order to be able to resolve the host correctly. The *.stream file has the correct URL to the camera with the password urlencoded and this works within VLC. The Wowza log shows that it can't connect at all and the log shows the connection string with the password urlDEcoded. I'm not sure where it breaks down in the connection attempt.

So if the connection string without any url encoding would be

rtsp://username:p@ssword@[ip-address]/axis-media/media.amp

the url encoded one of course would be

rtsp://username:p%40ssword@[ip-address]/axis-media/media.amp

and this works in VLC. If I use this url encoded one in Wowza it says it can't connect and the logs show the non-url encoded version.

In openRTSP this results in an 401 unauthorized access. For openRTSP I have to do

openRTSP -u username p@ssword rtsp://[ip-address]/axis-media/media.amp

and that works fine. In QuickTime I can only use

rtsp://[ip-address]/axis-media/media.amp

and get the login prompt and that works. If I remove the offending character from the password Wowza correctly connects and also correctly gets a 401 unauthorized. My guess at this point is that if the password were changed to not have any characters that needed to be urlencoded, it may work correctly with Wowza. That would be the simplest solution. I can't see justifying going into custom code if it doesn't though.
avatar image

Answer by Roger Littin · Nov 07, 2010 at 01:39 AM

I have seen some issues on axis cameras to do with passwords and have normally fixed them but setting the camera to use un-encrypted passwords only.
Comment

People who like this

0 Show 2 · Share
10 |600 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image Michael Wills · Nov 08, 2010 at 10:33 AM 0
Share
I have seen some issues on axis cameras to do with passwords and have normally fixed them but setting the camera to use un-encrypted passwords only.


That confirms what I saw happening with Wowza although it seems that openRTSP can log in fine with Digest or Basic authentication. Thanks for the note.
avatar image Michael Wills · Nov 08, 2010 at 10:37 AM 0
Share
Just a note for others interested in this. After some discussion with Wowza's awesome support there is a new development build, patch 8, which resolves this issue.

Note if you are using it on EC2 though you'll have to be careful to merge the existing /conf/Server.xml with the new /conf/Server.xml provided in this patch, and also merge the existing /conf/VHost.xml with the new /conf/VHost.xml. But this is a development build so it may not be completely stable and requires further testing.

http://www.wowza.com/forums/content.php?199-Development-Builds

Your answer

Hint: You can notify a user about this post by typing @username

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Follow this Question

Answers Answers and Comments

1 Person is following this question.

avatar image

Related Questions

Using Apple's QuickTime Broadcaster with Wowza Server (RTSP/RTP) 27 Answers

does Wowza block thew Teradek Bond or Sputnik 3 Answers

Live Streaming recording on iOS 2 Answers

Live streaming with HTML5 3 Answers

RTMP vs RTSP 1 Answer

Hot Topics
  • AWS Hosting
  • Mobile SDK
  • Deployment Options
  • Load Balancing
  • Content Security
Product Sign-in
  • Wowza Streaming Cloud
  • Wowza Player
Under the Hood
  • Developer Tools
  • Wowza System Status
  • Test Players
  • Developer IDE
Resellers
  • Find a Reseller
  • Reseller Portal
  • Become a Reseller
Company
  • About Us
  • Blog
  • News
  • Events
  • Careers
  • Customers
  • Partners
  • Contact Us
Stay Connected
Get Monthly Newsletter
Select a Language
  • English
    • English
    • Español
    • 日本語
    • 한국어
    • हिन्दी भाषा
    • 中文
    • русский язык

© 2005–2018 Wowza Media Systems, LLC. All rights reserved.   Terms | Privacy | Trademarks | Legal


Enterprise
Social Q&A

  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Create an article
  • Forums
  • Wowza ClearCaster
  • Wowza Streaming Engine
  • Wowza Streaming Cloud
  • Wowza Player
  • Wowza GoCoder SDK
  • Wowza Developer Dojo
  • Explore
  • Topics
  • Questions
  • Users
  • Badges