Support for multiple developer groups, each with their own client
configuration and client update requirements, is enabled by assigning
the desired value to the related directives (
pushtoclient.properties, as shown in Table 1.
|*.enabled value||Function enabled||Multiple groups supported|
|LDAP||Yes||Yes, based on membership of LDAP groups
|SAF||Yes||Yes, based on permit to security profiles
Note that when the function is enabled (this includes the
developers are always part of a default group. A developer can be
part of none, one, or multiple additional groups.
Rejecting the updates can also be made conditional, as shown in Table 2.
|reject.*.updates value||Function enabled|
|LDAP||Depends on LDAP group membership
|SAF||Depends on permit to security profile
Note that the directives in
independently from each other. You can assign any supported value
to any directive. There is no requirement to keep settings alike.
See LDAP-based group selection and SAF-based group selection for details about the required setup for the respective function. See “(Optional) pushtoclient.properties, Host-based client control” in the Host Configuration Guide (SC27-8437) for more information about enabling multiple group support.