search

Nico113 / mpoauthconnection

Automatically exported from code.google.com/p/mpoauthconnection
0 stars 0 forks source link

Keychain credentials should be validated against the consumer key / secret. #7

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Set consumer / secret and get an request & access token.
2. Change consumer / secret
3. Previous access token / secret & session handle are still used.

What is the expected output? What do you see instead?

The consumer key and secret should be stored in the keychain and validated
against the values of kMPOAuthCredentialConsumerKey,
kMPOAuthCredentialConsumerSecret.

What version of the product are you using? On what operating system?
r28 of MPOAuthMobile

Please provide any additional information below.

Original issue reported on code.google.com by zagra...@gmail.com on 27 Jan 2009 at 11:19

GoogleCodeExporter commented 9 years ago 
Good catch, was an edge case for me, but very valid for testing

Original comment by karl.a...@gmail.com on 27 Jan 2009 at 11:27