<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Oauth on Theddy Dev Space</title><link>http://theddy.dev/tags/oauth/</link><description>Recent content in Oauth on Theddy Dev Space</description><generator>Hugo -- 0.150.0</generator><language>en-us</language><lastBuildDate>Tue, 07 Apr 2026 13:40:25 +0300</lastBuildDate><atom:link href="http://theddy.dev/tags/oauth/index.xml" rel="self" type="application/rss+xml"/><item><title>The Framework Behind Modern Authorization - OAuth</title><link>http://theddy.dev/posts/oauth2/</link><pubDate>Tue, 07 Apr 2026 13:40:25 +0300</pubDate><guid>http://theddy.dev/posts/oauth2/</guid><description>&lt;h2 id="history"&gt;History&lt;/h2&gt;
&lt;p&gt;Before OAuth 2.0, giving access to third party applications to a requested resource, meant we needed to type our credentials - username and password, which are stored on the 3P side and used as an action which was performed on our behalf.&lt;/p&gt;
&lt;p&gt;This is a problem, firstly, because they can be used to access all kinds of resources, not a limited scope of them, no revocation was possible, and secondly, third party software stored those in plaintext. If the third-party software was compromised, our data was also at risk.&lt;/p&gt;</description></item></channel></rss>