<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style="word-wrap: break-word;"><br><div>So you already know where the problem is.</div>
</div></blockquote><div><br>As I stated above, since all the three clients I tried get that message, I suspected that it could perhaps be a server issue; but that was only a suspect.<br>The first suspect was about the certificate itself, which misses a URI:sip subjectAltName.<br>
Does anybody knows if this is mandatory?<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="word-wrap: break-word;"><div><br></div><div>By the way, where do you configure a client side X.509 certificate in Counterpath's Eyebeam client?<br clear="all"></div></div></blockquote><div><br>It gets the certificate from the microsoft windows keystore; in fact, the proper way to have it use client certificates is to install them in the operating system keystore.<br>
<br></div></div>Just to ask, does anybody uses successfully a client certificate for authentication?<br>If so, I would love, if possible, to see a sample of a working client certificate, so to triple check it and see how it must be formatted.<br>
<br>Thanks so much<br>
-- <br>Fabio<br>