<?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: Why location are getting listed in Groups API? in Webex for Developers</title>
    <link>https://community.cisco.com/t5/webex-for-developers/why-location-are-getting-listed-in-groups-api/m-p/5232366#M3984</link>
    <description>&lt;P&gt;Location is represented as a type of group in Common Identity (backend identity management service), whose usage is "location". This is how it's designed and it follows the &lt;A href="https://simplecloud.info/" target="_self"&gt;SCIM Specification&lt;/A&gt;. Basically locations are considered to be a type of&amp;nbsp;&lt;SPAN&gt;user group, in that a location usually includes a group of users, so it is returned by this API. Note that our SCIM 2.0 APIs are different to most of our other APIs in that they are specifically built to conform to the SCIM Specification standard (which is external to Cisco) and therefore it's not necessarily going to be tied to functionalities that our other APIs provide.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 04 Dec 2024 10:24:41 GMT</pubDate>
    <dc:creator>Raffaele Lagana</dc:creator>
    <dc:date>2024-12-04T10:24:41Z</dc:date>
    <item>
      <title>Why location are getting listed in Groups API?</title>
      <link>https://community.cisco.com/t5/webex-for-developers/why-location-are-getting-listed-in-groups-api/m-p/5230556#M3972</link>
      <description>&lt;P&gt;I have created a groups ans location on Webex control hub. When I use&amp;nbsp;&lt;A href="https://developer.webex.com/docs/api/v1/scim2-group/search-groups" target="_blank"&gt;https://developer.webex.com/docs/api/v1/scim2-group/search-groups&lt;/A&gt;&amp;nbsp;API then all groups and location are getting fetched in response.&lt;BR /&gt;My understanding is,&amp;nbsp;&lt;A href="https://developer.webex.com/docs/api/v1/scim2-group/search-groups" target="_blank"&gt;https://developer.webex.com/docs/api/v1/scim2-group/search-groups&lt;/A&gt;&amp;nbsp;API should only fetch groups not location in response.&lt;BR /&gt;Please correct if something is wrong here.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Prashant&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 29 Nov 2024 12:54:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/why-location-are-getting-listed-in-groups-api/m-p/5230556#M3972</guid>
      <dc:creator>prashant-chinchkar</dc:creator>
      <dc:date>2024-11-29T12:54:16Z</dc:date>
    </item>
    <item>
      <title>Re: Why location are getting listed in Groups API?</title>
      <link>https://community.cisco.com/t5/webex-for-developers/why-location-are-getting-listed-in-groups-api/m-p/5231966#M3978</link>
      <description>&lt;P&gt;Yes, this API returns both locations and groups (known as "policy" within this API). There is a&amp;nbsp;&lt;EM&gt;usage&lt;/EM&gt; field that tells whether it's a location or a group/policy. It also returns the synchronized groups, also returned with "usage=policy".&lt;/P&gt;</description>
      <pubDate>Tue, 03 Dec 2024 15:01:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/why-location-are-getting-listed-in-groups-api/m-p/5231966#M3978</guid>
      <dc:creator>Raffaele Lagana</dc:creator>
      <dc:date>2024-12-03T15:01:32Z</dc:date>
    </item>
    <item>
      <title>Re: Why location are getting listed in Groups API?</title>
      <link>https://community.cisco.com/t5/webex-for-developers/why-location-are-getting-listed-in-groups-api/m-p/5232025#M3980</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1321024"&gt;@Raffaele Lagana&lt;/a&gt;&amp;nbsp;Can you please brief why this is like this? We already have&amp;nbsp;&lt;A href="https://developer.webex.com/docs/api/v1/locations" target="_blank" rel="noopener"&gt;https://developer.webex.com/docs/api/v1/locations&lt;/A&gt;&amp;nbsp;which is dealing with location.&amp;nbsp;&lt;BR /&gt;API&amp;nbsp;&amp;nbsp;&lt;A href="https://developer.webex.com/docs/api/v1/scim2-group/search-groups" target="_blank" rel="nofollow noopener noreferrer"&gt;https://developer.webex.com/docs/api/v1/scim2-group/search-groups&lt;/A&gt;&amp;nbsp;should return only groups not location.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Prashant&lt;/P&gt;</description>
      <pubDate>Tue, 03 Dec 2024 16:56:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/why-location-are-getting-listed-in-groups-api/m-p/5232025#M3980</guid>
      <dc:creator>prashant-chinchkar</dc:creator>
      <dc:date>2024-12-03T16:56:47Z</dc:date>
    </item>
    <item>
      <title>Re: Why location are getting listed in Groups API?</title>
      <link>https://community.cisco.com/t5/webex-for-developers/why-location-are-getting-listed-in-groups-api/m-p/5232366#M3984</link>
      <description>&lt;P&gt;Location is represented as a type of group in Common Identity (backend identity management service), whose usage is "location". This is how it's designed and it follows the &lt;A href="https://simplecloud.info/" target="_self"&gt;SCIM Specification&lt;/A&gt;. Basically locations are considered to be a type of&amp;nbsp;&lt;SPAN&gt;user group, in that a location usually includes a group of users, so it is returned by this API. Note that our SCIM 2.0 APIs are different to most of our other APIs in that they are specifically built to conform to the SCIM Specification standard (which is external to Cisco) and therefore it's not necessarily going to be tied to functionalities that our other APIs provide.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Dec 2024 10:24:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/why-location-are-getting-listed-in-groups-api/m-p/5232366#M3984</guid>
      <dc:creator>Raffaele Lagana</dc:creator>
      <dc:date>2024-12-04T10:24:41Z</dc:date>
    </item>
  </channel>
</rss>

