On Thursday, May 2, 2013 6:24:57 AM UTC-4, José F. Romaniello wrote: > With the Resource Owner Password Credentials flow you need to have the > resource owner credentials (client id and secret) embed in your android > application. > > This is not good, no matter how hard you obfuscate. Few weeks ago someone > published the client id and client secret that all versions of Twitter for > OS[x] uses. > Yes, great points: I specifically want to avoid storing anything that would be useful to an attacker on the app locally.
Thanks for all the helpful replies! I decided to look into a jwt-simple implementation going forward in the next few days. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
