Persistent Identity FAQs

Why are we implementing Persistent Identity?

Establishing a persistent user identifier allows the University to provide a username that does not change regardless of a change in the employee or student’s affiliation, role or name. This provides a permanent identifier that allows applications and resources to rely on a non-changing value to identify and assign access to users. In addition, by not performing renames it also allows for no employee downtime when a role or name change occurs during the rename and other application issues that occur after a rename.

 

What is a “hash ID”?

Beginning January1, 2019, all new employees will receive a “hash based” username, similar to what students receive today. This hash ID will not be changed and will remain regardless of any name or role changes. Instead, additional name-based email addresses will be allowed on the user’s mailbox.

 

What affects only new employees and not current employees?

New employees will get hash IDs, but existing employees (prior to January 1, 2019) will be grandfathered and will not be required to have their username changed to match the new standard.

 

Who can obtain a name-based email address (personalized email address).

Any active or new hire employee and any currently enrolled student may obtain a personalized email address. To obtain a personalized address go to accounts.umsystem.edu, login and choose “Personalize Email”. (Note: Students who have asserted FERPA will not be allowed to personalize their email address).

 

What is the expected behavior when you pick a personalized email?

The additional email address is set as the primary email address, so any outgoing mail will appear to come from the new address. The existing email addresses will remain active and continue to deliver mail to the existing mailbox.

 

Are there any adverse effects to choosing a personalized email?

Applications that use the primary email address as the identifier may experience issues when a primary email address changes, such as software licenses purchased via the Missouri.onthehub.com website. The email address on these end applications may need to be updated to the new primary email address.

 

How many personalized email addresses can I have?

A user may have one name-based email address. If a change in business units/campuses occur, the new campus domain will be available with the same name-based prefix, i.e. someone with first.last@umkc.edu becomes a MU employee, they can add first.last@missouri.edu.

 

Can I change my personalized address after I choose one?

Generally no, unless a legal name change has occurred. Once a legal name change has been updated in PeopleSoft HR or Student the individual may contact the Help Desk and they can allow an additional email address to be chosen based on the updated name.

 

Does the email address apply to the student email as well or can I assign an alias separately?

An employee who is also a student will have one mailbox, and one primary email address for that mailbox. Changing the alias will change your primary email address.



If I choose a personalized account- what do I use to log into applications?

In most cases you will login with either just your username, your domain and username or your User Principal Name (UPN), for example, username@umsystem.edu.



Application

Login Value

Applications behind Shibboleth

Username@umsystem.edu

Webmail

Username@umsystem.edu

VPN

Username@umsystem.edu

Desktops

Username OR domain and username



Does this apply to new hospital employees?

Persistent Identity does apply to employees on the UMHS-USERS domain.

 

How can I tell an employee from a student now?

Distributed IT staff should be able to lookup a user in AIMS and see the current employee and student status for an individual. AIMS has explicit employee and student status on the users’ dashboard page.

There are also new role-based attributes being populated into Active Directory with the intention of applications using these to make authorization decisions rather than relying on domain or OU location or SSO type.