<?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 Proxy authentication in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/proxy-authentication/m-p/841699#M5528</link>
    <description>&lt;P&gt;I have the following topology. R1 with firewall features, R2 and ACS belong to Customer A, while R3 with firewall features and VPN concentrator belong to Customer B. &lt;/P&gt;&lt;P&gt;		    &lt;/P&gt;&lt;P&gt;User--Internet--R1FW---R2--R3FW--VPNConcentrator 	          |&lt;/P&gt;&lt;P&gt;                 ACS	    &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The requirement is for User which is a mobile user of Customer A to connect to Customer?s B VPN concentrator and open a IPSEC connection using Cisco VPN client.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;User must also be authenticated when entering Customer A network and I am considering proxy authentication. So, before opening the vpn client, the user will initiate an http connection to R1 and authenticate itself to the ACS server using a username/password. If authentication is successful, an entry will be downloaded to the R1 inbound access-list to allow traffic from the IP of the authenticated user to the IP of the VPN concentrator.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem is that Customer B needs to know the IP addresses of users with vpn clients so that it can allow only traffic from this IP passing through R3 FW. &lt;/P&gt;&lt;P&gt;Since this is a mobile user it can connect from different places so he does not use a single IP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here are my thoughts/questions to address this issue:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Is it possible to assign User with a static IP when authentication with the ACS along with proxy authentication?&lt;/P&gt;&lt;P&gt;2. Can I use NAT outside at R1 so I translate user IP to a static IP?   Do you see any issue with this implementation?&lt;/P&gt;&lt;P&gt;3. Is there another solution to achieve the above: 1. authentication of mobile users and static IP assignment?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Evi&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 18:19:14 GMT</pubDate>
    <dc:creator>epekou</dc:creator>
    <dc:date>2020-02-21T18:19:14Z</dc:date>
    <item>
      <title>Proxy authentication</title>
      <link>https://community.cisco.com/t5/network-access-control/proxy-authentication/m-p/841699#M5528</link>
      <description>&lt;P&gt;I have the following topology. R1 with firewall features, R2 and ACS belong to Customer A, while R3 with firewall features and VPN concentrator belong to Customer B. &lt;/P&gt;&lt;P&gt;		    &lt;/P&gt;&lt;P&gt;User--Internet--R1FW---R2--R3FW--VPNConcentrator 	          |&lt;/P&gt;&lt;P&gt;                 ACS	    &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The requirement is for User which is a mobile user of Customer A to connect to Customer?s B VPN concentrator and open a IPSEC connection using Cisco VPN client.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;User must also be authenticated when entering Customer A network and I am considering proxy authentication. So, before opening the vpn client, the user will initiate an http connection to R1 and authenticate itself to the ACS server using a username/password. If authentication is successful, an entry will be downloaded to the R1 inbound access-list to allow traffic from the IP of the authenticated user to the IP of the VPN concentrator.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem is that Customer B needs to know the IP addresses of users with vpn clients so that it can allow only traffic from this IP passing through R3 FW. &lt;/P&gt;&lt;P&gt;Since this is a mobile user it can connect from different places so he does not use a single IP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here are my thoughts/questions to address this issue:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Is it possible to assign User with a static IP when authentication with the ACS along with proxy authentication?&lt;/P&gt;&lt;P&gt;2. Can I use NAT outside at R1 so I translate user IP to a static IP?   Do you see any issue with this implementation?&lt;/P&gt;&lt;P&gt;3. Is there another solution to achieve the above: 1. authentication of mobile users and static IP assignment?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Evi&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:19:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/proxy-authentication/m-p/841699#M5528</guid>
      <dc:creator>epekou</dc:creator>
      <dc:date>2020-02-21T18:19:14Z</dc:date>
    </item>
    <item>
      <title>Re: Proxy authentication</title>
      <link>https://community.cisco.com/t5/network-access-control/proxy-authentication/m-p/841700#M5532</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Does the Concentrator have connectivity with Cust A's ACS server? I assume so. The best way to assign the remote client an IP address is to use an IP pool which is attached to the VPN user's group. Then Cust B would be able to build fw rules around this subnet. Be sure to use NARs to permit only authentication to the VPN and not any other RADIUS/TACACS+ clients. HTH.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Dec 2007 03:01:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/proxy-authentication/m-p/841700#M5532</guid>
      <dc:creator>j.langton</dc:creator>
      <dc:date>2007-12-14T03:01:29Z</dc:date>
    </item>
  </channel>
</rss>

