<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Neil Madden</title>
    <description/>
    <link>https://speakerdeck.com/neilmadden</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/neilmadden.rss"/>
    <lastBuildDate>2018-12-08 09:53:51 -0500</lastBuildDate>
    <item>
      <title>OAuth 2: What could possibly go wrong?</title>
      <description>Presentation given at Bristech 2018 in Bristol, UK. I discuss various potential security issues to be considered when implementing OAuth 2.0 as a resource server and for clients on mobile, server-side and client-side javascript (single page apps). The talk covers the latest best common practice advice currently in development at the IETF OAuth Working Group, including potential deprecation of the implicit flow in favour of authorization code + PKCE.</description>
      <media:content url="https://files.speakerdeck.com/presentations/841f92c606c44d81abc8fed345e241b8/preview_slide_0.jpg?11399154" type="image/jpeg" medium="image"/>
      <content:encoded>Presentation given at Bristech 2018 in Bristol, UK. I discuss various potential security issues to be considered when implementing OAuth 2.0 as a resource server and for clients on mobile, server-side and client-side javascript (single page apps). The talk covers the latest best common practice advice currently in development at the IETF OAuth Working Group, including potential deprecation of the implicit flow in favour of authorization code + PKCE.</content:encoded>
      <pubDate>Thu, 06 Dec 2018 00:00:00 -0500</pubDate>
      <link>https://speakerdeck.com/neilmadden/oauth-2-what-could-possibly-go-wrong</link>
      <guid>https://speakerdeck.com/neilmadden/oauth-2-what-could-possibly-go-wrong</guid>
    </item>
  </channel>
</rss>
