In addition to user ID and password, customers typically have contact information that must be populated in the Address Book. When customers first log into FootPrints and Auto Add Customers is enabled, they are presented with a sign up form. This form differs depending on the authentication method and the Address Book type.
A New Users: Sign Up Here link appears on the FootPrints login page. The sign up form prompts the user to provide the following information:
NOTE
Password complexity rules are displayed on the sign-up page to assist customers.
After completing the form, the account is created and a contact record is also created for the customer in the Address Book. If a duplicate user account is found, the new account is not created and the user associated with the account receives an email with the password to log in. If there is no duplicate user account, but there already is a contact record found in the Address Book based on the primary key (because it was loaded via import), the account is created, and is associated with the existing contact record.
A New Users: Sign Up Here link appears on the FootPrints login page. The sign up form prompts the user to provide the following information:
No contact information needs to be entered because the Contact records are taken directly from the external contact database (i.e., Active Directory). The contact record is found based on the user ID entered (i.e., the primary key). If a duplicate user account is found, the new account is not created, and the user is prompted to enter another ID. If there is no duplicate user account but there is a duplicate contact found in the Address Book (based on the primary key), the account is created and is associated with the existing Contact record. An email with a random password is then sent to the customer. This ensures that only the real contact can claim an account with that primary key.
There is a New Users: Sign Up Here link on the FootPrints login page. When the link is clicked, the customer is prompted to enter a network ID and password. When the customer logs into FootPrints the first time with a network ID and password, the system searches the network password file for the user ID. If the user ID is not found, or the password entered is incorrect, the user receives an error message. If the ID and password are found, FootPrints searches the Address Book associated with auto-added customers for the user’s ID (in primary key field).
If the ID/primary key is found in the Address Book, the Homepage is displayed and the customer's contact information populates the Request form. If a contact record is not found, the user is prompted to enter contact information. After completing this form, the account is created, and the contact record is added to the Address Book.
Because of multiple authentication methods, the Auto Add page does more checking to determine whether single profile mode is available to it. If either or both authentication methods are LDAP, you can create multiple profiles. If you have currently selected a method other than LDAP and attempt to go into multiple profile mode, you are warned and, if you accept it, you automatically use LDAP authentication. Conversely, if you are in multiple profile mode and attempt to change to an authentication method that is not LDAP, you are warned and you lose any multiple profiles you have created as you return to single profile mode.
Auto add customers can use both configured techniques.
There is a New Users: Sign Up Here link on the FootPrints login page. When the link is clicked, the customer is prompted to enter a network ID and password. The customer enters a network ID and password and the Homepage is displayed. In this case, the customer does not have to fill in any forms at the first login to FootPrints. The contact information taken from the LDAP Address Book automatically populates the Request form. If either the ID is not found in the network password file or a contact record isn't found in the LDAP Address Book (based on the primary key), the user receives an error message.
Note
The primary key for the Address Book must match the network user ID. If the primary key is currently Email address and that field does not match the network user ID, an additional field should be created in the Address Book called User ID and this should be set as the primary key.