Details
-
Bug
-
Resolution: Fixed
-
Blocker
-
COmanage Registry 3.3.0 (Magic Ring)
Description
When the CoPerson record is set to Suspended, the $provisioningData['CoGroupMember'] sent to the LDAP Provisioner does NOT include the UnixCluster group created for the CoPerson automatically by UnixCluster.
As such the LDAP Provisioner code
case 'gidNumber': |
case 'voPosixAccountGidNumber': |
// Find the Identifier of primary_co_group_id |
$gidIdentifier = Hash::extract($provisioningData['CoGroupMember'],'{n}.CoGroup[id='.$ua['UnixClusterAccount']['primary_co_group_id'].'].Identifier.{n[type='.$ua['UnixCluster']['gid_type'].']'); |
$attributes[$lsattr] = $gidIdentifier[0]['identifier']; |
break; |
|
|
cannot find the value for gidNumber and sends an empty value, but that is not allowed by the schema.