Duo Naming Conventions

When a system or application is registered with Duo at U-M, the system or application is given a name that displays to the users in the push notifications that are sent to the Duo Mobile App. For this reason, the name of an application needs to clearly identify the application to which the user is authenticating. Beginning July 20, 2016, the university will begin using Duo for two-factor authentication instead of MTokens.

This document describes the naming conventions to be used when setting up an application.

System Names

Example ITS SSH alethe.dsc.umich.edu

1. Active Directory Organization Prefix
2. Space or dash
3. Category, either SSH or RDP, or some other organizing category
4. Space or dash
5. Fully qualified distinguished name or group name
6. Space or dash
7. Append the word “Test” for applications in the University of Michigan Test sub-account, and remove it in the University of Michigan sub-account

Note Where it makes sense to name a system after an application, the naming convention for departmental applications can be followed.

Departmental Application Names

Example uuis-ssh-ubuntu

1. Active Directory Organization Prefix
2. Space or dash
3. Departmental name for the application (This is typically the user-facing application or service name.)
4. Space or dash
5. Append the word “Test” for applications in the University of Michigan Test sub-account, and remove it in the University of Michigan sub-account

Enterprise Application Names

Each enterprise application will be named on a case-by-case basis.

Examples

• Cosign is named U-M Weblogin.
• UMICH Account Management is named UMICH Account Management (adding the U-M is redundant in this case).
• The non-uniqname application is named UMICH Duo Active Directory Enrollment (adding the U-M is redundant in this case).

Append the word “Test” for applications in the University of Michigan Test sub-account, and remove it in the University of Michigan sub-account.