User Tools

Site Tools


middleware:deploy:ed:testing

Enterprise Directory Testing

Author Daniel Fisher
Date 2005/07/18

Introduction

This document lays out the procedure for testing the Enterprise Directory as fully as possible.
The system is far too complex to test every programmatic permutation in a reasonable amount of time.
However, we can exercise every component and come to a general conclusion as to the fitness of the system.

Testing of the Enterprise Directory is performed in our Pre-Production environment.
Since testers will be working with real person data every precaution must be taken to ensure the data remain private and confidential.
In order to begin testing Middleware must have authorized your PID to gain access to the necessary applications.

Overview

The following applications constitute the user facing portion of the Enterprise Directory:

Unless otherwise stated, after performing an operation in one of the previous applications the tester should confirm the change by checking the PeopleSearch application.
Direct access to our directories is only allowed via special request.

PeopleSearch

Procedures

You may use either the DSML or HTML search interfaces, their results are identical.

Fuzzy Logic Testing

  1. Login to the application using a PID
  2. Enter the telephone number of an unsuppressed person in any format (any combination of 4 to 10 digits is supported)
  3. Enter the first or last name of an unsuppressed person
  4. Enter the email address of an unsuppressed person
  5. Enter the first and last name of an unsuppressed person
  6. Enter the middle and last name of an unsuppressed person
  7. Enter a first or middle initial and last name of an unsuppressed person

Advanced Search Testing

  1. Login to the application using a PID
  2. Enter any valid ldap query, some examples include:
    • (uupid=PID)
    • (&(givenName=FIRSTNAME)(sn=LASTNAME))



Back to Overview

DAT

Description

The DAT is the main administrative application for data in the Registry.

Procedures

Person Testing

  1. Login to the application using a PID
  2. Select the Query a Person link
    1. Search for a person you know exists (and whose data you are willing to modify)
      • We do not recommend modify your own record, you may lock yourself out of the DAT
    2. Click on the person's UID
    3. Verify the user's information is displayed correctly (not that the actual data is correct)
  3. Select the PID Management link
    1. Enter a new PID to rename, verify the rename took place in peoplesearch
      • you may have to make several attempts to find an unused name
  4. Select the E-mail Management link
    1. Delete the E-mail account, verify email data has been removed in peoplesearch
  5. Select the PID Management link
    1. Enter the previous PID to rename, verify the rename took place in peoplesearch
  6. Select the E-mail Management link
    1. Create an E-mail account, verify email data has been added in peoplesearch
    2. Set and delete aliases
    3. Add and remove forwards
    4. Set various preferred email address
      • verify changes in either peoplesearch or User Information page for data not in EdLite
  7. Select the Account State Mgmt. link
    1. Verify you can authenticate with the PID you are modifying
    2. Change the account state to locked
    3. Attempt to authenticate again, you should get invalid credentials
    4. Change the account state back to active
    5. Attempt to authenticate again, you should succeed
  8. Select the Password Reset link
    1. Verify you can authenticate with the PID you are modifying
    2. Change the password
    3. Attempt to authenticate with the old password, you should get invalid credentials
    4. Attempt to authenticate again with the new password, you should succeed
    5. Change the password back to the original
    6. Attempt to authenticate again with the old password, you should succeed

Service Testing

requires a valid client certificate signed by the Middleware CA

  1. Login to the application using a PID
  2. Select the Create a Service link
    1. Upload a client certificate
    2. Enter a valid PID for the contact person
    3. Select any service type
    4. Set an expiration date in the future
    5. Add valid PIDs for administrators
    6. Select several viewable attributes
    7. Create the service
  3. Select the Query a Service link
    1. Search for the service you created
    2. Click on the service's SID
    3. Verify the service's information is displayed correctly
  4. Select the Account Info Mgmt. link
    1. Change the Account State to INACTIVE
    2. Change the Expiration Date
    3. Change the service type
  5. Select the Contact & Admins Mgmt. link
    1. Add a new Contact Person (expects a valid PID)
    2. Add a new Administrator (expects a valid PID)
    3. Delete an Administrator
  6. Select the Viewable Attributes Mgmt. link
    1. Add a new Viewable Attribute
  7. Select the Update Certificate link
    1. Upload a client certificate (can be the same certificate used to create the service)
  8. Select the Delete Service link
    1. Delete the service you created



Back to Overview

Pidgen

Description

Pidgen is the application that user's are forwarded to after verifying their identity via the mdsAuth application.

Procedures

