When running Nimble and WMSAuth with the Cloudfront CDN, I'm getting the following error message in the WMSAuth log, and the message is showing repeatedly from multiple IP addresses:
"cannot find hash match for 220.127.116.11 signature=[wmsAuthSign]"
And the IP addresses all resolve to Amazon (which I'm assuming is due to the Cloudfront distribution accessing the streaming server).
Is it possible to use WMSAuth (to avoid hot linking) together with Cloudfront?
If some CDN network is used, it is considered, that access to streams will be controlled via CDN.
WMSAuth won't work in such a scenario, as the session could not be established directly with the viewer, so the Nimble can't control if a viewer has a permission to view a stream.
Thanks Sergei. We were hoping to use the WMSAuth system as it is perfect for what we need and the CDN doesn't really have anything like this out of the box. Is it possible to use the WMSAuth without the IP address check? I did see somebody in these forums mentioning this might be possible using a variation of the PPV auth - would this be something that you would recommend?
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