<?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: Webex Control Hub SCIM 2 API - Cisco extension data missing in Webex for Developers</title>
    <link>https://community.cisco.com/t5/webex-for-developers/webex-control-hub-scim-2-api-cisco-extension-data-missing/m-p/5213100#M3886</link>
    <description>&lt;P&gt;Thank you. &amp;nbsp;I'll send them an email.&lt;/P&gt;</description>
    <pubDate>Tue, 22 Oct 2024 18:16:22 GMT</pubDate>
    <dc:creator>Martin Sloan</dc:creator>
    <dc:date>2024-10-22T18:16:22Z</dc:date>
    <item>
      <title>Webex Control Hub SCIM 2 API - Cisco extension data missing</title>
      <link>https://community.cisco.com/t5/webex-for-developers/webex-control-hub-scim-2-api-cisco-extension-data-missing/m-p/5210386#M3878</link>
      <description>&lt;P&gt;As suggested in the developer API docs, we're moving from the /v1/people API to the SCIM API.&amp;nbsp; When listing users with the new SCIM API, I'm not seeing properties in the&amp;nbsp;&lt;SPAN&gt;urn:scim:schemas:extension:cisco:webexidentity:2.0:User object for things like&amp;nbsp;accountStatus and sipAddresses.&amp;nbsp; What I get back for that schema is only meta.organizationId and userNameType&lt;/SPAN&gt;&lt;/P&gt;&lt;LI-CODE lang="javascript"&gt;......
"urn:scim:schemas:extension:cisco:webexidentity:2.0:User": {
        "meta": {
          "organizationId": &amp;lt;org_id&amp;gt;
        },
        "userNameType": "email"
      },
......&lt;/LI-CODE&gt;&lt;P&gt;The documentation says that the&amp;nbsp;&lt;SPAN&gt;accountStatus and sipAddresses properties should be included.&amp;nbsp; Anyone know why those properties are missing in the response?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Oct 2024 14:37:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/webex-control-hub-scim-2-api-cisco-extension-data-missing/m-p/5210386#M3878</guid>
      <dc:creator>Martin Sloan</dc:creator>
      <dc:date>2024-10-17T14:37:26Z</dc:date>
    </item>
    <item>
      <title>Re: Webex Control Hub SCIM 2 API - Cisco extension data missing</title>
      <link>https://community.cisco.com/t5/webex-for-developers/webex-control-hub-scim-2-api-cisco-extension-data-missing/m-p/5211512#M3882</link>
      <description>&lt;P&gt;Engineering have an open ticket for the documentation discrepancies with SCIM API around&amp;nbsp;&lt;SPAN&gt;&lt;EM&gt;accountStatus&lt;/EM&gt; and &lt;EM&gt;sipAddresses&lt;/EM&gt; properties which the team has been working on. However, you could share the API request and response details by sending&amp;nbsp;&lt;/SPAN&gt;an email to &lt;A href="mailto:devsupport@webex.com" target="_blank"&gt;devsupport@webex.com&lt;/A&gt;, that way you'll be informed with the progress or further updates regarding the issue.&lt;/P&gt;</description>
      <pubDate>Sat, 19 Oct 2024 15:37:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/webex-control-hub-scim-2-api-cisco-extension-data-missing/m-p/5211512#M3882</guid>
      <dc:creator>Rudrakshi</dc:creator>
      <dc:date>2024-10-19T15:37:43Z</dc:date>
    </item>
    <item>
      <title>Re: Webex Control Hub SCIM 2 API - Cisco extension data missing</title>
      <link>https://community.cisco.com/t5/webex-for-developers/webex-control-hub-scim-2-api-cisco-extension-data-missing/m-p/5213100#M3886</link>
      <description>&lt;P&gt;Thank you. &amp;nbsp;I'll send them an email.&lt;/P&gt;</description>
      <pubDate>Tue, 22 Oct 2024 18:16:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/webex-control-hub-scim-2-api-cisco-extension-data-missing/m-p/5213100#M3886</guid>
      <dc:creator>Martin Sloan</dc:creator>
      <dc:date>2024-10-22T18:16:22Z</dc:date>
    </item>
  </channel>
</rss>

