OAuth2, IdentityServer3 and integrating it into your current app | Paul Glavich at DDD Sydney 2016 - SSW TV - Learn from Professional Software Developers

SSW TV brings you all the best content from this year’s DDD Sydney event.

In this presentation Paul Glavich shows us how to integrate OAuth2 and IdentityServer3 into you app. From the description:

“Oauth2 is used by many companies such as google and twitter to provide secure authorisation. IdentityServer is an excellent open sourced product on the .Net stack that provides support for the myriad of flows that OAuth2 specifies however it is a large beast to tackle. In this talk, we will talk about why you might want to use IdentityServer and then jump into the how. There is a lot of information distributed on the interwebs on how to do various integration points but this talk will aggregate the most common aspects into one, thrill seeking, token-fest of ‘Auth-omness’.”

We hope you enjoy this content. You can watch more of DDD on SSW TV.

Take the Poll

Which one of the following is NOT an OAuth2 flow:

Presentation Slides

OAuth2 and IdentityServer3 from Paul Glavich

About the speakers

Mr Oauth

Paul is currently an ASP.NET MVP and works as a Chief Technology Officer (CTO) for Saasu (saasu.com). Previously he was a senior consultant for readify, and prior to that a technical architect for EDS Australia. He has over 20 years of industry experience ranging PICK, C, C++, Delphi and Visual Basic 3/4/5/6 to his current speciality in .Net with C#, ASP.NET and WCF

Treat Your Code Like Uranium | Adam Cogan

Adam Cogan shares a striking story comparing two World War II factories—one ordinary, one handling uranium—and the surprising lesson that the uranium workers lived longer because they followed disciplined, risk-aware practices. He connects that idea to software teams: the best outcomes come from careful habits like automated tests, telemetry, pull requests, retrospectives, shared rules, and good tools. The message is simple: treat software delivery with the same respect as dangerous work, and you’ll reduce stress, avoid chaos, and get better results.

3 Tips for Better Video Recordings | Adam Cogan

Great coaching can dramatically improve how you present, communicate, and learn. In this video, Adam Cogan shares 3 practical coaching tips that SSW uses every day—from onboarding and role plays to improving video delivery. He explains why having a coach matters, why immediate interruption beats delayed feedback, and how repeating corrections helps lock in better habits.

TinaCMS + Fumadocs: Bring Visual Editing to Your Docs | Hark Singh

Discover how to connect Playwright with AI agents and unlock powerful workflows.

Stop Using 👍 Wrong in Teams | Adam Cogan

A quick communication tip from Adam Cogan: don’t use 👍 as a catch-all response when someone assigns you a task in Teams, Slack, or Google Chat. In the example Adam gives, if a task will take about five minutes, a thumbs up is too ambiguous because it does not clearly say whether you’ve read it, agree with it, are doing it now, or will do it later. Instead, use 👍 for agreement, 👀 to show you’ve seen the task and are actively working on it, and then replace 👀 with ✅ once the task is done. It is a small change, but it removes ambiguity and cuts down unnecessary follow-up messages.

How to record a done video in SSW | Sylvia Huang | SSW Rules

Sylvia Huang from SSW shares her SSW Cultural Exchange experience from Hangzhou, China to Australia

4 Essential Sales Tips for Engineers | Adam Cogan

Not a salesman? No problem. Adam Cogan shares 4 practical tips to help engineers navigate sales meetings with confidence. Learn how to stop “selling” and start solving, how to talk numbers without the awkwardness, and why being transparent about your process wins more clients.

Do you explain why you’ve deleted or updated an appointment? | Adam Cogan | SSW Rules

Ever wonder why a meeting was moved or cancelled? Adam Cogan explains the “Secret Ingredient” to professional scheduling: always include a version history and reason for change at the top of your appointments. Improve clarity, keep a record of changes, and hold participants accountable with this simple SSW Rule.

Chat first before changing others’ code | Adam Cogan

Changing someone else’s code? Don’t just dive in! Adam explains why it’s important to check the source history and talk to the original developer before making changes. A quick chat can save headaches and keep everyone on the same page. Perfect advice for devs working in teams!