<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Authorization on dplabs — Software Engineering &amp; Technology Consultancy</title>
		<link>https://dplabs.tech/tags/authorization/</link>
		<description>Recent content in Authorization on dplabs — Software Engineering &amp; Technology Consultancy</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 29 Jun 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://dplabs.tech/tags/authorization/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Secure by Default: APIs That Are Hard to Misuse</title>
				<link>https://dplabs.tech/blog/secure-by-default-apis/</link>
				<pubDate>Mon, 29 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/secure-by-default-apis/</guid>
				<description>&lt;p&gt;Security by default is a design principle, not a feature list. An API is secure by default when using it correctly produces secure behavior automatically, and producing insecure behavior requires deliberate effort.&lt;/p&gt;&#xA;&lt;p&gt;Most security failures are not the result of sophisticated attacks on well-designed systems. They&amp;rsquo;re the result of developers using APIs incorrectly, making incorrect assumptions about what defaults are safe, or forgetting to add security checks that should have been built in.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Authentication vs Authorization: Two Problems People Keep Conflating</title>
				<link>https://dplabs.tech/blog/authentication-vs-authorization/</link>
				<pubDate>Mon, 24 Mar 2025 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/authentication-vs-authorization/</guid>
				<description>&lt;p&gt;&amp;ldquo;Authentication&amp;rdquo; and &amp;ldquo;authorization&amp;rdquo; are often used interchangeably. They&amp;rsquo;re not the same problem, they&amp;rsquo;re not the same solution, and conflating them produces security architectures that fail in predictable ways.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-definitions-that-matter&#34;&gt;The Definitions That Matter&lt;/h2&gt;&#xA;&lt;p&gt;&lt;strong&gt;Authentication&lt;/strong&gt;: verifying who someone is.&lt;/p&gt;&#xA;&lt;p&gt;A request is authenticated when the system has verified that the claimed identity (user, service) is legitimate. After authentication, you know &lt;em&gt;who&lt;/em&gt; is making the request.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Authorization&lt;/strong&gt;: determining what someone is allowed to do.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
