<?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 No Client Secret Needed? in Spotify for Developers</title>
    <link>https://community.spotify.com/t5/Spotify-for-Developers/No-Client-Secret-Needed/m-p/5635173#M10713</link>
    <description>&lt;P&gt;I am currently working on a web app using the spotify api. I am accessing the api via&amp;nbsp;spotify-web-api-ts-sdk which can be found here &lt;A href="https://github.com/spotify/spotify-web-api-ts-sdk/" target="_blank" rel="noopener"&gt;https://github.com/spotify/spotify-web-api-ts-sdk/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;When creating an sdk object, we can use the function&amp;nbsp;&lt;SPAN&gt;withUserAuthorization providing a cliendId, redirectUri scopes and optional config. I have noticed that this does NOT actually ask for a client secret. Which, knowing that the client id can, and IS, public as can be seen here:&amp;nbsp;&lt;A href="https://protect-us.mimecast.com/s/dJ7fC82D4vF6O34VJTnxmbW?domain=community.spotify.com" target="_blank" rel="noopener"&gt;https://community.spotify.com/t5/Spotify-for-Developers/Do-i-have-to-keep-the-Client-ID-secret/td-p/5258016&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;My question is, what keeps non authorized people from connecting to my api app?&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Sep 2023 19:11:23 GMT</pubDate>
    <dc:creator>ClydeFrog04</dc:creator>
    <dc:date>2023-09-12T19:11:23Z</dc:date>
    <item>
      <title>No Client Secret Needed?</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/No-Client-Secret-Needed/m-p/5635173#M10713</link>
      <description>&lt;P&gt;I am currently working on a web app using the spotify api. I am accessing the api via&amp;nbsp;spotify-web-api-ts-sdk which can be found here &lt;A href="https://github.com/spotify/spotify-web-api-ts-sdk/" target="_blank" rel="noopener"&gt;https://github.com/spotify/spotify-web-api-ts-sdk/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;When creating an sdk object, we can use the function&amp;nbsp;&lt;SPAN&gt;withUserAuthorization providing a cliendId, redirectUri scopes and optional config. I have noticed that this does NOT actually ask for a client secret. Which, knowing that the client id can, and IS, public as can be seen here:&amp;nbsp;&lt;A href="https://protect-us.mimecast.com/s/dJ7fC82D4vF6O34VJTnxmbW?domain=community.spotify.com" target="_blank" rel="noopener"&gt;https://community.spotify.com/t5/Spotify-for-Developers/Do-i-have-to-keep-the-Client-ID-secret/td-p/5258016&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;My question is, what keeps non authorized people from connecting to my api app?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Sep 2023 19:11:23 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/No-Client-Secret-Needed/m-p/5635173#M10713</guid>
      <dc:creator>ClydeFrog04</dc:creator>
      <dc:date>2023-09-12T19:11:23Z</dc:date>
    </item>
  </channel>
</rss>

