Blogger :
Musings from Gudge
All posts :
All posts by Musings from Gudge
Category :
WSCF/WCF
Blogged date : 2006 May 16
A while back, I wrote a
couple of
entries on
httpcfg and using it to configure certificates when self-hosting Indigo services. The
second entry talked about the various flags that could be passed using the -f parameter.
Unfortunately, I neglected to mention that you can't actually use the syntax with preceding 0x and zeros, despite the fact that the usage help you get from just typing httpcfg at the command line would lead you to believe that such syntax would work just fine.
It turns out you actually need to specify the values as straight decimal numbers, like this;
httpcfg <otheroptions> -f 1 (Gives you cert mapping to windows accounts)
httpcfg <otheroptions> -f 2 (Gives you client cert support)
httpcfg <otheroptions> -f 3 (Gives you both client cert support and mapping to windows accounts)
httpcfg <otheroptions> -f 4 (Turns off ISAPI routing)
httpcfg <otheroptions> -f 5 (Turns off ISAPI routing and gives you cert mapping to windows accounts)
httpcfg <otheroptions> -f 6 (Turns off ISAPI routing and gives you client cert support)
httpcfg <otheroptions> -f 7 (Turns off ISAPI routing and gives you both client cert support and mapping to windows accounts)
So if you want to use client certs you need -f 2 on the command line ( and NOT -f 0x00000002 )