security - request and access tokens in oauth -


can explain why request tokens must exchanged access tokens after user approval? why not pretend request token access token once user has approved access?

short answer : authenticate application.

refer youtube's oauth process flow diagram

oauth 3-legged protocol. in particular case, youtube needs authenticate 2 different entities - a) user , b) application needs accss.

now, after user grants access (step 10 in diagram), youtube knows "user x wants grant application y access youtube". hasn't yet verified application y. rogue application can perform steps step 10 pretending valid, known application - , such action must prevented.

in last 3 steps, application verifies youtube signing request. once done, youtube can safely provide access token application.


Comments

Popular posts from this blog

asp.net - repeatedly call AddImageUrl(url) to assemble pdf document -

java - Android recognize cell phone with keyboard or not? -

iphone - How would you achieve a LED Scrolling effect? -