OWA 2003, S/MIME, 3rd party certificates

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Administrator (Administrator_at_discussions.microsoft.com)
Date: 09/07/04


Date: Tue, 7 Sep 2004 15:03:05 -0700

What's the proper way to enable OWA 2003 support of 3rd party certificates
such as Thawte? I've got a handful of users needing encryption capabilities
but OWA isn't letting them use their certs (not on server, is my assumption)

Trying to sign only:

You are attempting to sign the message with an invalid digital ID. The
certificate chain that contains the digital ID was not created properly.

Trying to sign and encrypt:
A digital ID that allows you to encrypt this messages is missing. If your
digital ID isn't trusted by the Exchange server, you can't use it to encrypt
messages. Ask your server administrator to have the issuer of the digital ID
trusted, or send the message unencrypted.

What's the right way to get this going?



Relevant Pages

  • Re: Encrypting one line
    ... > line (string) before writing it to the file. ... logging system you don't want to mess with, ... The proper solution is most likely to encrypt the entire log file; ...
    (borland.public.delphi.language.objectpascal)
  • encrypt a message
    ... HI groups i am trying to encrypt a message or rather a password and ... int main ... i append the encrypted string into a file and then decrypt it back ... suggest me the proper group. ...
    (comp.security.unix)
  • Re: autoconf / automake problem
    ... > Using -lpthread directly is not the proper way. ... You should compile ... GPG Public Key: 0x25BFB848. ... Please sign and encrypt your mail. ...
    (comp.os.linux.development.apps)