Skip to content

Added read-only api key as an option for progress requests - #27

Closed
stormtek wants to merge 1 commit into
bitzeche:masterfrom
stormtek:master
Closed

stormtek wants to merge 1 commit into
bitzeche:masterfrom
stormtek:master

Conversation

@stormtek

Copy link
Copy Markdown
Contributor

For security reasons we do not want to send an api key as part of the url for any requests to Zencoder. On enquiring about this with them we were informed that you can create a read only api key - which can only be used for things like progress requests, and not for creating jobs. This means that even if someone gets hold of it they are unable to abuse our account, merely to try and monitor what we are doing. If this read only key is not set in the constructor then the code behaves as before, using the main api key.

@drallgood

Copy link
Copy Markdown
Contributor

To be honest, I don't see the point of this.
Security-wise it doesn't make much sense either.

We are sending the requests over a HTTPS connection. So, if someone is able to observe the URL he is also able to observe the request body. In that case, all it takes to get the unlimited api key is a single job creation request.

@drallgood drallgood closed this Feb 21, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants