<?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: AAA and multiple context ASA for multi-tenant cloud practice in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/aaa-and-multiple-context-asa-for-multi-tenant-cloud-practice/m-p/3495410#M201991</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I recommend you also post this to the Cisco Support Community for additional feedback.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://supportforums.cisco.com/" title="https://supportforums.cisco.com/"&gt;Cisco Support Community&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;Kelli Glass&lt;BR /&gt;Moderator for Cisco Customer Communities&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 23 Dec 2014 17:46:39 GMT</pubDate>
    <dc:creator>keglass</dc:creator>
    <dc:date>2014-12-23T17:46:39Z</dc:date>
    <item>
      <title>AAA and multiple context ASA for multi-tenant cloud practice</title>
      <link>https://community.cisco.com/t5/network-security/aaa-and-multiple-context-asa-for-multi-tenant-cloud-practice/m-p/3495409#M201990</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My company has a new cloud practice and are using multiple context ASAs for different tenants. The customers do not manage the contexts, we do.&amp;nbsp; As of right now, the way we manage the customers contexts is by SSHing into the Admin context then we do a "changeto" in order to access the other contexts. There is no logical connection to their context.&amp;nbsp; We have AAA set up on the Admin context and it is talking to a SecureACS server.&amp;nbsp; One thing I noticed is that once I do a "changeto" and go to a customer context, I don't seem to receive accounting messages anymore.&amp;nbsp; Authoriation doesn't seem to matter anymore at this point either.&amp;nbsp; Obviously the local context AAA has taken over.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any way for the other contexts to send authorization and accounting information via the admin context?&amp;nbsp; I would rather not create logical management connections from our VRF on the core into each customer context if I don't have to.&amp;nbsp; My guess is that I will need to do this, but figured I would see if anyone knew a special way to avoid doing this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Dec 2014 13:52:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/aaa-and-multiple-context-asa-for-multi-tenant-cloud-practice/m-p/3495409#M201990</guid>
      <dc:creator>m.yost</dc:creator>
      <dc:date>2014-12-19T13:52:13Z</dc:date>
    </item>
    <item>
      <title>Re: AAA and multiple context ASA for multi-tenant cloud practice</title>
      <link>https://community.cisco.com/t5/network-security/aaa-and-multiple-context-asa-for-multi-tenant-cloud-practice/m-p/3495410#M201991</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I recommend you also post this to the Cisco Support Community for additional feedback.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://supportforums.cisco.com/" title="https://supportforums.cisco.com/"&gt;Cisco Support Community&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;Kelli Glass&lt;BR /&gt;Moderator for Cisco Customer Communities&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Dec 2014 17:46:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/aaa-and-multiple-context-asa-for-multi-tenant-cloud-practice/m-p/3495410#M201991</guid>
      <dc:creator>keglass</dc:creator>
      <dc:date>2014-12-23T17:46:39Z</dc:date>
    </item>
  </channel>
</rss>

