Temporary Key? in the Server's individual channel urls

Answered

Follow

Jeff Jones

• December 01, 2018 07:36
• Edited

In version 3.2 the server's Camera Details Panel has a checkbox called "Use temporary key".

How temporary is that?

The "Duration (sec)" field which defaults to 300 doesn't seem to kill the feed even an hour later.  Is it supposed to or is this more like a random url that lasts forever?

I'm trying to figure out if I can feed a camera to a viewer that is having trouble with the credential method, but seems to work fine with the temporary key. Is the feed going to stop sometime during the future, after a reboot maybe? Can I force it to stop if someone got a hold of the URL that wasn't supposed to?

0

• 

  Evgeny Balashov

  • December 02, 2018 20:43

  Duration is related to the length for the download link. By default, it is will download 5 minutes (300 seconds).

  The temporary key works like a session: if the session is not active for about 30 minutes or so - it will expire and the link will not work anymore. If the session is always active, for example, the stream keeps going - the session will not expire and the link will work.

  The good thing about this temporary key is that it doesn't contain the password, so if the key is stolen - hacker won't be able to do much with it. All critical changes require the password.

  On the other hand, if the link is going to be public - we still recommend using only a user with limited access. 

   

  If you are interested in how this temporary link works (you can generate one yourself) - check 'For developers' section in web administration interface -> 'API testing tool' -> 'Calculating authentication hash' and 'URL-based authentication'

   

  BTW, what is the problem you are trying to solve with the temporary key? What are the requirements?

   

  0

  Permalink
• 

  Jeff Jones

  • December 03, 2018 01:34

  I am attempting to display cameras in the ActionTiles control software for Samsung Smartthings. For whatever reason ActionTiles can't handle the user/password credential so it needs some kind of key built into the URL. However, it needs to be somewhat permanent so the end user doesn't have to go back and input a new URL into ActionTiles every so often.

  0

  Permalink
• 

  Evgeny Balashov

  • December 03, 2018 05:34

  Is it possible to call a javascript function to generate the URL dynamically? Or generate them on the backend somehow?

  0

  Permalink
• 

  Evgeny Balashov

  • December 03, 2018 05:38

  You can also try this format: http://username:password@serverIp:7001/... and check if ActionTiles support it.

  0

  Permalink
• 

  Jeff Jones

  • December 03, 2018 05:41

  ActionTiles won't load the camera when using the http://username:password@serverIp:7001/ format.  That is why I was looking for another method and realized the Temporary Key worked, but wasn't sure if it would last.

  0

  Permalink
• 

  Jeff Jones

  • December 03, 2018 05:46

  What are you talking about with the Javascript function?

  0

  Permalink
• 

  Evgeny Balashov

  • December 03, 2018 07:12

  If you can place some code to generate temporary key dynamically somewhere - that would provide a reliable solution. This can be done using javascript in the browser, or on the backend.

  Authentication keys also expire if the server restarted for any reason, for example.

  0

  Permalink

Please sign in to leave a comment.