<?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: Question about accessToken for CI-using WebEx site in Cloud Collaboration</title>
    <link>https://community.cisco.com/t5/cloud-collaboration/question-about-accesstoken-for-ci-using-webex-site/m-p/3501690#M822</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; PDA is not specific to CI sites, it can be used on both CI and traditional WebEx sites, whether SSO is configured or not. I am not able to easily paste our reference material here, as format is altered and links stripped, however you may email &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:webex-meetings-api-dev@cisco.com"&gt;webex-meetings-api-dev@cisco.com&lt;/A&gt;&lt;SPAN&gt; to request the guide in Doc format. The basic config is just a matter of submitting a provisioning request to create the new SSO config, including the SSL certificate, IdP ID, SP ID, NameID Format, AuthContextClassRef, a unique name to identify the configuration, and a list of WebEx sites to link to this SSO configuration. This is mostly the same as our standard site SSO, but in a global sense so must be managed by provisioning instead of in Site Admin or Spark Control Hub. The end result is an application specific SSO config for authenticating API requests.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 16 Mar 2018 00:04:50 GMT</pubDate>
    <dc:creator>nmorrow</dc:creator>
    <dc:date>2018-03-16T00:04:50Z</dc:date>
    <item>
      <title>Question about accessToken for CI-using WebEx site</title>
      <link>https://community.cisco.com/t5/cloud-collaboration/question-about-accesstoken-for-ci-using-webex-site/m-p/3501687#M819</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am looking for some documentation as to how to retrieve an accessToken for a Common Identity site as described in the AuthenticateUser section of the XML API reference: &lt;A href="https://developer.cisco.com/site/webex-developer/develop-test/xml-api/xml-api-reference/" title="https://developer.cisco.com/site/webex-developer/develop-test/xml-api/xml-api-reference/"&gt;https://developer.cisco.com/site/webex-developer/develop-test/xml-api/xml-api-reference/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Separately, but related, I am curious as to whether a "Partner Administrator," who is not a member of a Customer's Spark Org, can use the XML API with WebEx sites that use CI and are attached to a Customer's Spark Org.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NPM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Mar 2018 15:34:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-collaboration/question-about-accesstoken-for-ci-using-webex-site/m-p/3501687#M819</guid>
      <dc:creator>nick.mueller</dc:creator>
      <dc:date>2018-03-15T15:34:49Z</dc:date>
    </item>
    <item>
      <title>Re: Question about accessToken for CI-using WebEx site</title>
      <link>https://community.cisco.com/t5/cloud-collaboration/question-about-accesstoken-for-ci-using-webex-site/m-p/3501688#M820</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;CI site authentication is detailed below. Partner Delegated Authentication (a global application specificl SSO configuration for multiple WebEx sites) will also work with CI sites. I am not aware of any backdoor admin access for CI sites.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __default_attr="plain" __jive_macro_name="code" class="jive_text_macro jive_macro_code _jivemacro_uid_15211468644241407" jivemacro_uid="_15211468644241407" modifiedtitle="true"&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Meeting Service API authentication for Cisco Spark with WebEx.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Log in to developer.ciscospark.com.&lt;/P&gt;
