Re: WSE 2.0 and Win 2000 Server

From: Softwaremaker (msdn_at_removethis.softwaremaker.net)
Date: 10/26/04

  • Next message: Sumaira Ahmad: "Authorization with WS Secure Conversation" 
    Date: Wed, 27 Oct 2004 07:26:28 +0800

    Import it from the Internet Explorer as opposed to mmc. Check out the paras
    below and take note of the para with >>

    Open an MMC console by pressing Start, press Run, type mmc, and then click
    OK.
    On the File menu, click Add/Remove Snap-in
    Click Add, under Snap-in, double-click Certificates.
    Click My user account to add the certificates for the current user. Click
    Finish.
    Click Add, under Snap-in, double-click Certificates.
    Click Computer account for the local machines certificates. Click Finish.
    Close the dialog boxes.

    In the console tree, under Certificates - Current User\Personal, click
    Certificates.
    Open the Certificate Import wizard by selecting Action | All Tasks and
    choose Import.
    Follow the wizard. When asked for the file to import, specify: C:\Program
    Files\Microsoft WSE\v2.0\Samples\Sample Test Certificates\Client
    Private.pfx.
    When asked for the private key password, specify: wse2qs.
    Finish the wizard.
    Note: this certificate will be used by our client application to sign
    messages sent to the service. It could also be used to identify the client
    for authentication purposes.

    In the console tree, under Certificates (Local Computer)\Personal, click
    Certificates.
    Open the Certificate Import wizard by selecting Action | All Tasks and
    choose Import.
    Follow the wizard. When asked for the file to import, specify: C:\Program
    Files\Microsoft WSE\v2.0\Samples\Sample Test Certificates\Server
    Private.pfx.
    When asked for the private key password, specify: wse2qs.
    Finish the wizard.
    Note: this certificate will be used to encrypt messages between the
    applications. The client application will use the public key to encrypt the
    message and the service will use the private key to decrypt the message. The
    client needs to have the public portion of the certificate available in the
    Current User store.

    In the console tree, under Certificates - Current User\Other People, click
    Certificates.
    >> Note: if you don't have an Other People store under Current User, open
    Internet Explorer, select Tools, Internet Options, Content, and press the
    Certificates >> button. You should see an Other People tab in the
    certificates dialog. You can import the certificate here through this
    interface or you can return to mmc and refresh the Current User tree and
    Other People should now show up.

    Open the Certificate Import wizard by selecting Action | All Tasks and
    choose Import.
    Follow the wizard. When asked for the file to import, specify: C:\Program
    Files\Microsoft WSE\v2.0\Samples\Sample Test Certificates\Server Public.cer.
    Finish the wizard.
    Note: this certificate only contains the public portion of Server
    Private.pfx. The client will use this to encrypt messages and the server
    will use the private key installed in the Local Machine store to decrypt the
    messages.

    btw, this also applies to Windows 2003 Server...

    hth. 

    -- 
Thank you.
Regards,
Softwaremaker
http://www.softwaremaker.net/blog
=========================================
"Tim Heuer" <heuert at Comcast dot net> wrote in message
news:C9A0F956-1AAF-45D7-B8ED-0F98F7B9621F@microsoft.com...
> There is a post from 9/21 named "Problem Setting Up x.509 Certificates for
> WSE2.0" (from Mike Clark) which states the same issue I'm having re: Win
2K
> and the Other People Store.  Was there ever a resolution to his (and my)
> issue?
>
> Thanks
>
> "Tim Heuer" wrote:
>
> > I've got Win 2000 Server.  It dosn't have a "Other People" Certificate
Store
> > as is available in XP and Server 2003.  Does this preclude me from
signing
> > and using secure conversation with X.509s?  Thanks Again for the Help
> >
> > -- 
> > Tim Heuer
> > heuert  at  Comcast dot net
  • Next message: Sumaira Ahmad: "Authorization with WS Secure Conversation"