C:\trunk\fl5\src\com\longtailvideo\jwplayer\utils\Strings.as, Línea 84 1180: Llamada a un método JSONDecoder posiblemente no definido.
C:\trunk\fl5\src\com\longtailvideo\jwplayer\utils\Strings.as, Línea 2 1172: No se encontró la definición com.adobe.serialization.json:JSONDecoder.
Could you please tell me how to solve them, or if they are essential for jw player to work with token?
I'm not sure how to help with this. Have you asked on the JW Player forum? I think this is going to become increasingly difficult because, as I understand it, the source for premium and enterprise editions is not available, so you can only do it with free version which lacks some features, like HLS to the desktop (tho SecureToken is not used in HLS streaming), and JW Player 5, which you are using, I don't think is available anymore.
Yes I have already asked them and I am waiting for an answer. Flash builder? It was not only needed the adobe flash professional to compile it?
Don´t you have any tutorial about how to use the token with any player without receiving errors?
I do not know what more to do and I need to secure my rtmp
Keep in mind that SecureToken only works with RTMP (and variants), and you will want to use HotLinkDenial (or htaccess rules to prevent hotlinking) and RTMPS (preferred) or RTMPE protocol to make a complete solution
Note that as far as I know the source code for the premium and enterprise versions of JW player are not available, but the main strength of those versions for streaming purposes is HLS to the desktop, which does not support SecureToken.
I am already using hotlinkdenial, but although I am using it there are people that continue taking my channel without doing iframe to my webpage.
but, with the source code for jw player 6 I can use secure token no?
I mean the only thing I want is to protect my channel because somone is still stealing my channel
You use SecureToken to ensure that only your player will work with your content, and you use HotLinkDenial to make sure no one will hotlink the player you have secured, and use RTMPS or RTMPE to encrypt the stream itself. So these are all used together. The readme.txt file in the source code has instructions for compiling, I can't help more with that.
The problem is though, people can view source, grab the swf, and decompile and easily get the token, I know personally that even with obfuscation people can just grab the token even with rtmpe or rtmps. Plus they can spoof the website, I am sure you guys have heard of rtmpdump by now.