Compartir a través de

.NET Passport Environments

  • Artículo

.NET Passport Environments

There are two distinct instances of the Microsoft® .NET Passport service, which are commonly referred to as environments. The Preproduction (PREP) environment is used for site development and testing; it enables participating sites to validate their development efforts against .NET Passport servers without granting access to real-world .NET Passport users and profiles. The Production environment is the live .NET Passport service; it is used by all working and approved .NET Passport participating sites after they are publicly deployed. User accounts that exist in the Production environment do not exist in the PREP environment, and vice versa.

The code used to implement a .NET Passport site is the same for both environments. The Passport Manager connects to the instance of the .NET Passport service for which the server is configured. You can switch between environments by configuring your server manually or by using the Passport Manager Administration utility.

To switch between environments using Passport Manager Administration utility

  1. Run the Passport Manager Administration utility.

  2. Look at the value of the Current text box. If this is not the name of the desired configuration environment, click the Change button.

    This will cause the Choose Environment dialog box to appear.

  3. Choose the appropriate environment from one of the options in the Environment section, and then click OK.

  4. Click Commit Changes.

    If a change was made to your configuration, the Confirm Server Changes dialog box appears.

  5. In the Confirm Server Changes dialog box, click OK.

    It may also be necessary to reinstall or at least use the /makecurrent option to reenable encryption keys that are particular to the new environment, if the key versions between environments are different. For more information, see Installing .NET Passport Encryption Keys.

  6. Stop the Microsoft® Internet Information Services (IIS) process.

    This is necessary in order to force Passport Manager to load a new Component Configuration Document (CCD) file and to reload the encryption key.

  7. Restart the IIS process.

  8. Using a browser, request any page on the server site that calls Passport Manager application programming interface (API) elements. For example, request: 

    https://[your server]/passporttest/

    Loading the object forces a reload of the CCD file, and Passport Manager is now configured to run against the new environment.

Generally, the Passport Manager Administration utility should only be used to switch environments while the computer being affected is still in a development situation.

Setting the environment is global for all Passport Manager sites running on the server. If you have more than one site configured to use Passport Manager, all these sites will have to share the environment settings.

To switch between environments manually

To sign in to the PREP environment, you must change registry settings and configure the client computer as follows:

  1. Sign in to the computer using an account with Administrator privileges.

  2. Delete the contents of the following registry keys:

    • Passport Network Configuration:
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Passport
    • Passport DAMap:
      HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Passport\DAMap
    Note  It might be helpful to save these values before deleting them in order to restore them quickly.

  3. Run the registry script for the PREP environment.

     https://www.passport.com/downloads/blaze-default.reg

Domain Name Resolution in the PREP Environment

Some domain names do not exist in the PREP environment. The following table lists the most common domains and the substitute domain names to use to test against them.

Domain Name Substitute PREP Domain Name
hotmail.com hmgreen.com
msn.com manga.net
passport.com passport-ppe.com

To sign in to the Production environment, follow the first two steps. It is recommended that you use the Passport Manager Administration utility rather than editing the registry directly.

See Also

Service Requirements | Component Configuration Document | Registering Your .NET Passport Site | Passport Manager Administration Utility