Testing this application requires database access to the registry.

  1. Find a PIDM that does not have a PID associated with it.
    1. Run the following query against the registry:
      select vtpeople_seqno, vtuserid_seqno, userid from vtregistry.vtuserids where (userid_type_code = 'BP' and vtpeople_seqno not in (select vtpeople_seqno from vtregistry.vtuserids where userid_type_code = 'PID') and rownum <= 10);
    2. Select a PIDM from the result set to use for testing. The PIDM is listed in the USERID column. If possible, select a PIDM for an account with VT affiliations that allow the personal information to be viewed in the portal, such as VT-EMPLOYEE (VE). The VT affiliations for an account can be listed using the following query against the registry:
      select * from vtregistry.vtaffiliations where vtpeople_seqno=<VTPEOPLE_SEQNO for the PIDM selected>
  2. Access the PidGen servlet using the PIDM you just selected:
    https://webapp-pprd.middleware.iad.vt.edu/pidgen/PidGenServlet?pidm=<PIDM YOU SELECTED>
  3. Select a PID from the list or enter a custom PID
  4. Agree to the AUP
  5. Select a password
  • Note that this process uses sessions which can expire if any step takes too long. This may result in cryptic error messages or stack traces.



Back to Overview

VCOM-Pidgen

Description

VCOM-Pidgen is the application that VCOM user’s are forwarded to after verifying their identity via the mdsAuth application.

Procedures

Testing this application requires database access to the registry.

  1. Find a UID that does not have a PID associated with it and is a VCOM person.
    1. Run the following query against the registry:
      select distinct vtpeople_seqno from vtregistry.vtaffiliations where (affiliation_type_code like 'MS%' or affiliation_type_code = 'MF') and vtpeople_seqno not in (select vtpeople_seqno from vtregistry.vtuserids where userid_type_code = 'PID') and rownum <= 10
    2. Select a UID from the result set to use for testing.
  2. Access the PidGen servlet using the UID you just selected:
    https://webapp-pprd.middleware.iad.vt.edu/vcom-pidgen/PidGenServlet?uid=<UID YOU SELECTED>
  3. Select a PID from the list or enter a custom PID
  4. Agree to the AUP
  5. Select a password
  • Note that this process uses sessions which can expire if any step takes too long. This may result in cryptic error messages or stack traces.



Back to Overview

VCOM-Import

Description

VCOM Import is the web application that VCOM administration uses to manage VCOM user accounts in the VT ED Registry. It processes data in XML files to create new accounts, modify existing accounts, or remove existing accounts.

Procedures

Testing this application requires database access to the registry.

  1. Create an XML file containing the user account data to be processed. See sampleAddMod.xml and sampleRemoval.xml. You can place the data for more than one person in each file. Additions and modifications can be included in the same XML file. Modifications are full records, not just the modified fields. Removes must be placed in a separate XML file.
  2. Access the VCOM import application from your web browser
    https://webapp-pprd.middleware.iad.vt.edu/vcomImport
  3. Enter your VT pid and password and click the Log On button.
  4. Click the [Browse] button, browse to to the XML data file to be processed and select it.
  5. Bullet the appropriate action, either [Add or Modify People] or [Remove People].
  6. Click the Process File button.
  7. A summary of the actions taken will be displayed, showing the UID and name of records added, modified, or removed.
  8. Check the VT ED registry to verify that the correct changes were made. The tables that potentially change are
VTPEOPLE
VTPEOPLE_NAMES
VTAFFILIATIONS
VTADDRESSES
VTPHONE_NUMBERS

Sample XML for an add / modify

