doesn't match hash calculated - vod+securetoken(v2)+clienip - missing _definst_

Wowza Streaming Engine
1

— hi i am trying to secure a vod mp4 file using

securetoken v2 plus client ip

Randomly the video is stopping in different spots! … some times 5 min, sometimes 14 min

upon more investigation… i found that wowza side string hash calculation is missing definst in the string.

in the hash string… causing wowza to calculate wrong hash.

server side : vodc/definst/mp4:remotehost/vod/movie.mp4

wowza side: string hashed string hashed: vodc/mp4:remotehost/vod/movie.mp4

not sure how to fix it!

logs below

2015-11-19

13:34:47 (EST)

comment

server (200)

HTTPStreamerAdapterCupertinoStreamer.onMediaFile[vodc/definst/mp4:remotehost/vod/movie.mp4/media_w198079091_tkdG9rZW5zdGFydHRpbWU9MTQ0Nzk1Njc1MCZ0b2tlbmVuZHRpbWU9MTQ0Nzk3ODMyMCZ0b2tlbmhhc2g9dG1nTEhZZ3V5T0VrNFRXcEV1UTJ4QWQwZGgzOVdlNnI4c2ozbG10c25lQT0=_114.ts]: Session not accepted.

x-duration: 1301.174

2015-11-19

13:34:47 (EST)

comment

server (200)

[vodc/definst]SecureTokenDef:Hash tmgLHYguyOEk4TWpEuQ2xAd0dh39We6r8sj3lmtsneA=, doesn’t match hash calculated, HDAXHUNXQuuxkwQlx4juGIOCjdfoOY6_3aHufE6SzEw=

x-duration: 1301.174

2015-11-19

13:34:47 (EST)

comment

server (200)

[vodc/definst]ModuleCoreSecurity:token end time stamp: 1447978320

x-duration: 1301.173

2015-11-19

13:34:47 (EST)

comment

server (200)

[vodc/definst]ModuleCoreSecurity:token start time stamp: 1447956750

x-duration: 1301.173

2015-11-19

13:34:47 (EST)

comment

server (200)

[vodc/definst]ModuleCoreSecurity:string hashed: vodc/mp4:remotehost/vod/movie.mp4?xx.xx.xx.xx&966a0ef2a7c9b272&tokenendtime=1447978320&tokenstarttime=1447956750

x-duration: 1301.173

2015-11-19

13:34:47 (EST)

comment

server (200)

[vodc/definst]ModuleCoreSecurity:hashCalculated: HDAXHUNXQuuxkwQlx4juGIOCjdfoOY6_3aHufE6SzEw=

x-duration: 1301.173

2015-11-19

13:34:47 (EST)

comment

server (200)

[vodc/definst]ModuleCoreSecurity:client IP: xx.xx.xx.xx

x-duration: 1301.173

2015-11-19

13:34:47 (EST)

comment

server (200)

[vodc/definst]ModuleCoreSecurity:creating httpToken for SessonId:198079091 uri:/vodc/definst/mp4:remotehost/vod/movie.mp4/media_w198079091_tkdG9rZW5zdGFydHRpbWU9MTQ0Nzk1Njc1MCZ0b2tlbmVuZHRpbWU9MTQ0Nzk3ODMyMCZ0b2tlbmhhc2g9dG1nTEhZZ3V5T0VrNFRXcEV1UTJ4QWQwZGgzOVdlNnI4c2ozbG10c25lQT0=_114.ts

x-duration: 1301.173

2

solved -

after extensive back and forth with wowza engineers via ticket submitted with conf/logs!

looks like a 3rd party app wmspanel security custom module was causing this conflict with wowza 4.3.0.01 secure token

you can close this thread!

3

Thanks for the update and glad you sorted this out.

Salvadore