<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>🔐 Authentication on Software Design</title><link>https://software-design.dev/backend/authentication/</link><description>Recent content in 🔐 Authentication on Software Design</description><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2026 Daniil Dzemidovich</copyright><lastBuildDate>Tue, 21 Feb 2023 13:26:53 +0300</lastBuildDate><atom:link href="https://software-design.dev/backend/authentication/index.xml" rel="self" type="application/rss+xml"/><item><title>Basic Auth</title><link>https://software-design.dev/backend/authentication/basic-auth/</link><pubDate>Sun, 05 Feb 2023 14:19:21 +0300</pubDate><guid>https://software-design.dev/backend/authentication/basic-auth/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;HTTP Basic Auth&lt;/strong&gt; is a simple authentication method using username/password pair credentials for HTTP requests.&lt;/p&gt;
&lt;p&gt;These credentials are encoded in &lt;strong&gt;Base64&lt;/strong&gt; format and transmitted through the &lt;code&gt;Authorization&lt;/code&gt; header. The header value starts with the &lt;code&gt;Basic&lt;/code&gt; keyword. Here is an example header:&lt;/p&gt;</description></item><item><title>API Keys</title><link>https://software-design.dev/backend/authentication/api-keys/</link><pubDate>Thu, 09 Feb 2023 14:42:54 +0300</pubDate><guid>https://software-design.dev/backend/authentication/api-keys/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;API Key&lt;/strong&gt; is a unique identification key assigned to an API client. It&amp;rsquo;s typically an alphanumeric string included in every API call that a server can receive and validate.&lt;/p&gt;</description></item><item><title>JWT Token</title><link>https://software-design.dev/backend/authentication/jwt/</link><pubDate>Tue, 21 Feb 2023 13:26:53 +0300</pubDate><guid>https://software-design.dev/backend/authentication/jwt/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;JWT (JSON Web Token)&lt;/strong&gt; is a standard 

&lt;a class="link link--text" href="https://www.rfc-editor.org/rfc/rfc7519" rel="external"&gt;RFC 7519&lt;/a&gt; that defines a secure way for information transmission in a JSON object form. This piece of data can be digitally signed using a &lt;em&gt;secret keyword&lt;/em&gt; (symmetrical &lt;strong&gt;HMAC&lt;/strong&gt;) or &lt;em&gt;public/private keys&lt;/em&gt; (asymmetrical &lt;strong&gt;RSA&lt;/strong&gt; or &lt;strong&gt;ECDSA&lt;/strong&gt;).&lt;/p&gt;</description></item></channel></rss>