<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Security on sugar, spice, &amp;terminal? nice</title>
    <link>https://terminal.space/tag/security/</link>
    <description>Recent content in Security on sugar, spice, &amp;terminal? nice</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 27 Aug 2023 02:06:05 +0000</lastBuildDate>
    <atom:link href="https://terminal.space/tag/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Easy, secure API keys</title>
      <link>https://terminal.space/tech/easy-secure-api-keys/</link>
      <pubDate>Sun, 27 Aug 2023 02:06:05 +0000</pubDate>
      <guid>https://terminal.space/tech/easy-secure-api-keys/</guid>
      <description>&lt;figure&gt;&lt;img src=&#34;https://terminal.space/tech/easy-secure-api-keys/images/christian-lendl-ZyttGSu-o2E-unsplash.jpg&#34;&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;p&gt;I needed to add API key authentication to our work environment. I needed:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;To develop the functionality quickly&lt;/li&gt;&#xA;&lt;li&gt;Be confident in the security of the system&#xA;&lt;ul&gt;&#xA;&lt;li&gt;API keys should only be visible once when created&lt;/li&gt;&#xA;&lt;li&gt;Should be hard to impersonate other users/be resilient to DB leak&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Have an upgrade path for when we want to change/improve things&lt;/li&gt;&#xA;&lt;li&gt;Performance isn&amp;rsquo;t a huge consideration&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;I was able to use JWT tokens in a slightly clever way to make this happen. The best part is, there are no stored secrets on the server side. All of the server data could be revealed publicly without compromising the security. Here&amp;rsquo;s how:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
