Results 1 to 4 of 4

Thread: GoCoder and publish.password for authentication

  1. #1

    Default GoCoder and publish.password for authentication


    Right now, in order to authenticate GoCoder, you must include your user credentials in "[install-dir]/conf/publish.password" ..

    Is there any way to tell Wowza to look at the "[install-dir]/applications/[appname]/publish.password" file instead?

    It would seem that if all usernames/passwords are stored in that one file (and not separated by applications), it will allow any user/pass to publish to any application which is a problem.


  2. #2


    Hello there,

    Please see this article:
    How to use a per application publish.password file

    Kind regards,


  3. #3


    Thank you.

    It would appear, for Wowza 4.x, we need to have the following property added:


    Thanks for the tip!

  4. #4


    Yes, that is right. I am sorry, it looks like I linked to the old method.

    Thanks for pointing this out. And for anyone looking for this in the future, here is the updated method:
    Configure per-application authentication using properties

    Thanks again.


Similar Threads

  1. publish.password need
    By tavius in forum GoCoder iOS app
    Replies: 2
    Last Post: 02-03-2014, 03:16 PM
  2. How to publish live streaming with publish.password file?
    By divyat in forum Live Streaming and Encoder Discussion
    Replies: 1
    Last Post: 11-17-2012, 09:09 AM
  3. connect.password vs. publish.password - protecting upstream
    By riverjack in forum Server Administration Discussion
    Replies: 3
    Last Post: 06-15-2012, 05:00 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts