I am trying to setup VPN for multi-domain PCs only. I have a cert on an ASA that allows our main domain computers to connect to the VPN. We are also installing a root CA and issuing certs to computers of other domains. I am new to setting up this type of authentication. I am unable to get the other domain computers to connect. Do they all have to be part of the same domain? This is for a government agency and it will be some time before we are all one domain.
Hi, I assume you are referring to an Remote Access VPN on an ASA and using AnyConnect? You could issue certificates to computers/users of the 2nd domain from the 1st domain (that the ASA can already authenticate) or if the 2nd domain has it's own CA, you should be to define another Trustpoint on the ASA and therefore the ASA would trust either CA and could authenticate connections using either certificate.
So therefore they don't necessarily need to be part of the same domain, it would make things easier for you though.
Threat Response Basics
What is Threat Response and how can it help my organization?
What is the cost of Threat Response?
What are the deployment options for Threat Response?
Is Threat Response available outside of the United States?
Gartner has once again named Cisco a Leader in the Magic Quadrant for Network Firewalls. This distinction recognizes Cisco's ingenuity in redefining the firewall as the basis for an integrated security platform.
Find out how Cisco stands out from the comp...
Hi experts,I would like any suggestions on this topology. We are is the middle of replacing our old ASA5520 with the new FirePower. Our current firewall terminate our IPsec tunnels and the GRE is terminated on the first inside router's loopback on the sec...
Hi All, A customer wants to authenticate Anyconnect VPN users from an ASA using the client installed certificate and then with AD. i.e. Is this a corporate device?Would we recommend authenticating the cert on the ASA then passing the AD check to ISE ...
Hello Team, we are getting alert in FMC stating policy deployment failed, we are running on 6.2.0 version and not sure which version is stable version to re mediate this issue, in one event i have seen restart will resolve this issue but is it perman...