On Sun, Mar 3, 2013 at 10:03 AM, Phil Mayers <p.may...@imperial.ac.uk>wrote:
> Try with a private ca first, it'll save cash > > I tested using a standard TLD domain cert that I have on-hand Of course, it works as expected. It appears you are indeed correct - wildcard certs do not work for this purpose under Windows. Thank you all for the help. > > Thomas Simmons <twsn...@gmail.com> wrote: >> >> On Sun, Mar 3, 2013 at 6:41 AM, Phil Mayers <p.may...@imperial.ac.uk>wrote: >> >>> When you enable "validate...", what are you entering as the server name? >>> I'm not sure wildcard certs work with eap under windows. >>> >>> Hello Phil, >> >> Initially, I unchecked "Connect to these servers" and left this field >> empty - this is what I did with the self-signed cert that worked. I also >> tried *.mydomain.com (the CN) and domain.com. I can purchase a standard >> cert to verify this is the problem. >> >> >>> Thomas Simmons <twsn...@gmail.com> wrote: >>> >>> >Hello All, >>> > >>> >I'm trying to get my setup working with a GoDaddy-issued wildcard >>> >certificate (I understand self-signed is recommended). I don't >>> >understand >>> >why this is not working and appreciate any input. What I have found so >>> >far: >>> > >>> >Everything works with self-signed certs. With the CA cert imported, >>> >"Validate server certificate" is not required. >>> >Everything works with GoDaddy certs on Android. >>> >Everything works with GoDaddy certs and "Validate ..." unchecked. >>> >>> -- >>> Sent from my mobile device, please excuse brevity and typos. >>> >> >> > -- > Sent from my mobile device, please excuse brevity and typos. >
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html