6. Secure, but…
• Relies on a calculated signature to ensure
security between server and consumer
• Secure for end user but pain for
developer to implement
• Difficult to debug 401 unauthorized when
signature is bad (nonce, timestamp, etc)
• Not all OAuth libraries are created equal
Developer Relations
8. OAuth 2.0
• Easier to code
• Relies on SSL instead of complicated
signatures
• Still provides secure authorization for
end user
• Supports scopes for granular member
permissions
Developer Relations
9. LinkedIn + OAuth 2.0
How easy is it to authorize a
LinkedIn user to my app??
Developer Relations