<?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: SSL Multiple Tunnel Groups with Multiple group policies in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ssl-multiple-tunnel-groups-with-multiple-group-policies/m-p/1346021#M948275</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Easy. Disable the drop-down list, and use the authentication-server (LDAP or Radius) in the DefaultWEBVPNGroup. By default when you browse to the ASA, it will be using the DefaultWEBVPNGroup. Let LDAP or Radius take care of the rest.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will get the functionality you are looking for.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS. If this post was helpful, please rate it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 08 Oct 2009 21:36:20 GMT</pubDate>
    <dc:creator>auraza</dc:creator>
    <dc:date>2009-10-08T21:36:20Z</dc:date>
    <item>
      <title>SSL Multiple Tunnel Groups with Multiple group policies</title>
      <link>https://community.cisco.com/t5/network-security/ssl-multiple-tunnel-groups-with-multiple-group-policies/m-p/1346020#M948274</link>
      <description>&lt;P&gt;Hello folks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a query and cant seem to find an answer on the web.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have configured SSL Clientless VPN on a lab ASA5510, using 2 tunnel groups, one for enginneers and one for staff, mapped to 2 different group policies, each with different customisation. I have mapped the AD groups to the tunnel groups using both ACS and now LDAP (currently in use), both working successfully, using group lock and LDAP map of IETF-Radius-Class to Group name ensures engineers get assigned to the engineers tunnel group and staff get mapped to the staff tunnel group only.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The question i have is....is there a way to use a single tunnel group to map the user based on AD group which will then use the correct Group-policy (1 tunnel group to multiple group-polciies). I have seen examples of doing this with different URLs but want to know if they can all use the same URL and avoid using the drop down list using aliases.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It may be a simple "No" but it would be nice to know how to do it without using the URLs or drop down list. Users are easily confused ......&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 11:42:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssl-multiple-tunnel-groups-with-multiple-group-policies/m-p/1346020#M948274</guid>
      <dc:creator>GarySLear</dc:creator>
      <dc:date>2020-02-21T11:42:30Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Multiple Tunnel Groups with Multiple group policies</title>
      <link>https://community.cisco.com/t5/network-security/ssl-multiple-tunnel-groups-with-multiple-group-policies/m-p/1346021#M948275</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Easy. Disable the drop-down list, and use the authentication-server (LDAP or Radius) in the DefaultWEBVPNGroup. By default when you browse to the ASA, it will be using the DefaultWEBVPNGroup. Let LDAP or Radius take care of the rest.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will get the functionality you are looking for.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS. If this post was helpful, please rate it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Oct 2009 21:36:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssl-multiple-tunnel-groups-with-multiple-group-policies/m-p/1346021#M948275</guid>
      <dc:creator>auraza</dc:creator>
      <dc:date>2009-10-08T21:36:20Z</dc:date>
    </item>
  </channel>
</rss>

