<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Identity-Security on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/identity-security/</link>
    <description>Recent content in Identity-Security on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 15 Nov 2026 09:55:34 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/identity-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fixing Session Fixation in a Remember Me Cookie</title>
      <link>https://linuxeries.org/post/2026-11-15-why-the-remember-me-cookie-in-our-ecommerce-a/</link>
      <pubDate>Sun, 15 Nov 2026 09:55:34 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-11-15-why-the-remember-me-cookie-in-our-ecommerce-a/</guid>
      <description>&lt;h3 id=&#34;the-scenario&#34;&gt;The scenario&lt;/h3&gt;&#xA;&lt;p&gt;Our e‑commerce API was built on a stateless REST layer that delegated authentication to a central identity service. The API accepted a short‑lived bearer token (JWT) and, for convenience, exposed a “Remember Me” feature that let users stay logged in across browser restarts. The implementation was simple: the client stored a cookie named &lt;code&gt;REMEMBER_ME&lt;/code&gt; that contained a signed, encrypted token. When the browser sent the cookie back, the API would issue a new JWT and refresh the cookie.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
