<?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 How to use multiple interfaces for same ldap server in aaa-server in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/how-to-use-multiple-interfaces-for-same-ldap-server-in-aaa/m-p/3189747#M552575</link>
    <description>&lt;P&gt;Hello, all!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm currently using DUO to authenticate VPN users, using LDAP connector.&lt;/P&gt;&lt;P&gt;DUO just provides 1 hostname to&amp;nbsp;access their LDAP server, and I want to use redundant internet interfaces to access this.&lt;/P&gt;&lt;P&gt;I already have a setup with SLA and track to enable/disable routes based on network availability, but in aaa-server configuration, I need to specify an interface, and all my redundancy is gone for authentication.&lt;/P&gt;&lt;P&gt;I tried to set another aaa-server entry with same hostname and another interface, but ASA just ignores...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any ideas on how to use&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;See configuration example below:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;aaa-server Duo-LDAP (outside) host api-XXXXXXXXXXX.duosecurity.com&lt;BR /&gt;timeout 180&lt;BR /&gt;server-port 636&lt;BR /&gt;ldap-base-dn dc=XXXXXXXXXXX,dc=duosecurity,dc=com&lt;BR /&gt;ldap-naming-attribute cn&lt;BR /&gt;ldap-login-password XXXXXXXXXXX&lt;BR /&gt;ldap-login-dn dc=XXXXXXXXXXX,dc=duosecurity,dc=com&lt;BR /&gt;ldap-over-ssl enable&lt;BR /&gt;server-type auto-detect&lt;/P&gt;</description>
    <pubDate>Sat, 22 Feb 2020 07:40:56 GMT</pubDate>
    <dc:creator>Departamento TI</dc:creator>
    <dc:date>2020-02-22T07:40:56Z</dc:date>
    <item>
      <title>How to use multiple interfaces for same ldap server in aaa-server</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-use-multiple-interfaces-for-same-ldap-server-in-aaa/m-p/3189747#M552575</link>
      <description>&lt;P&gt;Hello, all!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm currently using DUO to authenticate VPN users, using LDAP connector.&lt;/P&gt;&lt;P&gt;DUO just provides 1 hostname to&amp;nbsp;access their LDAP server, and I want to use redundant internet interfaces to access this.&lt;/P&gt;&lt;P&gt;I already have a setup with SLA and track to enable/disable routes based on network availability, but in aaa-server configuration, I need to specify an interface, and all my redundancy is gone for authentication.&lt;/P&gt;&lt;P&gt;I tried to set another aaa-server entry with same hostname and another interface, but ASA just ignores...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any ideas on how to use&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;See configuration example below:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;aaa-server Duo-LDAP (outside) host api-XXXXXXXXXXX.duosecurity.com&lt;BR /&gt;timeout 180&lt;BR /&gt;server-port 636&lt;BR /&gt;ldap-base-dn dc=XXXXXXXXXXX,dc=duosecurity,dc=com&lt;BR /&gt;ldap-naming-attribute cn&lt;BR /&gt;ldap-login-password XXXXXXXXXXX&lt;BR /&gt;ldap-login-dn dc=XXXXXXXXXXX,dc=duosecurity,dc=com&lt;BR /&gt;ldap-over-ssl enable&lt;BR /&gt;server-type auto-detect&lt;/P&gt;</description>
      <pubDate>Sat, 22 Feb 2020 07:40:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-use-multiple-interfaces-for-same-ldap-server-in-aaa/m-p/3189747#M552575</guid>
      <dc:creator>Departamento TI</dc:creator>
      <dc:date>2020-02-22T07:40:56Z</dc:date>
    </item>
    <item>
      <title>Re: How to use multiple interfaces for same ldap server in aaa-server</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-use-multiple-interfaces-for-same-ldap-server-in-aaa/m-p/3356708#M552578</link>
      <description>&lt;P&gt;Did you come up with a fix for this?&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Mar 2018 13:58:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-use-multiple-interfaces-for-same-ldap-server-in-aaa/m-p/3356708#M552578</guid>
      <dc:creator>c.registration</dc:creator>
      <dc:date>2018-03-28T13:58:03Z</dc:date>
    </item>
    <item>
      <title>Re: How to use multiple interfaces for same ldap server in aaa-server</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-use-multiple-interfaces-for-same-ldap-server-in-aaa/m-p/3357002#M552581</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;If configuring a seconary LDAP for the same server doesn't work, I think that your last option would be to use EEM. Watch for LDAP unavailable log to configure a new LDAP server connection &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Octavian&lt;/P&gt;</description>
      <pubDate>Wed, 28 Mar 2018 19:34:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-use-multiple-interfaces-for-same-ldap-server-in-aaa/m-p/3357002#M552581</guid>
      <dc:creator>Octavian Szolga</dc:creator>
      <dc:date>2018-03-28T19:34:22Z</dc:date>
    </item>
    <item>
      <title>Re: How to use multiple interfaces for same ldap server in aaa-server</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-use-multiple-interfaces-for-same-ldap-server-in-aaa/m-p/4708017#M577884</link>
      <description>&lt;P&gt;This isn't a direct solution, but it may be an alternative strategy. I found this &lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa918/release/notes/asarn918.html" target="_self"&gt;in the v9.18 release notes&lt;/A&gt;:&lt;/P&gt;&lt;PRE&gt;Loopback interface support for BGP and management traffic&lt;/PRE&gt;&lt;P&gt;You could potentially create a BGP peering with your network, configure a loopback (with a name) on the ASA and redistribute it into BGP. Then bind the aaa-server group to the loopback.&lt;/P&gt;&lt;P&gt;I haven't tested this, but it looks like a feasible option for using the same LDAP servers via multiple physical interfaces.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2022 09:08:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-use-multiple-interfaces-for-same-ldap-server-in-aaa/m-p/4708017#M577884</guid>
      <dc:creator>j.a.m.e.s</dc:creator>
      <dc:date>2022-10-24T09:08:21Z</dc:date>
    </item>
  </channel>
</rss>

