Thanks but I coulf not see any reference to proxy support in that document.
I have experience of configuring EAP-TLS. However in this case I want to proxy the authentication to another radius server (ACS or ISA)
I am unsure how to set up the CA chain. i.e. Is the primary ACS radius server going to be the issuing CA or is it the secondary. I hope that the secondary is just a proxy radius server that uses a back end username database such as MS AD and that the name is stripped from the certificate at the primary.
I have completed the project now. The way the proxy finds the information is that it reads the certificate details and then uses the CN information to decide on the target radius server. It does not have to have the EAP type configured or be part of the certificate chain. I did not get a chance to see if it uses the SAN feild before the CN feild. The latter would be usefull with user (not machine) certificates ecause there tends not to be delimiting information in the CN with MS enterprise CA certificates. Stand Alone MS CA allows user to put any info in the CN but AD needs Enterprise CA for proper CA intergration and autoenrollment.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...