<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Jwt on BradCypert.com</title>
    <link>https://www.bradcypert.com/tags/jwt/</link>
    <description>Recent content in Jwt on BradCypert.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 27 Dec 2022 22:25:45 -0500</lastBuildDate>
    <atom:link href="https://www.bradcypert.com/tags/jwt/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using JSON Web Tokens with Clojure</title>
      <link>https://www.bradcypert.com/using-json-web-tokens-with-clojure/</link>
      <pubDate>Thu, 23 Jun 2016 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/using-json-web-tokens-with-clojure/</guid>
      <description>&lt;p&gt;Authentication is easy. Good authentication is difficult. We’re at a point in the world where our users expect to be able to sign up for your service or app, and receive a more personalized experience. If you can’t validate who the user is, you can’t achieve this.&lt;/p&gt;&#xA;&lt;p&gt;In the past, people have leveraged sessions, cookies, sending the user’s email and password on each request (&lt;strong&gt;please don’t ever do this&lt;/strong&gt;), and many other techniques to validate that a user is who they say they are. A lot of these techniques worked relatively well for the time, but they all have their flaws – Cookies expire and are tied the browser, Sessions don’t scale well, sending email/password on every request violates your user’s trust in you to keep their information secure.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
