Return to: U of M Home

Gold University of Minnesota M. Skip to main content.University of Minnesota. Home page.
 
Data Security

What's inside.

Access Request Form

Policies

Protect Your System Access

How to Keep Your Access Active

Functional IDs & Sponsored Internet Accounts

Systems List

Key Contact List

Data Custodian Sites

Training Sites

Reporting Sites

Additional Security Info.

OIT Helpline

Contact Us

 
 

Search Data Security

 
 

Data Security Home

 
 

Usage of Functional IDs/Accounts

Departments who determine that they have a need for a Functional ID/Account to access an Enterprise system (e.g., PeopleSoft) are expected to adhere to standards regarding the usage of their Functional IDs.

Important News - A new standard for Functional ID usage

Effective immediately OIT Data Security will be applying a new standard as new Functional IDs are requested. Anyone who will work for your department for more than 1 week must request access under their own X.500 ID (not an X.500 Sponsored Account). To get these employees into the X.500 your Department HR person would enter them into the HR system, which in turn generates the X.500 ID and EMPLID for the employee. This includes Adecco employees, Contractors and Student employees. Due to authentication restrictions, UM Reports remains the only Enterprise Application in which student employees will need a Functional ID to authenticate.

Questions regarding entering Adecco staff or contractors in the HR system should be directed to the: HRMS Helpline 5-2016

Some of the common uses of Functional IDs are:

  1. Access for Functional IDs can be restricted enabling the department to prevent access outside of normal business hours.
  2. Can be used by temporary employees (i.e., Adecco, contractors) who will work for your department for 1 week or less.
  3. Functional IDs are often used as "training IDs" by departments that train staff on how to use Enterprise Systems.

Standards Relating to Functional IDs:

  1. An X.500 Sponsored Account must be established and maintained for each Functional ID.
  2. Functional IDs must go through the standard Access Request form and authorization process.
  3. Data Custodians determine the type/level (view vs. update) to be associated with a Functional ID accessing their data.
  4. The Department must select a person who will be responsible for the Functional ID. This person signs as Requester on the Access Request Form.
  5. If the Functional ID is used by more than one person, the 'owner' or department person is responsible for maintaining the security of the password by either:
    • Log in/authenticating into the application with the ID/Password, or
    • Ensuring that the password for the Functional ID is changed whenever anyone who knows the password leaves your department.

How to Request an X.500 Sponsored Internet Account.

 
The University of Minnesota is an equal opportunity educator and employer.