Custom attribute

Lohr, Donald lohrda at
Thu Jun 11 23:05:13 UTC 2020

Our students have a student #, our employees have a employee # both are 
differently sequenced.  When the SP only supports one number in the 
assertion to match as the record key, we've chosen to source another 
sequenced unique # managed by IT that is added to each loginID we create 
in LDAP & AD.  This IT # number is also made available to our student 
system and employee system for when we externally feed data to an SP.  
Using something like the eduPersonTargetedID, which is sourced from 
inside of our Shibboleth code, would not work because it would not be 
available to an external data feed.

So yes, the IT unique #, is best described as a employee or student # 
for all tense and purposes.


On 6/11/20 5:38 PM, Peter Schober wrote:
> * Cantor, Scott <cantor.2 at> [2020-06-10 21:12]:
>> Though that's literally employeeNumber, I believe.
> It is.
> But from what the OP wrote:
> * Lohr, Donald <lohrda at> [2020-06-10 14:44]:
>> For a definition, it would be similar to a user's employee# and/or
>> student#.
> I somehow assumed he didn't employeeNumber (otherwise it would have
> been too obvious to just use employeeNumber, I guess)? Maybe I'm
> overcomplicating things.
> -peter

D o n a l d   L o h r
I n f o r m a t i o n   S y s t e m s
J a m e s   M a d i s o n   U n i v e r s i t y
5 4 0 . 5 6 8 . 3 7 3 0

More information about the users mailing list