# RTMP Kulabyte Haivision authentication **URL:** \ **Category:** Wowza Streaming Engine\ **Created:** [October 9, 2014, 2:58pm UTC](https://community.wowza.com/t/rtmp-kulabyte-haivision-authentication/40215 "2014-10-09T14:58:52Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Left\_Chal](https://avatars.discourse-cdn.com/v4/letter/l/48db29/32.png) [@Left\_Chal](https://community.wowza.com/u/Left_Chal)\ **Post date:** [October 9, 2014, 2:58pm UTC](https://community.wowza.com/t/rtmp-kulabyte-haivision-authentication/40215/1 "2014-10-09T14:58:52Z")
Hello, i own a Kulabyte Haivision encoder, i have an issue when i enable ModuleRTMPAuthenticate in the xml application file. When i enable the module the encoder cant connect to the wowza media server and when is disabled the connection established . Let me know if there is some issue where it is not working properly with Kulabyte encoders. ---
**Author:** ![sal\_jefferson](https://avatars.discourse-cdn.com/v4/letter/s/6de8d8/32.png) [@sal\_jefferson](https://community.wowza.com/u/sal_jefferson)\ **Post date:** [October 9, 2014, 7:57am UTC](https://community.wowza.com/t/rtmp-kulabyte-haivision-authentication/40215/2 "2014-10-09T07:57:32Z")
Hello there, First, can you confirm you are entering the publisher name and password correctly when ModuleRTMPAuthenticate is enabled? Second, you could try adding the name of the encoder to the Flash Version String field. If you are not sure what to put here, you can find it by looking for a line like this in the logs: ```auto INFO server comment 2011-01-14 22:16:23 - - - - - 2.894 - - - - - - - - Flashver: Wirecast/FM 1.0 (compatible; FMSc/1.0) ``` You can edit this field at: ```auto Engine Manager > App name > Incoming Security > Flash Version String ``` And here is the guide for further reference: [How to configure security using Wowza Streaming Engine Manager](https://www.wowza.com/docs/how-to-configure-security-using-wowza-streaming-engine-manager) Lastly, are you seeing any indication of the issue output to the Wowza logs? You can start Wowza in stand-alone mode [install-dir]/bin/startup.bat|startup.sh and view the output in the console. Or you can find the logs at [install-dir]/logs Thank you, Salvadore ---
**Author:** ![sal\_jefferson](https://avatars.discourse-cdn.com/v4/letter/s/6de8d8/32.png) [@sal\_jefferson](https://community.wowza.com/u/sal_jefferson)\ **Post date:** [October 14, 2014, 5:18am UTC](https://community.wowza.com/t/rtmp-kulabyte-haivision-authentication/40215/3 "2014-10-14T05:18:15Z")
In Wowza 3.x, you need to add the “AllowEncoder” property to the Application.xml /Properties list, at bottom of the file: ```auto AllowEncoder FM ``` “FM” should work as the userAgent of the encoder, if not, look in the access log and you should see the userAgent of the encoder. Copy that to the AllowEncoder Property Value. Thank you, Salvadore ---
**Author:** ![sal\_jefferson](https://avatars.discourse-cdn.com/v4/letter/s/6de8d8/32.png) [@sal\_jefferson](https://community.wowza.com/u/sal_jefferson)\ **Post date:** [October 14, 2014, 9:32am UTC](https://community.wowza.com/t/rtmp-kulabyte-haivision-authentication/40215/4 "2014-10-14T09:32:03Z")
Please restart Wowza and try to publish again, then zip up conf and logs folders and send to support@wowza.com Tell us which application you are using, and any custom code you may have. Include the connection URL you are using in the encoder Include a link to this thread for reference. Thank you, Salvadore ---
**Author:** ![sal\_jefferson](https://avatars.discourse-cdn.com/v4/letter/s/6de8d8/32.png) [@sal\_jefferson](https://community.wowza.com/u/sal_jefferson)\ **Post date:** [October 14, 2014, 9:39am UTC](https://community.wowza.com/t/rtmp-kulabyte-haivision-authentication/40215/5 "2014-10-14T09:39:09Z")
Actually, before you open a ticket, have you read through this article carefully? [How to enable username/password authentication for RTMP and RTSP publishing](https://www.wowza.com/docs/how-to-enable-username-password-authentication-for-rtmp-and-rtsp-publishing%28ModuleRTMPAuthenticate%29) Salvadore ---
**Author:** ![sal\_jefferson](https://avatars.discourse-cdn.com/v4/letter/s/6de8d8/32.png) [@sal\_jefferson](https://community.wowza.com/u/sal_jefferson)\ **Post date:** [October 16, 2014, 3:44pm UTC](https://community.wowza.com/t/rtmp-kulabyte-haivision-authentication/40215/6 "2014-10-16T15:44:27Z")
Thank you for the update, and I am glad to hear you got this sorted. Salvadore ---
**Author:** ![Left\_Chal](https://avatars.discourse-cdn.com/v4/letter/l/48db29/32.png) [@Left\_Chal](https://community.wowza.com/u/Left_Chal)\ **Post date:** [October 14, 2014, 11:20am UTC](https://community.wowza.com/t/rtmp-kulabyte-haivision-authentication/40215/7 "2014-10-14T11:20:18Z")
Hello, 1. The publish name and password are correct i use an other FMLE encoder to connect and everything is OK 2. Adding the name of the encoder to the Flash Version String field. Is there any other module i cant find this line into Application.xml How can do that with Wowza Media Server 3 Perpetual Edition 3.6.3 1. From logs 2014-10-14 11:56:53 EEST connect-pending session INFO 100 … Kulabyte (compatible; FMSc/1.0) Thank you. ---
**Author:** ![Left\_Chal](https://avatars.discourse-cdn.com/v4/letter/l/48db29/32.png) [@Left\_Chal](https://community.wowza.com/u/Left_Chal)\ **Post date:** [October 14, 2014, 2:38pm UTC](https://community.wowza.com/t/rtmp-kulabyte-haivision-authentication/40215/8 "2014-10-14T14:38:37Z")
No it doesnt work for me, i also tryied [Allow encoders in wowza](http://community.wowza.com/t/-/36572) but i cant connect . ---
**Author:** ![Left\_Chal](https://avatars.discourse-cdn.com/v4/letter/l/48db29/32.png) [@Left\_Chal](https://community.wowza.com/u/Left_Chal)\ **Post date:** [October 15, 2014, 3:30pm UTC](https://community.wowza.com/t/rtmp-kulabyte-haivision-authentication/40215/9 "2014-10-15T15:30:53Z")
FYI Kulabyte Haivision mention ,that the connection to Wowza should be Open. No authentication required under Incoming Security, so i used the ModuleSecureURLParams module [https://www.wowza.com/docs/how-to-secure-publishing-from-an-rtmp-encoder-that-does-not-support-authentication-modulesecureurlparams](https://www.wowza.com/docs/how-to-secure-publishing-from-an-rtmp-encoder-that-does-not-support-authentication-modulesecureurlparams) and works fine for me. Thank you