Last week at the Engage user group in Eindhoven, The Netherlands, I gave a session on OAuth 2.0, how the protocol works and how easy it is the code against. The demo I showed at the end of the session showed just how easy it is and how little code is required to make a fully functioning OAuth 2.0 Client. Below you’ll find the slides on Slideshare as well as a recorded, narrated, demo. The demo walks you through coding an OAuth 2.0 app in Eclipse and deploying it to IBM Bluemix.
Oh and do remember… Never, EVER, use a library until you understand the protocol.
OAuth is core to integrations these days but I see many developers that try and use OAuth without really understanding the protocol. The protocol is very easy to understand so I created this presentation to try and explain it in easy, visual, chunks. I’ll present on the topic tomorrow (Friday 6 November 2015) at the Social Connections IX conference in Stuttgart, Germany. I hope you’ll come see it live if you are at the conference.
Thanks for all the e-mail and all the IM’s reminding me that Twitter would retire the use of basic authentication (username/password) in client applications on 30 June 2010. After that announcement it was postponed to 16 August 2010 so there’s still time… That’s how I read the frontpage of the Twitter API wiki as of today anyway.
Nathan was the first to poke me and remind of it and ever since the reminders have been tickling in. Happy to see that so many are using TwitNotes and is using it enough to actually be bothered by it not working. I’m in the process of testing an OAuth approach using Scribe and hopefully the solution will be ready soon and in good time before the deprecation… 🙂