Submit a ticketCall us

Quickly Address Software Vulnerabilities
Patch Manager is an intuitive patch management software which extends the capabilities of WSUS and SCCM to not only patch Windows® servers and workstations, and Microsoft® applications, but also other 3rd-party applications which are commonly exploited by hackers. Learn more about our patch management solution.

 

Home > Success Center > Web Help Desk (WHD) > Web Help Desk Administrator Guide > Enable FIPS > Prepare for the database migration

Prepare for the database migration

Created by Steve.Hawkins, last modified by Anthony.Rinaldi on Jul 18, 2016

Views: 43 Votes: 0 Revisions: 5

After you enable FIPS 140-2 cryptography and complete the steps in the Getting Started wizard, schedule and implement the appropriate procedures in your organization to prepare all stakeholders for the database migration.

The following illustration provides an overview of the database migration milestones using the Password Security Migration Tool.

File:Success_Center_V2/Web_Help_Desk_(WHD)/WHD_Admin_MT/050/030/WHD_FIPS_Migration_Process3_707x482.png

Milestone Completed Tasks
1

Web Help Desk 12.4.0 is installed in your deployment.

You scheduled a date to invalidate all tech and client passwords in your current Web Help Desk database stored with weaker cryptography and a date to verify system status using the Audit Tool.

2

You configured a FIPS 140-2 cryptography provider in your Web Help Desk deployment.

Web Help Desk begins using FIPS 140-2 cryptography for user passwords and a non-FIPS provider for hash attachment links and third-party connection passwords.

All techs and clients are notified to log in to Web Help Desk before your scheduled date.

3

The Web Help Desk Admin runs the Password Security Migration Tool.

All non-migrated clients and techs using the non-FIPS provider are invalidated. These users are forced to change their password before they can log in and access the application.

All third-party connection passwords are re-encrypted to AES with the FIPS provider.

To prepare for the database migration:

  1. Schedule the migration.

    Select a date to invalidate all passwords stored in your current Web Help Desk database stored with weaker cryptography and a date to verify your system status.

  2. Notify all techs and clients to log in to Web Help Desk 12.4.0.

    Ensure that all clients and techs receive confirmation about the planned migration. Provide a deadline date and ample time for all users to proactively log in to Web Help Desk 12.4.0. If your clients and techs do not log in to Web Help Desk 12.4.0 by the deadline date, they will be forced to change their password after the migration before they can log in and access Web Help Desk.

  3. Record your existing SolarWinds Integration configuration settings.

    If you are connected to an external SolarWinds product (such as SolarWinds Network Performance Monitor [NPM], SolarWinds Server and Application Monitor [SAM], or SolarWinds Network Configuration Monitor [NCM] ), record your current configuration settings. All external SolarWinds integration passwords will be updated to FIPS 140-2 cryptography during the database migration.

    A list of SolarWinds connections appear.

    1. Click Setup and select SolarWinds Integration > SolarWinds Connection.
    2. Double-click a connection.
    3. Record the connection information listed in the screen.
    4. Click Next.
    5. Record the filter settings listed on the screen.
    6. In the SolarWinds Integration menu, click SolarWinds Connection.
    7. Record the connection settings for any remaining connections.

Migrate user passwords to FIPS 140-2 cryptography

On a prescheduled date, execute the database compliance tool in Web Help Desk using your administrator password to ensure that all client and tech account passwords are migrated to FIPS 140-2 cryptography. When completed, only the stored client and tech passwords using FIPS 140-2 cryptography are validated.

Prepare for the password migration

  1. Log on to Web Help Desk as an administrator.
  2. Click Setup and select General > Authentication.
  3. Scroll down to the Password Security Migration Tool window.
  4. Click Check Password Security.

    The tool scans all client and tech account passwords in your Web Help Desk database.

    If all clients and techs have logged in to Web Help Desk 12.4.0 before the scheduled date, a message displays stating that your database is now using strong cryptography and is FIPS 140-2 compliant.

    If one or more clients or techs have not logged in to Web Help Desk before the scheduled date, Web Help Desk lists the remaining number of client accounts and a list of tech accounts that require a password change. The report will include third-party integration accounts that will be migrated automatically without user intervention.

  5. Decide whether to invalidate all passwords in your database using the weaker cryptography.

    If you click No and do not invalidate all passwords, Web Help Desk will not erase any passwords from your database that are using weaker cryptography.

Execute the password migration

  1. Click Yes to invalidate all passwords.

    The following message displays:

    Are you sure you want to erase all passwords that are using weaker cryptography?

    Confirm by entering your Admin password below.

  2. Enter your admin password in the appropriate field.
  3. Click Yes to invalidate all passwords.

    When completed, a message displays listing the reset client and tech passwords.

     

    All clients who did not update their passwords are forced to create a new password when they log in to Web Help Desk. Additionally, all future client and tech account passwords will be encrypted using FIPS 140-2 cryptography.

  4. Click Save.

    The migration is completed.

Notify all users that the migration is completed

All remaining users who did not change their passwords during the notification period must navigate to the Log In page and click Forgot Password to change their password and access Web Help Desk.

 
Last modified
13:48, 18 Jul 2016

Tags

Classifications

Public