<?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: How to protect public APIs (no credentials) from being exploited? in cybersource APIs</title>
    <link>https://community.developer.cybersource.com/t5/cybersource-APIs/How-to-protect-public-APIs-no-credentials-from-being-exploited/m-p/82167#M24</link>
    <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.developer.cybersource.com/t5/user/viewprofilepage/user-id/60217"&gt;@Harold123&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;It's more of a general question, but What is the recommended way to protect APIs used in SIGN UP processes? Let's say there is these public APIs (No user credential required, only API KEYs);&lt;/P&gt;
&lt;P&gt;find_person(Data about the person trying to sign up), returns if a person already exists or not (no user credentials required AND no sensitive information returned).&lt;BR /&gt;create_person(Data about the person trying to sign up), creates this person into the system (no user credentials required)&lt;BR /&gt;Can we have "anonymous" users that have a short-lived JWT token? For example, how can the SPA Web application or Mobile application securely obtain a "per-session" anonymous user? Are Captchas actually helpful in this scenario?&lt;/P&gt;
&lt;P&gt;We are already considering:&lt;/P&gt;
&lt;P&gt;API KEY for every application (not per session)&lt;BR /&gt;Rate limiting&lt;BR /&gt;DDoS services to protect the APIs&lt;BR /&gt;Any help would be much appreciated.&lt;/P&gt;
&lt;P&gt;Check this for reference&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Any suggestions ????&lt;/P&gt;</description>
    <pubDate>Thu, 14 Apr 2022 14:28:15 GMT</pubDate>
    <dc:creator>Harold123</dc:creator>
    <dc:date>2022-04-14T14:28:15Z</dc:date>
    <item>
      <title>How to protect public APIs (no credentials) from being exploited?</title>
      <link>https://community.developer.cybersource.com/t5/cybersource-APIs/How-to-protect-public-APIs-no-credentials-from-being-exploited/m-p/82159#M22</link>
      <description>&lt;P&gt;It's more of a general question, but What is the recommended way to protect APIs used in SIGN UP processes? Let's say there is these public APIs (No user credential required, only API KEYs);&lt;/P&gt;
&lt;P&gt;find_person(Data about the person trying to sign up), returns if a person already exists or not (no user credentials required AND no sensitive information returned).&lt;BR /&gt;create_person(Data about the person trying to sign up), creates this person into the system (no user credentials required)&lt;BR /&gt;Can we have "anonymous" users that have a short-lived JWT token? For example, how can the SPA Web application or Mobile application securely obtain a "per-session" anonymous user? Are Captchas actually helpful in this scenario?&lt;/P&gt;
&lt;P&gt;We are already considering:&lt;/P&gt;
&lt;P&gt;API KEY for every application (not per session)&lt;BR /&gt;Rate limiting&lt;BR /&gt;DDoS services to protect the APIs&lt;BR /&gt;Any help would be much appreciated.&lt;/P&gt;
&lt;P&gt;Check this for reference&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 13 Apr 2022 15:18:37 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/cybersource-APIs/How-to-protect-public-APIs-no-credentials-from-being-exploited/m-p/82159#M22</guid>
      <dc:creator>Harold123</dc:creator>
      <dc:date>2022-04-13T15:18:37Z</dc:date>
    </item>
    <item>
      <title>Re: How to protect public APIs (no credentials) from being exploited?</title>
      <link>https://community.developer.cybersource.com/t5/cybersource-APIs/How-to-protect-public-APIs-no-credentials-from-being-exploited/m-p/82167#M24</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.developer.cybersource.com/t5/user/viewprofilepage/user-id/60217"&gt;@Harold123&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;It's more of a general question, but What is the recommended way to protect APIs used in SIGN UP processes? Let's say there is these public APIs (No user credential required, only API KEYs);&lt;/P&gt;
&lt;P&gt;find_person(Data about the person trying to sign up), returns if a person already exists or not (no user credentials required AND no sensitive information returned).&lt;BR /&gt;create_person(Data about the person trying to sign up), creates this person into the system (no user credentials required)&lt;BR /&gt;Can we have "anonymous" users that have a short-lived JWT token? For example, how can the SPA Web application or Mobile application securely obtain a "per-session" anonymous user? Are Captchas actually helpful in this scenario?&lt;/P&gt;
&lt;P&gt;We are already considering:&lt;/P&gt;
&lt;P&gt;API KEY for every application (not per session)&lt;BR /&gt;Rate limiting&lt;BR /&gt;DDoS services to protect the APIs&lt;BR /&gt;Any help would be much appreciated.&lt;/P&gt;
&lt;P&gt;Check this for reference&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Any suggestions ????&lt;/P&gt;</description>
      <pubDate>Thu, 14 Apr 2022 14:28:15 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/cybersource-APIs/How-to-protect-public-APIs-no-credentials-from-being-exploited/m-p/82167#M24</guid>
      <dc:creator>Harold123</dc:creator>
      <dc:date>2022-04-14T14:28:15Z</dc:date>
    </item>
  </channel>
</rss>

