Configure uid as subjectIdentifier0

base/container_files/conf/subject.properties

@@ -8,6 +8,7 @@ subjectApi.source.ldap.param.Name_AttributeType.value = cn
 subjectApi.source.ldap.param.Description_AttributeType.value = description
 subjectApi.source.ldap.param.emailAttributeName.value = mail
 subjectApi.source.ldap.param.netId.value = uid
+subjectApi.source.ldap.param.subjectIdentifierAttribute0.value = uid
 subjectApi.source.ldap.numberOfAttributes = 9
 subjectApi.source.ldap.attribute.0.name = uid
 subjectApi.source.ldap.attribute.0.subjectIdentifier = true
@@ -95,12 +96,6 @@ subjectApi.source.ldap.param.subjectIdentifierToFindOnCheckConfig.value = dgilmo
 #subjectApi.source.example.param.statusTranslateUser0.value = active
 #subjectApi.source.example.param.statusTranslateDatastore0.value = A
 
-# subject identifier to store in grouper's member table.  this is used to increase speed of loader and perhaps for provisioning
-# you can have up to max 1 subject identifier
-# todo is this valid for GrouperLdapSourceAdapter2_5?
-#subjectApi.source.ldap.param.subjectIdentifierAttribute0.value = employeeNumber
-
-
 #searchSubjectByIdentifier: find a subject by identifier.  Identifier is anything that uniquely
 #  identifies the user, e.g. jsmith or jsmith@institution.edu.
 #  Subjects can have multiple identifiers.  Note: it is nice to have if identifiers are unique