Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This page describes an experimental feature of USAS and USPS Redesign application may assist in migration of user passwords from Classic to Redesign. The feature is believed to be functioning but has not undergone routine testing.

When a district migrates from Classic to Redesign, it is necessary to set new passwords on the imported Redesign user profiles.  Because passwords are one-way encoded on OpenVMS, it is not possible to extract OpenVMS passwords for importing.   The normal practice is to manually set new passwords.

However, for districts with a large number of users, this may create a burden and hinder smooth migration.  In this case, it may be desirable to assist users in migrating the password.   The Redesign applications contain an optional module named "Legacy Password Migration". 

If enabled and configured, the Redesign authentication system will check the Redesign, and any configured ADS and LDAP authentication sources.  If those fail, it will attempt to authenticate against the configured Classic SOAP service.   If the Classic authentication succeeds, then the password will be marked as expired.  The user will then be able to use the "Password Change" page in the application to change the "expired" password.

Step-by-step guide

Use the steps below to configure the password migration feature:

  1. Use System → Modules to enable the "Legacy Password Migration" module
  2. Use System → Configuration option and set:

    1. The "Enabled" checkbox 

    2. In Legacy SOAP Endpoint, enter end point URL of an instance of Classic USAS or USPS SOAP.  This will in the form: https://youritc.org/usassoap/services/USASWS

It's valid to use the USAS (or USPS) endpoint for both Redesign applications.  The module only uses the "login" operation of the service that is compatible with both Classic SOAP API's.

This module is not intended to remain active for extended periods. ITC's are encouraged to disable the configuration and un-install the module after all, or most, users have migrated to the new system.





  • No labels