Authentication with Oauth 2.0
Will there be any ability to do 3rd party authentication with Oauth 2.0, or will it remain in Oauth 1.0a?
You can also read more about this in our Future of the API page. https://developer.twitter.com/en/products/twitter-api/early-access/guide#oauth2
If you perfect person and you never did something wrong you can do whatever you want only remember every activity came the consequences
Rahul Ganju commented
OAuth 2.0 is a complete rewrite of OAuth 1.0 from the ground up, OAuth 2.0 is not backwards compatible with OAuth 1.0 or 1.1, and should be thought of as a completely new protocol.
OAuth 2.0 is definitely an improvement over its arcane predecessor. Instances of developer community faltering while implementing the signatures of 1.0 are not unknown. OAuth 2.0 also provides several new grant types, which can be used to support many use-cases like native applications, but the USP of this spec is its simplicity over the previous version.
There are a few loose ends in the specification, as it fails to properly define a few required components, the big one -Security
Security: The spec just "recommends" the use of SSL/TLS while sending the tokens in plaintext over the wire. Although, every major implementation has made it a requirement to have secure authorization endpoints as well require that the client must have a secure redirection URL, otherwise it will be way too easy for an attacker to eavesdrop on the communication and decipher the tokens.