<?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 Support multiple Client IDs? in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Support-multiple-Client-IDs/m-p/330834#M39638</link>
    <description>&lt;P&gt;It doesn't appear this addon supports multiple Client IDs (like the Splunk Add-on for Microsoft Cloud Services Addon)?&lt;/P&gt;

&lt;P&gt;It would be great it this addon could leverage the existing settings/inputs present in the &lt;A href="https://splunkbase.splunk.com/app/3110/"&gt;Splunk Add-on for Microsoft Cloud Services Addon&lt;/A&gt;, so one does not have duplicate client id/secrets for different addons on the same SH. &lt;/P&gt;</description>
    <pubDate>Tue, 23 Jan 2018 01:44:04 GMT</pubDate>
    <dc:creator>ChrisBell04</dc:creator>
    <dc:date>2018-01-23T01:44:04Z</dc:date>
    <item>
      <title>Support multiple Client IDs?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Support-multiple-Client-IDs/m-p/330834#M39638</link>
      <description>&lt;P&gt;It doesn't appear this addon supports multiple Client IDs (like the Splunk Add-on for Microsoft Cloud Services Addon)?&lt;/P&gt;

&lt;P&gt;It would be great it this addon could leverage the existing settings/inputs present in the &lt;A href="https://splunkbase.splunk.com/app/3110/"&gt;Splunk Add-on for Microsoft Cloud Services Addon&lt;/A&gt;, so one does not have duplicate client id/secrets for different addons on the same SH. &lt;/P&gt;</description>
      <pubDate>Tue, 23 Jan 2018 01:44:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Support-multiple-Client-IDs/m-p/330834#M39638</guid>
      <dc:creator>ChrisBell04</dc:creator>
      <dc:date>2018-01-23T01:44:04Z</dc:date>
    </item>
    <item>
      <title>Re: Support multiple Client IDs?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Support-multiple-Client-IDs/m-p/330835#M39639</link>
      <description>&lt;P&gt;Moving the ClientID/Secret to the input configuration would be the best solution. I need to pull data from multiple Azure AD tenants and I really need this functionality!!&lt;/P&gt;</description>
      <pubDate>Mon, 19 Mar 2018 20:19:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Support-multiple-Client-IDs/m-p/330835#M39639</guid>
      <dc:creator>trevsmit</dc:creator>
      <dc:date>2018-03-19T20:19:03Z</dc:date>
    </item>
    <item>
      <title>Re: Support multiple Client IDs?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Support-multiple-Client-IDs/m-p/330836#M39640</link>
      <description>&lt;P&gt;Moving the ClientID/Secret to the input configuration would be the best solution. I need to pull data from multiple Azure AD tenants and I really need this functionality!!&lt;/P&gt;</description>
      <pubDate>Mon, 19 Mar 2018 20:19:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Support-multiple-Client-IDs/m-p/330836#M39640</guid>
      <dc:creator>trevsmit</dc:creator>
      <dc:date>2018-03-19T20:19:30Z</dc:date>
    </item>
    <item>
      <title>Re: Support multiple Client IDs?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Support-multiple-Client-IDs/m-p/330837#M39641</link>
      <description>&lt;P&gt;Any updates on updating the app to support this? I'd prefer not to clone the app /use a diff name or modify the existing app.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jul 2018 17:31:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Support-multiple-Client-IDs/m-p/330837#M39641</guid>
      <dc:creator>Bloodnite</dc:creator>
      <dc:date>2018-07-18T17:31:57Z</dc:date>
    </item>
    <item>
      <title>Re: Support multiple Client IDs?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Support-multiple-Client-IDs/m-p/330838#M39642</link>
      <description>&lt;P&gt;I agree, multi-tenant support is a big requirement to make this more useful. I am going to try to run 2 deployments at a time but it requires alot of regex changes to inputs/outputs.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Aug 2018 23:55:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Support-multiple-Client-IDs/m-p/330838#M39642</guid>
      <dc:creator>troybebee</dc:creator>
      <dc:date>2018-08-09T23:55:05Z</dc:date>
    </item>
    <item>
      <title>Re: Support multiple Client IDs?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Support-multiple-Client-IDs/m-p/330839#M39643</link>
      <description>&lt;P&gt;I have to concur ... attempting to clone instances of the TA to cope with separate client_ids &amp;amp; tenants and it's doing my head in.  Other than this limitation the TA works well.  Multi-tenant capability would be #1 on the list of enhancements.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Aug 2018 16:27:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Support-multiple-Client-IDs/m-p/330839#M39643</guid>
      <dc:creator>tobinbxnz</dc:creator>
      <dc:date>2018-08-16T16:27:31Z</dc:date>
    </item>
    <item>
      <title>Re: Support multiple Client IDs?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Support-multiple-Client-IDs/m-p/330840#M39644</link>
      <description>&lt;P&gt;Addition ... having the add-on cope with the latencies of the audit records in particular ... there are other solutions being proposed&lt;/P&gt;</description>
      <pubDate>Tue, 18 Dec 2018 23:38:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Support-multiple-Client-IDs/m-p/330840#M39644</guid>
      <dc:creator>tobinbxnz</dc:creator>
      <dc:date>2018-12-18T23:38:42Z</dc:date>
    </item>
  </channel>
</rss>

