<?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: POST Access Token 200 Response missing scopes in Webex for Developers</title>
    <link>https://community.cisco.com/t5/webex-for-developers/post-access-token-200-response-missing-scopes/m-p/4683108#M3292</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;The admin needs to be a Webex Contact Center Administrator - it looks like the user does not have a contact center license.&lt;/P&gt;
&lt;P&gt;Can you please confirm this?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;FAQ:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://developer.webex-cx.com/faq/#gettingStarted" target="_blank"&gt;https://developer.webex-cx.com/faq/#gettingStarted&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;
&lt;P&gt;Arunabh.&lt;/P&gt;</description>
    <pubDate>Wed, 07 Sep 2022 22:47:02 GMT</pubDate>
    <dc:creator>Arunabh Bhattacharjee</dc:creator>
    <dc:date>2022-09-07T22:47:02Z</dc:date>
    <item>
      <title>POST Access Token 200 Response missing scopes</title>
      <link>https://community.cisco.com/t5/webex-for-developers/post-access-token-200-response-missing-scopes/m-p/4682925#M3290</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We are running into an issue where after authenticating successfully, the access tokens we receive from the POST response to&amp;nbsp;&lt;A href="https://webexapis.com/v1/access_token" target="_blank"&gt;https://webexapis.com/v1/access_token&lt;/A&gt;&amp;nbsp;is missing scopes. The scopes we are asking are spark:people_read, cjp:config, and cjp:config_read. The only scope that is getting returned in the 200 response is spark:people_read. The Integration App setting on&amp;nbsp;&lt;A href="https://developer.webex-cx.com/my-apps/" target="_blank"&gt;https://developer.webex-cx.com/my-apps/&lt;/A&gt;&amp;nbsp;for the App in question has the 3 above Scopes selected. We already manually granted access.&lt;/P&gt;&lt;P&gt;We verified that the initial GET request to &lt;A href="https://webexapis.com/v1/authorize?" target="_blank"&gt;https://webexapis.com/v1/authorize?&lt;/A&gt;&amp;nbsp;has the scopes in the URL: "scope=spark%3Apeople_read%20cjp%3Aconfig%20cjp%3Aconfig_read".&lt;/P&gt;&lt;P&gt;To be clear, the POST to&amp;nbsp;&lt;A href="https://webexapis.com/v1/access_token" target="_blank"&gt;https://webexapis.com/v1/access_token&lt;/A&gt;&amp;nbsp;is coming back with a 200 response code. But without the cjp scopes above, we cannot make any of the API calls necessary for our client's needs.&lt;/P&gt;&lt;P&gt;Any assistance in resolving this issue would be appreciated. We are on a tight deadline and currently dead in the water.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Sep 2022 15:44:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/post-access-token-200-response-missing-scopes/m-p/4682925#M3290</guid>
      <dc:creator>BlakeR</dc:creator>
      <dc:date>2022-09-07T15:44:31Z</dc:date>
    </item>
    <item>
      <title>Re: POST Access Token 200 Response missing scopes</title>
      <link>https://community.cisco.com/t5/webex-for-developers/post-access-token-200-response-missing-scopes/m-p/4682935#M3291</link>
      <description>&lt;P&gt;Two other important details:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;The account we are using is a Full Admin WebEx account.&lt;/LI&gt;&lt;LI&gt;The "Try Out" samples are coming back with 403&amp;nbsp;"Access denied - Client is forbidden access to the resource" errors while logged into the Full Admin WebEx Account. Screenshot from&amp;nbsp;&lt;A href="https://developer.webex-cx.com/documentation/team/v1/list-teams" target="_blank"&gt;https://developer.webex-cx.com/documentation/team/v1/list-teams&lt;/A&gt;&amp;nbsp;&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Wed, 07 Sep 2022 15:53:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/post-access-token-200-response-missing-scopes/m-p/4682935#M3291</guid>
      <dc:creator>BlakeR</dc:creator>
      <dc:date>2022-09-07T15:53:10Z</dc:date>
    </item>
    <item>
      <title>Re: POST Access Token 200 Response missing scopes</title>
      <link>https://community.cisco.com/t5/webex-for-developers/post-access-token-200-response-missing-scopes/m-p/4683108#M3292</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;The admin needs to be a Webex Contact Center Administrator - it looks like the user does not have a contact center license.&lt;/P&gt;
&lt;P&gt;Can you please confirm this?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;FAQ:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://developer.webex-cx.com/faq/#gettingStarted" target="_blank"&gt;https://developer.webex-cx.com/faq/#gettingStarted&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;
&lt;P&gt;Arunabh.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Sep 2022 22:47:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/post-access-token-200-response-missing-scopes/m-p/4683108#M3292</guid>
      <dc:creator>Arunabh Bhattacharjee</dc:creator>
      <dc:date>2022-09-07T22:47:02Z</dc:date>
    </item>
    <item>
      <title>Re: POST Access Token 200 Response missing scopes</title>
      <link>https://community.cisco.com/t5/webex-for-developers/post-access-token-200-response-missing-scopes/m-p/4683736#M3293</link>
      <description>&lt;P&gt;That was indeed the issue. We had our customer double check and add the licenses required and we are now getting the Scopes we expect and the "Try Out" samples are working as well.&lt;/P&gt;&lt;P&gt;Thank you.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 08 Sep 2022 15:23:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/post-access-token-200-response-missing-scopes/m-p/4683736#M3293</guid>
      <dc:creator>BlakeR</dc:creator>
      <dc:date>2022-09-08T15:23:43Z</dc:date>
    </item>
  </channel>
</rss>

