views:

76

answers:

1

subject says all, the REST api docs seem to make me think I do (and if I dont my code doesnt work)

Do: -hard code ProductToken -ask user for authorization key

DoNot: -hard code (or use) access key ID -hard code (or use) secret access key

keep in mind this is for an application that uses devpay, not a website

thanks!

A: 

Either hardcode it or store it in an encrypted DB or XML file, as for Secret Key and Key ID, it is better to not hard code your own keys maybe as mentioned above store them in an encrypted file somewhere in your app and once you get the user Keys successfully delete the file that has your own keys or replace your keys with the new user credentials as you wont be needing your keys once the customer has successfully activated your product.

sure its always better to hide the ProductToken from the user rather than asking the user to input it manually because once your Product token goes public people can easily access your buckets and do whatever changes they like and you'll probably lose control of your data flow.

Red Serpent
so it's okay to hardcode my ProductToken into my app? if I dont hard code it how do I protect it? seems thta no matter what I do it'd be possible to hack, all I can do is make it harder?
stuck
Well another method is simply to store the Tokens in an encrypted/secure online database. But this will slow you down because each time you want to send a request you'll have to communicate with your DB first, get the user credentials and then send the request. Not mentioning the agony of data filtering and user verification.Plus I don't think it is possible to hard code the accesskey and accesskeyID since you wont be having those to begin with until the user activates the product and your credentials wont do you any good considering your application is a desktop product.
Red Serpent