Skip to Content.
Sympa Menu

comanage-dev - Re: [comanage-dev] Fwd: [JIRA] Work started: (CO-87) Affiliation model cleanup

Subject: COmanage Developers List

List archive

Re: [comanage-dev] Fwd: [JIRA] Work started: (CO-87) Affiliation model cleanup


Chronological Thread 
  • From: Benn Oshrin <>
  • To: comanage-dev <>
  • Subject: Re: [comanage-dev] Fwd: [JIRA] Work started: (CO-87) Affiliation model cleanup
  • Date: Thu, 24 Nov 2011 22:36:32 -0500

On 11/23/11 6:43 PM, Marie Huynh wrote:

I'm looking at this in cmp_enrollment_configurations_controller.php:

if(!defined_attribute($attrs, 'affiliation'))
{
$newattrs[]['CmpEnrollmentAttribute'] = array(
'cmp_enrollment_configuration_id' => $fid,
'attribute' => 'edu_person_affiliation',
'required' => RequiredEnum::Optional,
'ldap_name' => 'edu_person_affiliation',
'saml_name' => 'edu_person_affiliation'
);
}

Are all instances supposed to change to just "affiliation" too, or
does that string have other meanings in the code?

Well I suppose I should've just replied to this thread.

In this case, we probably want to keep 'ldap_name' and 'saml_name' as edu_person_affiliation, especially since these are defaults in those contexts (ie: LDAP eduperson schema and SAML) and we default to affiliation being populated with edu_person_affiliation values (so it's compliant with those contexts).

-Benn-



Archive powered by MHonArc 2.6.16.

Top of Page