<?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 Re: Spotify PKCE Auth Invalid Client Secret in Spotify for Developers</title>
    <link>https://community.spotify.com/t5/Spotify-for-Developers/Spotify-PKCE-Auth-Invalid-Client-Secret/m-p/5098976#M1790</link>
    <description>&lt;P&gt;Chimildic&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Did you ever get this working?&amp;nbsp; I struggled with this for a bit until I found I had an odd typo in my code.&amp;nbsp; The weird thing was that the typo resulted in a URL that was valid for a regular auth flow, but not a PKCE flow.&amp;nbsp; So it would still return an authorization code that I could redeem for a regular auth flow token if I provided my client ID and secret.&amp;nbsp; Triple check your URL generator for the PKCE flow and make sure you don't have any typos there that could be causing this same issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Will&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 26 Dec 2020 17:04:28 GMT</pubDate>
    <dc:creator>ktuli44</dc:creator>
    <dc:date>2020-12-26T17:04:28Z</dc:date>
    <item>
      <title>Spotify PKCE Auth Invalid Client Secret</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Spotify-PKCE-Auth-Invalid-Client-Secret/m-p/5081925#M1640</link>
      <description>&lt;P&gt;Check &lt;A href="https://stackoverflow.com/questions/65069734/spotify-pkce-error-invalid-client-secret" target="_self"&gt;StackOverflow&lt;/A&gt;&amp;nbsp;for full code&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I need to complete&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://spotify.dev/documentation/general/guides/authorization-guide/#authorization-code-flow-with-proof-key-for-code-exchange-pkce" target="_blank" rel="nofollow noopener noreferrer"&gt;Authorization Code Flow with Proof Key for Code Exchange&lt;/A&gt;&lt;SPAN&gt;. In step 4, I get an error&amp;nbsp;&lt;/SPAN&gt;400 - bad request&lt;SPAN&gt;. I can't understand what problem is.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;{"error":"invalid_request","error_description":"Invalid client secret"}. What? I used PKCE, why you need client secret?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Dec 2020 09:32:26 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Spotify-PKCE-Auth-Invalid-Client-Secret/m-p/5081925#M1640</guid>
      <dc:creator>Chimildic</dc:creator>
      <dc:date>2020-12-01T09:32:26Z</dc:date>
    </item>
    <item>
      <title>Re: Spotify PKCE Auth Invalid Client Secret</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Spotify-PKCE-Auth-Invalid-Client-Secret/m-p/5098976#M1790</link>
      <description>&lt;P&gt;Chimildic&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Did you ever get this working?&amp;nbsp; I struggled with this for a bit until I found I had an odd typo in my code.&amp;nbsp; The weird thing was that the typo resulted in a URL that was valid for a regular auth flow, but not a PKCE flow.&amp;nbsp; So it would still return an authorization code that I could redeem for a regular auth flow token if I provided my client ID and secret.&amp;nbsp; Triple check your URL generator for the PKCE flow and make sure you don't have any typos there that could be causing this same issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Will&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 26 Dec 2020 17:04:28 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Spotify-PKCE-Auth-Invalid-Client-Secret/m-p/5098976#M1790</guid>
      <dc:creator>ktuli44</dc:creator>
      <dc:date>2020-12-26T17:04:28Z</dc:date>
    </item>
  </channel>
</rss>

