> Hi Tareq,
>
> The sample certificates that you use are not issued from trusted authority like Verisign or other. I.e. they are test ones.
> How did you create your policy?
>Did you use the policy wizard?
using wizard
Which options did you choose?
I use the option which stated in the Lab
Tech.ED 2004
Hands-On Lab
Lab Manual
HOLDEVL34: WSE 2.0 Security and Policy
-----------------------------------------------------
Task 1 – Installing the Sample Certificates
WSE 2.0 provides two sample certificates for you to use while testing your
WSE 2.0 applications. These two certificates were generated by the makecert
tool provided in the Microsoft Platform Software Development Kit. In order to
begin using these certificates in your applications, you must first install
them on your computer.
Note: you should not use these sample certificates in a production
environment. You must contact a certificate authority, request your own
certificate, and follow the procedures shown here to use it.
• 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.
• Your MMC window should now look something like this:
• 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.
----------------------------------------------------
> Regards,
>
[quoted text clipped - 3 lines]
> MCAD Charter Member
> MCSD.NET Early Achiever