<?xml version="1.0" encoding="UTF-8"?>
<!--Sample XML file generated by XMLSPY v2004 rel. 2 U (http://www.xmlspy.com)-->
<people xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="Z:\Middleware Website\xsd\vcom-person-update.xsd">
        <person>
                <names>
                        <name suppressed="false">
                                <name-prefix>Mr.</name-prefix>
                                <first-name>Joe</first-name>
                                <middle-name>Q</middle-name>
                                <last-name>Blow</last-name>
                                <name-suffix>III</name-suffix>
                        </name>
                        <name suppressed="false">
                                <name-prefix>Dr.</name-prefix>
                                <first-name>Joseph</first-name>
                                <middle-name>Quinn</middle-name>
                                <last-name>Blow</last-name>
                                <name-suffix>III</name-suffix>
                                <preferred/>
                        </name>
                </names>
                <social-security-number>123456789</social-security-number>
                <gender>M</gender>
                <affiliations>
                        <affiliation>faculty</affiliation>
                </affiliations>
                <date-of-birth>1965-04-01</date-of-birth>
                <addresses>
                        <address suppressed="false">
                                <type>business</type>
                                <street1>2265 Kraft Drive</street1>
                                <mail-stop>VCOM</mail-stop>
                                <post-office-box>P. O. Box 1234</post-office-box>
                                <city>Blacksburg</city>
                                <state-or-province>VA</state-or-province>
                                <postal-code>24060</postal-code>
                                <country>US</country>
                                <telephone-number>5402314000</telephone-number>
                                <facsimilie-number>5402325000</facsimilie-number>
                        </address>
                        <address suppressed="false">
                                <type>home</type>
                                <street1>3607 Paul Street</street1>
                                <street2>Apt. C</street2>
                                <city>Alexandria</city>
                                <state-or-province>VA</state-or-province>
                                <postal-code>22311</postal-code>
                                <country>US</country>
                                <telephone-number>7038208436</telephone-number>
                        </address>
                        <address suppressed="false">
                                <type>local</type>
                                <street1>6 Laurel Drive</street1>
                                <city>Blacksburg</city>
                                <state-or-province>VA</state-or-province>
                                <postal-code>24060</postal-code>
                                <country>US</country>
                                <telephone-number>5409511234</telephone-number>
                        </address>
                </addresses>
        </person>
</people>

Sample XML for a remove

<?xml version="1.0" encoding="UTF-8"?>
<!--Sample XML file generated by XMLSPY v2004 rel. 2 U (http://www.xmlspy.com)-->
<people xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="Z:\Middleware Website\xsd\vcom-person-update.xsd">
        <person>
                <social-security-number>123456789</social-security-number>
        </person>
</people>



Back to Overview

DPID-IRM

Description

Dpid-IRM is a simple web application that allows IRM to perform basic operations on DPIDs.

Procedures

  1. Login to the application using a PID

Create DPID

  1. Click on the Create DPID button
  2. Enter a new DPID
  3. Enter a new Password
  4. Enter the Responsible UID for this DPID
  5. Check Create Mailbox
  6. Click on Create DPID
  7. Verify that the DPID you just created can login to the dpid-pub tool

Modify DPID

  1. Click on the Modify DPID button
  2. Enter the DPID you wish to modify
  3. Enter the fields you wish to change
  4. Click Modify DPID
  5. Verify on the next page or under View DPID that the proper data has changed

View DPID

  1. Click on the View DPID button
  2. Enter the DPID you wish to view
  3. Verify that all DPID data is correct



Back to Overview

DPID-Pub

Description

Dpid-Pub is a simple web application that allows DPIDs to perform basic operations on themselves. Operations include changing their password, managing email aliases, and managing email forwarding.

Procedures

  1. Login to the application using a DPID created with the DPID-IRM tool

Change your Password

  1. Click on the Change your Password link
  2. Enter the new password in the password input field(s)
  3. Click on Logout in the upper right-hand corner of the page
  4. Login to the application with the DPID and new password (note: It may take up to one minute for changes to replicate)

Manage your Email Aliases

Add an alias
  1. Click on the Manage your Email Aliases link
  2. Add a new email alias in the text input field
  3. Click on Add Alias
  4. Check to make sure the new alias shows up under Current Aliases
Delete Alias
  1. Create an alias if the DPID has no aliases
  2. Click the checkbox next to the alias you wish to delete
  3. Click Delete Alias
  4. Check to make sure the alias no longer shows up under Current Aliases

Manage your Email Forward

Start Forward (DPID has no forwarding addresses)
  1. Add the Forward Address into the text input field
  2. Click on Start Forward
  3. Check to make sure the forward shows up under Current Forward
Stop Forward (DPID has a forwarding address)
  1. Click on Stop Forward
  2. Check that no forwards are listed for the DPID



Back to Overview

Description

The IRM Payload Hijacking Application (PHA) is used to inspect and replicate records from Banner. It is useful to test replication from Banner to the Registry.

Procedure

  1. Login to the proper URL above. Note that you may need to contact Kevin Rooney for access.
  2. Enter the PIDM of the record you want to inspect.
  3. Inspect the Person XML, and, if wanted, click on Enqueue to Registry to put the record into the ED_VTPEOPLE_QUEUE.
middleware/deploy/ed/testing.txt · Last modified: 2015/06/01 12:02 (external edit)