# Proper workflow with publishing security, and letting users livestream by themselves

**URL:** <https://community.wowza.com/t/proper-workflow-with-publishing-security-and-letting-users-livestream-by-themselves/43209>\
**Category:** Wowza Streaming Engine\
**Created:** [June 12, 2014, 1:09am UTC](https://community.wowza.com/t/proper-workflow-with-publishing-security-and-letting-users-livestream-by-themselves/43209 "2014-06-12T01:09:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Allan\_Smith](https://avatars.discourse-cdn.com/v4/letter/a/73ab20/32.png) [@Allan\_Smith](https://community.wowza.com/u/Allan_Smith)\
**Post date:** [June 12, 2014, 1:09am UTC](https://community.wowza.com/t/proper-workflow-with-publishing-security-and-letting-users-livestream-by-themselves/43209/1 "2014-06-12T01:09:04Z")

</div>

I have a wowza origin server setup for live streaming with 1 publishing username/password, and a separate server setup ([asp.net](http://asp.net)) for a live streaming site frontend. After the user has logged into the frontend site I want to let them start live streaming by providing the URL of my origin server and some custom stream name (eg. [http://1.1.1.1:1935/livestream/user9\_06\_12\_2014](http://1.1.1.1:1935/livestream/user9_06_12_2014)) However my concern is that I don’t want to share my global publishing username/password setup with that user.

How can I properly share this URL and let them publish their rtsp/rtmp stream and not give out my global pushing user/pass?

Is there a way to generate new username/password via API so that everytime someone signs up on my frontend site they automatically get a custom publishing account? Would there be a limit to max # of accounts in this case in Wowza?

TY

---

<div class="post-metadata">

**Author:** ![Zoran](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/zoran/32/385_2.png) [@Zoran](https://community.wowza.com/u/Zoran)\
**Post date:** [June 12, 2014, 10:46am UTC](https://community.wowza.com/t/proper-workflow-with-publishing-security-and-letting-users-livestream-by-themselves/43209/2 "2014-06-12T10:46:22Z")

</div>

Hello,

Please take a look at the “[How to integrate Wowza user authentication with external authentication systems (ModuleRTMPAuthenticate)](https://www.wowza.com/docs/how-to-integrate-wowza-user-authentication-with-external-authentication-systems-modulertmpauthenticate%28ModuleRTMPAuthenticate%29)” forum article. Youmight find it useful when implementing the workflow you have described.

Regards,

Zoran

---

<div class="post-metadata">

**Author:** ![Allan\_Smith](https://avatars.discourse-cdn.com/v4/letter/a/73ab20/32.png) [@Allan\_Smith](https://community.wowza.com/u/Allan_Smith)\
**Post date:** [June 14, 2014, 12:17pm UTC](https://community.wowza.com/t/proper-workflow-with-publishing-security-and-letting-users-livestream-by-themselves/43209/3 "2014-06-14T12:17:15Z")

</div>

Hi Zoran,

Thank you for the quick reply. I believe this model is for viewing security, but I am interested in publisher security. Also I need RTSP support.

Lets say I have 3 users registered on my site:

UserA, UserB, UserC.

I want to let each of the 3 users publish their stream via FFMPEG. The stream names would be username + 5 digit number (which my randomly generated and stored in sql on my frontend server). So stream names can be something like:

UserA11111

UserB22303

UserC90293

This way I have security on the streaming end (with the extra token on the end of the stream name). However I need help to secure the publish name. I want to make sure each user only has authority to publish to a specific stream name (ie. UserA can only publish to stream UserA11111, and UserA should not be able to publish to UserA22222. How can I best accomplish this?

Thanks