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 (config.enabled and product.enabled) in, as shown in Table 1.

Table 1. Push-to-client group support matrix for *.enabled
*.enabled value Function enabled Multiple groups supported
False No No
True Yes No
LDAP Yes Yes, based on membership of LDAP groups FEK.PTC.*.ENABLED.sysname.devgroup
SAF Yes Yes, based on permit to security profiles FEK.PTC.*.ENABLED.sysname.devgroup

Note that when the function is enabled (this includes the TRUE value), 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.

Table 2. Push-to-client group support matrix for reject.*.updates
reject.*.updates value Function enabled
False No
True Yes
LDAP Depends on LDAP group membership FEK.PTC.REJECT.*.UPDATES.sysname.**
SAF Depends on permit to security profile FEK.PTC.REJECT.*.UPDATES.sysname.**

Note that the directives in work 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), Host-based client control” in the Host Configuration Guide (SC27-8437) for more information about enabling multiple group support.