&lt;P&gt;Click My Apps&lt;/P&gt;
&lt;P&gt;Create a new app with spark:all scope selected (Existing app is ok)&lt;/P&gt;
&lt;UL style="list-style-type: disc;"&gt;
&lt;LI&gt;- Set Redirect URL to valid URL that you control, this will be used to provide authorization code via GET variable&lt;/LI&gt;
&lt;LI&gt;- Save generated Client ID and Client Secret&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Issue HTTP GET request to &lt;A href="https://api.ciscospark.com/v1/authorize"&gt;https://api.ciscospark.com/v1/authorize&lt;/A&gt;&lt;/P&gt;
&lt;UL style="list-style-type: disc;"&gt;
&lt;LI&gt;- response_type=code&lt;/LI&gt;
&lt;LI&gt;- client_id=&amp;lt;your Client ID&amp;gt;&lt;/LI&gt;
&lt;LI&gt;- redirect_uri = &amp;lt;your redirect URL from registered application, it must match&amp;gt;&lt;/LI&gt;
&lt;LI&gt;- scope=spark:all&lt;/LI&gt;
&lt;LI&gt;- state=&amp;lt;custom state value of your choosing for identification or tracking, optional&amp;gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Spark page will prompt user to authorize application, if approved, user will be redirected to redirect uri with a code and the previously set state value as GET variables, save the code&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Issue HTTP POST request to &lt;A href="https://api.ciscospark.com/v1/access_token"&gt;https://api.ciscospark.com/v1/access_token&lt;/A&gt;&lt;/P&gt;
&lt;UL style="list-style-type: disc;"&gt;
&lt;LI&gt;- grant_type=authorization_code&lt;/LI&gt;
&lt;LI&gt;- client_id=&amp;lt;your Client ID&amp;gt;&lt;/LI&gt;
&lt;LI&gt;- client_secret=&amp;lt;your Client Secret&amp;gt;&lt;/LI&gt;
&lt;LI&gt;- code=&amp;lt;the previously returned code&amp;gt;&lt;/LI&gt;
&lt;LI&gt;- redirect_uri=&amp;lt;your redirect URL from registered application, it must match&amp;gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;JSON data will be returned in the response body, save the access_token value.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Issue XML API AuthenticateUser request&lt;/P&gt;
&lt;UL style="list-style-type: disc;"&gt;
&lt;LI&gt;- securityContext should contain webExID and siteName&lt;/LI&gt;
&lt;LI&gt;- webExID should match the email address for the spark user (webExID is not actually used for authenticateUser and is ignored but schema requires a value, any non-null value will work, email address for authenticated user is a best practice)&lt;/LI&gt;
&lt;LI&gt;- siteName is the subdomain of the WebEx site&lt;/LI&gt;
&lt;LI&gt;- bodyContent will include one child element named accessToken, which should be set to the previously returned access_token&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;returned sessionTicket will be used in the security context for subsequent XML API requests.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;/PRE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Mar 2018 20:48:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-collaboration/question-about-accesstoken-for-ci-using-webex-site/m-p/3501688#M820</guid>
      <dc:creator>nmorrow</dc:creator>
      <dc:date>2018-03-15T20:48:28Z</dc:date>
    </item>
    <item>
      <title>Re: Question about accessToken for CI-using WebEx site</title>
      <link>https://community.cisco.com/t5/cloud-collaboration/question-about-accesstoken-for-ci-using-webex-site/m-p/3501689#M821</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WHere can I find documentation on the setup of partner delegated Authentication for CI WebEx sites?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;npm&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Mar 2018 23:54:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-collaboration/question-about-accesstoken-for-ci-using-webex-site/m-p/3501689#M821</guid>
      <dc:creator>nick.mueller</dc:creator>
      <dc:date>2018-03-15T23:54:33Z</dc:date>
    </item>
    <item>
      <title>Re: Question about accessToken for CI-using WebEx site</title>
      <link>https://community.cisco.com/t5/cloud-collaboration/question-about-accesstoken-for-ci-using-webex-site/m-p/3501690#M822</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; PDA is not specific to CI sites, it can be used on both CI and traditional WebEx sites, whether SSO is configured or not. I am not able to easily paste our reference material here, as format is altered and links stripped, however you may email &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:webex-meetings-api-dev@cisco.com"&gt;webex-meetings-api-dev@cisco.com&lt;/A&gt;&lt;SPAN&gt; to request the guide in Doc format. The basic config is just a matter of submitting a provisioning request to create the new SSO config, including the SSL certificate, IdP ID, SP ID, NameID Format, AuthContextClassRef, a unique name to identify the configuration, and a list of WebEx sites to link to this SSO configuration. This is mostly the same as our standard site SSO, but in a global sense so must be managed by provisioning instead of in Site Admin or Spark Control Hub. The end result is an application specific SSO config for authenticating API requests.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Mar 2018 00:04:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-collaboration/question-about-accesstoken-for-ci-using-webex-site/m-p/3501690#M822</guid>
      <dc:creator>nmorrow</dc:creator>
      <dc:date>2018-03-16T00:04:50Z</dc:date>
    </item>
    <item>
      <title>Re: Question about accessToken for CI-using WebEx site</title>
      <link>https://community.cisco.com/t5/cloud-collaboration/question-about-accesstoken-for-ci-using-webex-site/m-p/3501691#M823</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;One more question Nathan/Cisco: are the methods described above also valid for NBR API?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Mar 2018 18:26:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-collaboration/question-about-accesstoken-for-ci-using-webex-site/m-p/3501691#M823</guid>
      <dc:creator>nick.mueller</dc:creator>
      <dc:date>2018-03-20T18:26:55Z</dc:date>
    </item>
    <item>
      <title>Re: Question about accessToken for CI-using WebEx site</title>
      <link>https://community.cisco.com/t5/cloud-collaboration/question-about-accesstoken-for-ci-using-webex-site/m-p/3501692#M824</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; NBR API is strictly limited to site admin username and password at this time. This will not work with SSO or CI authentication method until this behavior is addressed. CI sites that have not yet configured SSO can use NBR API in the meantime, with their login email address and password.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Mar 2018 18:48:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-collaboration/question-about-accesstoken-for-ci-using-webex-site/m-p/3501692#M824</guid>
      <dc:creator>nmorrow</dc:creator>
      <dc:date>2018-03-20T18:48:39Z</dc:date>
    </item>
  </channel>
</rss>

