# Why does Shibboleth sometimes return different names for students than class roster?

The legacy <span class="caps">UCLA</span> Single Sign On solution <span class="caps">ISIS</span>, now replaced by Shibboleth, used to prioritize data in payroll record from <span class="caps">QDB</span> over student record from <span class="caps">SRDB</span> if a student works at <span class="caps">UCLA</span> and their payroll record shows a different name. After the Enterprise Directory (ED) rolled out in production in November 2006, <span class="caps">ISIS</span> (now Shibboleth) switched its backend to ED which pulls a person’s name information based on a different logic. This ED name logic favors the name recorded in student system when different names are found in both student and payroll system for the same <span class="caps">UID</span>, if the person is a current student with <span class="caps">UCLA</span>. Therefore <span class="caps">ISIS</span> (now Shibboleth) no longer returns the name in payroll system as long as the person is a current student. The only case that payroll name is returned instead of student record name is that the person is a current <span class="caps">UCLA</span> employee but not a current <span class="caps">UCLA</span> student.

Exception: Students who have full-on <span class="caps">FERPA</span> restriction flag turned on in student system are not recognized in the Enterprise Directory because their information including names in student system are restricted for release. In such case, if they are <span class="caps">UCLA</span> employee at the same time, ED will recognize them as current <span class="caps">UCLA</span> employee but not current <span class="caps">UCLA</span> student, and thus return the names in payroll system.

---

Here’s the current name resolution logic implemented in ED:

a. If a person currently has student affiliation (meaning <span class="caps">UID</span> exists in V610), select the name in the order below no matter what other affiliation this person has:

1. SR0 name
2. SI0 name
3. PP0 name
4. <span class="caps">UNX</span> name

Note: If the name selected is found with APP\_USAGE\_STATUS &lt;&gt; ‘A’, an error message will be logged but the name still goes in ED.

b. Else, if a person currently has employee affiliation (meaning <span class="caps">UID</span> in payroll system with a emp\_status&lt;&gt; ‘S’ – ‘not seperated’), select the name in the order below:

1. PP0 name
2. SR0 name
3. SI0 name
4. <span class="caps">UNX</span> name

Note: If the name selected is found with APP\_USAGE\_STATUS &lt;&gt; ‘A’ an error message will be logged but the name still goes in ED.

c. Else, meaning a person does not have either student of employee affiliation, go with the same order of step a.