RPC over HTTPS question



hi,

I'm about to setup RPC over HTTPS.
my boss does no wants to a public (verisign or other) certificate but
one that has to be in each and every remote PC. well. why not (he's the
boss) but he also want this certificate to be 1) password protected, 2)
different for each user.

I think 1 is easy but what about 2?

TIA,
Pierre.
.



Relevant Pages

  • 2 Websites & 2 Certificates on 1 IIS Server
    ... We want to add another website to the same Server. ... access www.website2.org, we want to use an SSL connection (https), and we ... also want www.website2.org be authenticated with a Verisign certificate. ...
    (microsoft.public.inetserver.iis)
  • Chaining x.509 certificates
    ... x.509 certificate (via keytool and jarsigner) to sign our jars before ... It looks like, with https, our customer will need their own x.509 ... certificate, or get one from Verisign, et al. ...
    (comp.security.misc)
  • Chaining x.509 certificates
    ... x.509 certificate (via keytool and jarsigner) to sign our jars before ... It looks like, with https, our customer will need their own x.509 ... certificate, or get one from Verisign, et al. ...
    (comp.security.misc)
  • Re: RPC over HTTPS question
    ... my boss does no wants to a public (verisign or other) certificate but ... the boss) but he also want this certificate to be 1) password ... there's no password protection, and each user will have to use the same cert ...
    (microsoft.public.exchange2000.admin)
  • Re: Chaining x.509 certificates
    ... > I work for a software development organization. ... > shipping a new product enhancement that uses https for security. ... > certificate, or get one from Verisign, et al. ...
    (comp.security.misc)