# Signed (with Secure Token) RTSP url is inaccessible
**URL:** https://community.wowza.com/t/signed-with-secure-token-rtsp-url-is-inaccessible/47967
**Category:** Wowza Streaming Engine
**Created:** [February 3, 2017, 11:28am UTC](https://community.wowza.com/t/signed-with-secure-token-rtsp-url-is-inaccessible/47967 "2017-02-03T11:28:25Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Tomasz\_Rybarczyk](https://community.wowza.com/u/Tomasz_Rybarczyk)
#### Post date: [February 3, 2017, 11:28am UTC](https://community.wowza.com/t/signed-with-secure-token-rtsp-url-is-inaccessible/47967/1 "2017-02-03T11:28:25Z")
I’ve got some problems with signed (with Secure Token) RTSP url. All other protocols works for me. I’m not sure, but I think that we’ve tested our code on previous versions of WowzaStreamingEngine 4 and it worked, but I’ve started noticing it on 4.6.0, but I can be wrong…
Scenario:
- I’m trying to request data from this url:
- I’m getting 403 response.
- What is really funny, provided hash is correct (from logs):
- Of course I’ve tried also simplest possible option and made requests without any parameters - like this:
- All the time I’m getting this error:
- I’ve tried also turn on DEBUG logging, but it didn’t provide any additional information.
- I’ve done all these tests on Wowza 4.6.0 with my developement keys.
- Without secure token I can access this stream freely.
---
### Author:  [@Tomasz\_Rybarczyk](https://community.wowza.com/u/Tomasz_Rybarczyk)
#### Post date: [February 16, 2017, 9:26am UTC](https://community.wowza.com/t/signed-with-secure-token-rtsp-url-is-inaccessible/47967/2 "2017-02-16T09:26:14Z")
After update to WowzaStreamingEngine-4.0.6.02 all my tests are passing and rtsp protection works fine!