<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OAuth on Yunier&#39;s Wiki</title>
    <link>http://localhost:1313/tags/oauth/</link>
    <description>Recent content in OAuth on Yunier&#39;s Wiki</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 05 Jun 2022 00:00:00 +0000</lastBuildDate>
    <atom:link href="http://localhost:1313/tags/oauth/rss" rel="self" type="application/rss+xml" />
    <item>
      <title>Authorization Code From Terminal</title>
      <link>http://localhost:1313/post/2022/authorization-code-from-terminal/</link>
      <pubDate>Sun, 05 Jun 2022 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/post/2022/authorization-code-from-terminal/</guid>
      <description>&lt;p&gt;I was recently presented with a unique challenge at work. I needed to create a script that clones repositories from Bitbucket. The problem is that as of June 2022, Bitbucket only supports managing repositories using OAuth via two grant types, the authorization code grant &amp;amp; the implicit grant.&lt;/p&gt;&#xA;&lt;p&gt;I won&amp;rsquo;t get into the details here but the implicit grant is no longer recommended and is in fact discouraged from ever being used. Regardless of which flow I use I will end up facing the same problem, the browser. In both the implicit and authorization grant, user interaction (3-legged OAuth) is required, the end-user must provide their credentials in order to properly authenticate, in some cases this may even include multifactor authentication.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
