<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic PKCE refresh token storage in Spotify for Developers</title>
    <link>https://community.spotify.com/t5/Spotify-for-Developers/PKCE-refresh-token-storage/m-p/5824678#M12315</link>
    <description>&lt;P&gt;I'm currently building a SPA that communicates with the Spofity API using the Authorization Code with PKCE Flow.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;How do I safely store the refresh token so the user won't need to grant authorization everytime it uses the application? My worriy is that if I use the browser's local storage, a malicious third party might manage to get access to the refresh token, and be able to generate an access token form it.&lt;/P&gt;</description>
    <pubDate>Fri, 19 Jan 2024 03:05:36 GMT</pubDate>
    <dc:creator>Vitorgus</dc:creator>
    <dc:date>2024-01-19T03:05:36Z</dc:date>
    <item>
      <title>PKCE refresh token storage</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/PKCE-refresh-token-storage/m-p/5824678#M12315</link>
      <description>&lt;P&gt;I'm currently building a SPA that communicates with the Spofity API using the Authorization Code with PKCE Flow.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;How do I safely store the refresh token so the user won't need to grant authorization everytime it uses the application? My worriy is that if I use the browser's local storage, a malicious third party might manage to get access to the refresh token, and be able to generate an access token form it.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 03:05:36 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/PKCE-refresh-token-storage/m-p/5824678#M12315</guid>
      <dc:creator>Vitorgus</dc:creator>
      <dc:date>2024-01-19T03:05:36Z</dc:date>
    </item>
  </channel>
</rss>

