Description
Many services such as Facebook, GitHub, and Google have already deployed OAuth 2.0 servers. The OAuth 2.0 spec leaves many decisions up to the implementer. Instead of describing the possible decisions that need to be made to successfully implement OAuth 2.0, this lecture will explain most of the appropriate decisions to make for most implementations. This lecture is an attempt to explain OAuth 2.0 in a simplified format to help developers and service providers implement the protocol. Attendees will also discover how they can use other people's OAuth servers instead of implementing their own.
Key Learnings
- Understand differences between OAuth versions
- Understand requirements for implementing your own OAuth server
- Learn why you should use OAuth and how to use OAuth when exposing an API or using a third-party API
- Learn how to use third-party OAuth server in your infrastructure
Speakers
Cyrille FauvelCyrille Fauvel got his first computer when he was 12 years old, and as he had no money left to buy software, he started writing code in assembly code. A few years later, he wrote code in Basic, Pascal, C, C++, and so on, and he’s still doing that. He’s been with Autodesk, Inc., since 1993, joining the company to work on AutoCAD software originally. He’s passionate about technology and computers. At Autodesk he’s worked in various roles, from the design side to manufacturing and finally to games and films. He is now an evangelist for the Forge API (application programming interface) and web services, and he has a desire to deliver the most effective creative solutions to partners using these APIs and web services.- PLPhilippe LeefsmaI write JavaScript for the future 3D World Wide Web, A.K.A Autodesk forge Platform.
Video Player is loading.
No transcript