I know a while back I requested the feature where we would be able to use the ip and id at the same time for the wmsauth signature and I was sure that you said it was implemented. I have since changed my email address so I've lost the support message explaining the right order for the hash.
Thanks for your help
Feature was added in 3.1.4-3
3.1.4-3 Dec 12 2016
- Fixed setting icecast bitrate for mpegts mp3 streams
- Some improvements in transcoder
- Improve transmuxing performance when remote VOD storage is used
- Support validating client IP in PPV signatures
This revision adds support for "checkip=true" parameter to wmsAuth.
If this parameter exists in wmsAuth Nimble will validate both ppv id and viewer ip. By default if ppv id exists viewer ip not checked
In order to use the "checkip=true", we need to hash the ip and the id in a specific order in order to match with the server side. I currently don't have this information and cannot find it anywhere.
If "checkip=true"presented in wmsAuthSign you need to add
client_ip first and then add client_id to your hash
It`s very important feature. Please add this in ducumentation.
Pavel, thanks for your notice, we added checkip description to this article: https://wmspanel.com/nimble/pay_per_view
and required to achieve the purposes illustrated in the
If you want to know more or withdraw your consent to all or some of the cookies, please
refer to the