Centrify® DirectControl® 5.1.2 Release Notes

© 2004-2013 Centrify Corporation.

This software is protected by international copyright laws.

All Rights Reserved.


Table of Contents

1.  About This Release. 3

2.  New Features. 3

2.1.  New Features in DirectControl 5.1.2. 3

DirectControl Agent 3

Centrify OpenSSH.. 6

Supported Platforms. 6

2.2.  New Features in DirectControl 5.1.1. 7

DirectControl Agent 7

DirectManage Access Manager 8

adedit 8

Centrify OpenSSH.. 8

Supported Platforms. 8

2.3.  New Features in DirectControl 5.1.0. 9

DirectControl Agent 9

DirectManage Access Manager 12

Migration. 12

adedit 13

Centrify LDAP Proxy. 13

Centrify OpenSSH.. 13

Supported Platforms. 14

2.4. New Features in DirectControl 5.0.5. 14

2.5. New Features in DirectControl 5.0.4. 14

2.6. New Features in DirectControl 5.0.3. 15

2.7. New Features in DirectControl 5.0.2. 15

2.8. New Features in DirectControl 5.0.1. 16

2.9. New Features in DirectControl 5.0.0. 17

3.   Bugs Fixed. 20

3.1.  Bugs Fixed in Centrify DirectControl 5.1.2. 20

DirectControl Agent 20

DirectManage Access Manager 22

Report Center 23

Zone Provisioning Agent 23

Centrify OpenSSH.. 23

3.2.  Bugs Fixed in Centrify DirectControl 5.1.1. 23

DirectControl Agent 23

DirectManage Access Manager 23

Centrify OpenSSH.. 24

3.3.  Bugs Fixed in Centrify DirectControl 5.1.0. 24

DirectControl Agent 24

DirectManage Access Manager 25

Zone Provisioning Agent 25

Centrify OpenSSH.. 26

3.4. Bugs Fixed in Centrify DirectControl 5.0.5. 26

3.5. Bugs Fixed in Centrify DirectControl 5.0.4. 26

3.6. Bugs Fixed in Centrify DirectControl 5.0.3. 26

3.7. Bugs Fixed in Centrify DirectControl 5.0.2. 26

3.8. Bugs Fixed in Centrify DirectControl 5.0.1. 27

4.   Known Issues. 28

DirectControl Agent 28

DirectAuthorize on Linux/UNIX.. 33

DirectControl Auto Zone mode. 35

Smart Card. 35

DirectManage Access Manager 38

Report Center 39

Zone Provisioning Agent 40

Zone Migration. 40

Group policies. 40

Centrify Network Information Service. 41

Centrify LDAP Proxy. 41

Centrify OpenSSH.. 41

Interoperability with Centrify Samba. 41

5. Additional Information and Support 42


1.  About This Release


Centrify Suite featuring DirectControl centralizes authentication and privileged user access across disparate systems and applications by extending Active Directory-based authentication, enabling use of Windows Group Policy and single sign-on. With Centrify Suite, enterprises can easily migrate and manage complex UNIX, Linux and Windows systems, rapidly consolidate identities into the directory, organize granular access and simplify administration. DirectControl, through Centrify's patented Zone technology, allows organizations to easily establish global UNIX identities, centrally manage exceptions on Legacy systems, separate identity from access management and delegate administration.  Centrify’s non-intrusive and organized approach to identity and access management results in stronger security, improved compliance and reduced operational costs.


An upgrade application note (/Documentation/centrify-upgrade-guide.pdf) is provided with this release to guide customers who have installed multiple Centrify packages. The document describes the correct order to perform updates such that all packages continue to perform correctly once upgraded. This document is also available in the Centrify Knowledge Base.


You can obtain information about previous releases from the Centrify Support Portal, in the Documentation & Application Notes page.


Centrify Suite is protected by U.S. Patents 7,591,005, 8,024,360, and 8,321,523.

2.  New Features

2.1.  New Features in DirectControl 5.1.2

DirectControl Agent




·        In-memory Kerberos credential cache (REF#: 27272, 45252)

- Prior to this release, DirectControl could only support file-based Kerberos credential cache. Now we have provided a more secure option to store Kerberos tickets in memory.

- A new setting, krb5.cache.type, is added to centrifydc.conf with the corresponding GP to allow administrators to configure to use this in-memory Kerberos credential cache.

- Centrify OpenSSH and Centrify Samba are also enhanced to make use of this new in-memory Kerberos credential cache.


·        In this release we have provided the following enhancements surrounding ‘dzdo’ feature (REF#: 51605)

- The ‘dzcheck’ validator script can be used to determine which role is used in the selected dzdo command.

-   An environmental variable DZDO_ROLE is set up for this purpose and a sample file /usr/share/centrifydc/dzcheck.sample is provided as a reference.

-   Some important security changes are made:

-   Since the dzcheck validator script is executed in the context of another user who may have more privileges, dzdo needs to ensure that dzcheck is trusted.  We now require dzcheck to be owned by root, and not group/world writable.  If dzcheck does not meet this requirement, it will not be executed.

-   To prevent malicious users from modifying any DirectControl configuration parameters and potentially compromising system integrity and security, the security settings of the following files must be owned by root and must NOT be writable by group or world:

a. /etc/centrifydc/centrifydc.conf

b. /etc/centrifyda/centrifyda.conf

c. All files referred by “file:<path>” in /etc/centrifydc.conf.

- The ‘dzdo –i’ command line option can be used to open a login shell other than the default login shell of the runas user. (REF#: 48298)

-   A new environment variable DZDO_LOGIN_SHELL is added to specify the shell to run when “dzdo –i” is used.

- An administrator can specify a list of directories where ‘dzdo’ searches for commands and scripts. An administrator can also specify a secure search path for use by ‘dzdo’ commands and scripts. (REF#: 48296)

-   Two new configuration parameters, ‘dzdo.search.path’ and ‘dzdo.secure.path’ are added to support this feature.

-   If you are using the secure_path parameter in the sudoers configuration file, you can achieve the same security level by setting both dzdo.search_path and dzdo.secure_path to the same value as secure_path setting in the sudoers file.

-   A new selection “System search path” option in the “Match path” attribute is added for this purpose in Access Manager when you define a command right.

-   You can also use adedit to set the path attribute of a command right to SYSTEMSEARCHPATH.

- If you use DirectAudit to audit the dzdo command and the users use “dzdo –i”, you need to create a command right definition for the DirectAudit shell and grant it to the roles that invoke “dzdo –i”.  If you are using DirectAudit 3.1.0 or earlier (Suite  2013.2 or earlier, please use “/da/cdashmod” as the command for the DirectAudit shell. From DirectAudit 3.1.1 (Suite 2013.3) onwards, please use “/bin/centrifyda” as the command for the DirectAudit shell. (REF#: 45346)



Smart Card


·        PKCS 11 support for RHEL (REF#: 51238)

- Apart from our default PKCS 11 module, you can now plug in 3rd party PKCS 11 modules through a new centrifydc.conf parameter and the corresponding GP.



Configuration Parameters

·        centrifydc.conf is updated:


-   New parameters:

-   adclient.cache.expires.group.membership: This parameter specifies cache timeout for the object membership information. If not specified the object expiration settings are used. (REF#: 22238)

-   adclient.excluded.domains: This parameter specifies a list of space-separated AD domain names in dotted format. Users can use this parameter to blacklist one or multiple domains. If the list is not empty, domains in this list will be excluded in the trusted domain map. Default is an empty list. (REF#: 41000)

-   adclient.included.domains: This parameter specifies a list of space-separated AD domain names in dotted format. If the list is not empty, only domains in this list (and the joined domain) will be included in the trusted domain map. Default is an empty list. (REF#: 41000)

-   adclient.krb5.conf.domain_realm.strict: This parameter controls whether adclient should remove any unknown hosts for the joined domain in the [default_realm] section of krb5.conf. Default is false. (REF#: 49897)

-   dzdo.search_path: This parameter defines a path used for every command run from dzdo, like 'secure_path' option in sudoers but used only in command searching. Default is not set. You can also use a file to specify path, and the lines in file shall contain only path values split by colons, for example:

dzdo.search_path: file:/etc/centrifydc/dzdo.search_path

(REF#: 48296)

-   dzdo.secure_path: This parameter defines a path used for every command run from dzdo, like 'secure_path' option in sudoers but used only in command executing. Default is not set. You can also use a file to specify path, and the lines in file shall contain only path values split by colons, for example:

dzdo.secure_path: file:/etc/centrifydc/dzdo.secure_path

(REF#: 47769, 51472)

-   dzdo.use.realpath: For some customers, when using dzdo to run commands, he/she may want dzdo to resolve the real path of the command before checked against authorization and run. This parameter is introduced for user to decide whether to use realpath(3) routine in dzdo to get the canonicalized path of the run command before checked against the DZ commands. Default is not used.

(REF#: 52662)

-   krb5.cache.type: This parameter defines the type of kerberos crendential cache adclient should create when AD user login. Valid value:

# FILE : create FILE based credential cache in /tmp when AD user login. Note: Mac OS only supports this type.

# KCM : create in-memory based credential cache. This requires KCM server to be running.

Default is FILE. (REF#: 27272)

-   rhel.smartcard.pkcs11.module: This parameter specifies which PKCS #11 module to be used for SmartCard support on RedHat. Default is /usr/$LIB/pkcs11/libcentrifypkcs11.so. $LIB variable is supported in specifying PKCS #11 module path. lib and lib64 will replace the value of $LIB for 32 and 64 bit system respectively. You must re-enable SmartCard support once you change this parameter.

To re-enable SmartCard support, please run the following command as root:

> /usr/bin/sctool -d && /usr/bin/sctool -e.

You might also want to refresh GNOME to reflect the change. You can run the following command as root to do so:

> /usr/sbin/gdm-safe-restart

(REF#: 51238)


-   Obsoleted parameters:

-   log.audit: This parameter has not been used and hence is now removed. (REF#: 50751)

-   log.client: This parameter has not been used and hence is now removed. (REF#: 50751)


Please refer to Configuration Parameters Reference Guide for details.


Centrify OpenSSH


·        Upgraded to OpenSSH 6.2p2 (REF: 40359, 51889)

Centrify OpenSSH 5.1.2 is now based on OpenSSH 6.2p2 and hence may support more configuration parameters. By this upgrade, Centrify OpenSSH 5.1.2 only works with Centrify DirectControl 5.1.2 or later.


Supported Platforms


·        Support is removed for the following operating systems:

- Mac OX X 10.6 version

- This release does not support Mac OSX as we are planning a separate release to coincide with the OSX 10.9 release.


·        Refer to http://www.centrify.com/products/all-supported-platforms.asp for the complete list.


2.2.  New Features in DirectControl 5.1.1

DirectControl Agent




·        Audit Trail

Audit Trail is enhanced to track security-related operations in DirectControl Agent and DirectManage Access Manager.


Smart Card


·        Name mapping smart card (a.k.a alternate identity smart card)

Centrify DirectControl agent is enhanced to support login via name mapping smart cards on both Mac and RedHat platforms. This feature is disabled by default and must be enabled manually as follows:

·        Edit /etc/centrifydc/centrifydc.conf and set the following configuration parameter to true:

o   smartcard.name.mapping: true

·        Restart the DirectControl agent:

o   /usr/share/centrifydc/bin/centrifydc restart

·        Note the following sequence during login process:

o   At system startup, user is prompted for smart card insertion

o   Upon card insertion, user is prompted for PIN

o   At this point, user is prompted for user name. User must specify which user account to authenticate with.


DirectControl for Mac


·        DirectControl for Mac OS X has been updated to version 5.1.1. Please see the Centrify DirectControl for Mac OS X release notes in the Documentation directory for more information.


Configuration Parameters

·        centrifydc.conf is updated:


-   New parameters:

-   adclient.altupn.update.interval: This parameter tells the DirectControl Agent to update the list of alternate UPN suffixes at a given interval. The default is 1800 seconds.

-   adclient.cache.flush.interval.dz: This parameter configures the frequency (in seconds) for the DirectControl Agent to flush its DirectAuthorize (DZ) cache. This parameter forces periodic DZ cache updates (not the DC cache). The default '0' means no periodic DZ cache update (to match existing behavior).

-   dzdo.set.runas.explicit: This parameter configures whether it is required to specify the runas user in dzdo use. The default is true.

-   smartcard.name.mapping: This parameter allows non-root user to be able to see the Alternate Security Identity field in Active Directory objects. The ‘name mappings for smartcard’ feature uses this field to identify which cards can login to which Active Directory user.


-   Modified parameters:

-   adclient.server.try.max: The default is changed from 3 to 0. Note: this parameter was deprecated since 4.4.3 and resurrected in 5.1.0.


Please refer to Configuration Parameters Reference Guide for details.


DirectManage Access Manager


·        Sudoers Import

Sudoers Import now supports GID in user list and runas list (REF#: 37923)


·        Audit Trail

Audit Trail is enhanced to track administrative operations related to Centrify objects, such as creation and deletion of zones, definition of user and group profiles, and roles and rights definition and assignment.




·        adedit sample scripts are enhanced:

-   addbloader is enhanced to better support the effective user rights and special user/group types: All AD Users, All Local Unix Users and All Local Unix Groups, in UNIX environment. Note: Classic zones are not supported.

-   adreport is enhanced to work with the new addbloader to report the effective user rights and special user/group types: All AD Users, All Local Unix Users and All Local Unix Groups, in UNIX environment.


Centrify OpenSSH


·        When Centrify-openssh is installed, it will check whether the computer already has an ssh. If an ssh is found, Centrify-openssh will automatically adopt the Port and AuthorizedKeysFile settings in the sshd_config. (REF: 39835)


Supported Platforms


·        Support is added for the following operating systems:

-   Red Hat Enterprise Linux 5.9, 6.4 (32-bit and 64-bit)

-   Oracle Linux 5.9, 6.4 (32-bit and 64-bit)

-   CentOS 5.9, 6.4 (32-bit and 64-bit)

-   Scientific Linux 5.9, 6.4 (32-bit and 64-bit)

-   Fedora 18, 19 (32-bit and 64-bit)

-   OpenSuSE 12.3 (32-bit and 64-bit)

-   Ubuntu 13.04 (32-bit and 64-bit)

-   Debian 7 (32-bit and 64-bit)

-   Mint LMDE 201303 (32-bit and 64-bit)

-   Mint 15 (32-bit and 64-bit)

- Solaris 11.1 (x86_64 and SPARC)


·        Support is removed for the following operating systems:

- Ubuntu 8.04LTS

- Microsoft Windows Vista


·        This is the last release for the support of the following operating systems:

- Mac OX X 10.6 version


·        Refer to http://www.centrify.com/products/all-supported-platforms.asp for the complete list.


2.3.  New Features in DirectControl 5.1.0

DirectControl Agent


·        Read-only Domain Controller (RODC) is supported

RODC is supported in DMZ. RODC can also be in the same forest with writeable domain controller. Refer to Administrator's Guide for UNIX for details.


·        adnisd supports multiple domains in hierarchical zones

In this release of the Centrify NIS server, the NIS maps can be distributed into different domain controllers in hierarchical zones.


·        0.9.8w OpenSSL

DirectControl is integrated with 0.9.8w OpenSSL.



Auto Zone

·        Configure Auto Zone to limit access

You can set configuration parameters or group policies to specify a subset of Active Directory users and groups that have access to computers joined through Auto Zone. Refer to Administrator's Guide for UNIX for details.


·        Substitute UID with employee number or employee ID in Auto Zone

Zone Provisioning Agent allows using employee number or employee ID as the UID in the user's UNIX profile.




·        Role based Audit rights

There are predefined audit rights that are built into every role definition. They specify whether and under what conditions a user must be audited in order to login. This feature is only available in hierarchical zones.


New pre-defined role definitions:

-   always permit login: users in this role are allowed to login even if auditing is required but not available.

-   scp: Predefined system role for granting scp access without explicit SSH login.

-   sftp: Predefined system role for granting sftp access without explicit SSH login.

-   UNIX login: Predefined system role that grants typical UNIX user login rights. It is called “login” role in previous releases.

-   Windows login: Predefined system role that grants typical Windows user login rights including console and remote login.

-   winscp: Predefined system role for granting winscp access.


The pre-defined role definitions are not created for the zones that exist before DirectControl is upgraded. You can use “Generated pre-defined roles” context menu to create those roles.


See the Administrator's Guide for UNIX for details.


·        Audit Trail

Authentication and authorization granted and denied messages are written in the syslog file. The audit trail messages are identified by the AUDIT_TRAIL token in the message.


DirectControl Agent Commands

·        CLI is updated


-   adjoin

- New --dnsname (-D): This is an optional parameter to override the dNSHostName attribute in the computer object.

-   addns:

- New –list (-L): lists DNS record details

- New –refresh (-r): update unchanged records to refresh TTL

-   dzdo

-     dzdo is enhanced to support local users and local groups.

-     dzdo is enhanced to execute a command on a remote machine via SSH connection.

See the Administrator’s Guide for UNIX for details.


-   dzinfo

- New --computer-role (-C): show the computer role

- New –format (-f): produces scriptable output



Configuration Parameters

·        centrifydc.conf is updated:


-   New parameters:

-   auto.schema.allow.users: Users allowed in this Auto Zone.auto.schema.allow.groups: Users who are members of the groups specified in here are allowed in this Auto Zone.

-   auto.schema.groups: Groups allowed in this Auto Zone.

-   auto.schema.max.unix.name.length: Maximum Auto Zone length

-   auto.schema.override.uid: Specify which Active Directory user attribute to use to generate the UID.

-   auto.schema.substitute.chars: The character is used to substitute invalid characters.

-   auto.schema.unix.name.disallow.chars: Characters not allowed in Auto Zone name.

-   adclient.binding.refresh.force: Indicate whether we force to re-establish LDAP bindings regardless the current binding is closest site or not.

-   adclient.dzdo.clear.passwd.timestamp: Set to true will remove the tickets after logout. Default is false.

-   adclient.sudo.clear.passwd.timestamp: Set to true will remove the tickets after logout. Default is false.

-   adclient.sudo.timestampdir: The directory where sudo stores timestamp files.

-   adclient.update.os.interval: How often adclient should wait before attempting to update the OS information in the case where adclient starts up in disconnected mode. Default is 30 seconds.

-   dc.penalty.time: controls how long a domain controller that has failed is considered less preferable to the other domain controllers in the forest.

-   dzsh.roleswitch.silent: Set to true to not output the role switch info in dzsh use. Default is false.

-   dzdo.passprompt: The password prompt format when the target user's password is needed. Default is "[dzdo] password for %p:".

-   pam.setcred.respect.sufficient: set to true if pam_setcred calls the remaining modules even the 'sufficient' is fulfilled.  DirectControl will set the value according to the target platform.


-   Modified parameters:

-   adclient.cache.expires: Default is changed from 3600 to 600 seconds.

-   adclient.cache.expires.gc: Default is changed from 3600 to 600 seconds.

-   adclient.cache.expires.group: Default is changed from 3600 to 600 seconds.

-   adclient.cache.expires.user: Default is changed from 3600 to 600 seconds.

-   adclient.cache.expires.user.membership: Default is changed from 3600 to 600 seconds.

-   nss.program.ignore: added unix_chkpw


Refer to Configuration Parameters Reference Guide for details.


DirectManage Access Manager


·        DirectManage Access Manager

DirectManage Access Manager is the new name for DirectControl Administrator Console.


·        License report in Report Center is replaced by the Deployment Report. There is a start menu item to open the Deployment Report.


·        Windows access and auditing

Centrify Windows agents provide role-based access control, privilege management and auditing on Windows computers.   For details, please refer to Administrator's Guide for Windows.


·        Migrate from sudo to dzdo

A wizard is provided in DirectManage Access Manager to migrate privilege management of UNIX computers from sudoers to Active Directory via the Centrify Suite DirectAuthorize features. It is recommended to import the UNIX users and groups and create the computer roles before importing the sudoers file. Refer to Administrator's Guide for UNIX for details.


·        Import users and groups from Deployment Manager database

The import users and groups wizard in DirectManage Access Manager is enhanced to retrieve the users and groups’ data from the Deployment Manager database.


·        Forest Analysis in DirectManage Access Manager is enhanced to check for:

-   expired profiles storing SID in sidHistory

-   profiles schema for cross forest users

-   orphan role assignment




·        Migrate Classic Zone to Hierarchical Zone

The admigrate script migrates users, groups, roles and rights in a classic zone to a hierarchical zone.  Refer to its manpage for usage.


·        Move Computer to Hierarchical Zone

The adchzone script moves a zone computer object from classic to hierarchical zone in the same domain.  Refer to its manpage for usage.


·        Upgrading DirectControl cache

When DirectControl is upgraded from 5.0.x, its cache is also upgraded.  It does not support cache upgrade from 4.x. The 4.x cache will be deleted when upgrade is performed. Upgrade is not performed if the cache is encrypted.




·        adedit is enhanced

-   get_all_zone_users: gets all zone users along the hierarchical path.

-   get_user_groups: gets the groups that the user belongs to.

-   get_zone_user_field, get_zone_group_field, get_zone_computer_filed: add dn option to locate AD object.

-   dn_to_principal, get_group_members, get_role_assignments, get_zone_users, joined_name_to_principal, list_role_assignments, list_zone_user, principal_from_sid: add upn option to display UPN name.

-   move_object: moves the selected object to the specified location in the same domain.

-   rename_object: renames the common name of the selected object.


·        New adedit sample scripts

-   addbloader is enhanced to support the new sysRights and roles in DirectControl and Windows Agent.  When you use adedit to modify the sysRights, you must use bit operators to make the change.  Otherwise, the Windows Agent sysRights will be reset.

-   adreport is enhanced to report command rights.

-   adzonediff is new in this release.  It compares the roles and rights between two zones. Refer to its command help for usage.

-   More adedit sample scripts can be found under /usr/share/centrifydc/samples/adedit directory.  See the UNIX and Linux Evaluation Guide for details.


Centrify LDAP Proxy


·        DirectControl LDAP Proxy supports global catalog search

In addition to searching through the domain controller, LDAP Proxy also supports global catalog search by adding "CN=$" in front of the search base. The global catalog search is useful in a multi-domain forest environment.


Centrify OpenSSH


·        Centrify 5.1.0 OpenSSH

Centrify DirectControl includes Centrify 5.1.0 OpenSSH, which is based on 6.0p1 OpenSSH in this release. Refer to Administrator Guide for UNIX.    


·        New UNIX Rights Definition


-   SSH Rights

New predefined SSH rights identify specific SSH services that a user who is enabled for PAM SSH access can run. The SSH rights will be generated after upgrade DirectControl console is upgraded. Refer to Administrator's Guide for UNIX for details.


Supported Platforms


·        Support is added for the following new operating systems:

-   Centos 6.4 (32-bit and 64-bit)

-   Scientific Linux 6.4 (32-bit and 64-bit)

-   Red Hat Enterprise Linux 6.4 (32-bit and 64-bit)

-   Red Hat Enterprise Linux 5.8 PPC (64-bit)

-   Red Hat Enterprise Linux 5.8 Itanium (64-bit)

-   Linux Mint Debian Edition (32-bit and 64-bit)

-   OpenSuSE 12.2 (32-bit and 64-bit)


·        Refer to http://www.centrify.com/products/all-supported-platforms.asp for the complete list.


2.4. New Features in DirectControl 5.0.5


-   Support is added for the following operating systems:

-   Red Hat Enterprise Linux 6.3 (32-bit and 64-bit)

-   Red Hat Enterprise Linux Desktop 6.3 (32-bit and 64-bit)

-   CentOS 5.8, 6.3 (32-bit and 64-bit)

-   Scientific Linux 5.8, 6.3 (32-bit and 64-bit)

-   Oracle Linux 6.3 (32-bit and 64-bit)

-   Ubuntu Desktop 12.10 (32-bit and 64-bit)

-   Ubuntu Server 12.10 (32-bit and 64-bit)

-   Linux Mint 13, 14 (32-bit and 64-bit)


Only x86 and x86-64 Red Hat packages are updated in this release.  The Debian packages in Suite 2012.2 are verified to work with Ubuntu 12.10 and Linux Mint 13 and 14.


All other packages are identical to DirectControl 5.0.4.

2.5. New Features in DirectControl 5.0.4


·        In this release, the following platforms support SmartCard login:

- Red Hat Enterprise Desktop 5.x and 6.x (32-bit and 64-bit)


·        The following smart cards are supported:

- Gemalto SC 64k 1.2 – CAC

- Oberthur One 5.2 – PIV

- Oberthur 128 v5.5 DI – CAC

- Gemalto 144 TOPDL DI – CAC

- Oberthur ID One 5.2 Dual – CAC

- Gemalto 72k DI - CAC


·        SmartCard login is supported on GNOME only.


·        New group policies are added to support smart cards. Refer to Group Policy Guide for details.


·        Only Red Hat packages are updated in this release. All other platforms are identical to DirectControl 5.0.3.  

2.6. New Features in DirectControl 5.0.3


·        DirectControl for Mac OS X


DirectControl for Mac OS X has been updated to version 5.0.3. See the Centrify DirectControl for Mac OS X release notes in the Documentation directory for more information.


Support has been added for Mac OS X 10.8.


·        Centrify 4.5.4 OpenSSH


OpenSSL is upgraded from 0.9.8k to 0.9.8w, which is statically linked. It fixes several security vulnerabilities since 0.9.8k. Refer to the openssl release notes for details.


·        All other packages are identical to DirectControl 5.0.2.

2.7. New Features in DirectControl 5.0.2


·        FIPS 140-2

Red Hat Enterprise Linux Server and Mac OS X support FIPS 140-2 standard.


·        DirectControl in FIPS mode

DirectControl in FIPS mode is integrated with 0.9.8s OpenSSL.


·        Centrify 4.5.3 OpenSSH

Centrify DirectControl includes Centrify 4.5.3 OpenSSH, which is based on 5.9p1 OpenSSH in this release. Refer to Centrify 4.5.3 OpenSSH release notes for details.


·        Centrify 4.5.3 Samba

Centrify 4.5.3 Samba is based on 3.5.11 Open Samba code. Centrify 4.5.3 Samba can be downloaded from Centrify web site. Previous Centrify Samba does not work with Centrify DirectControl in this release.


·        SQLite

DirectControl does not provide SQLite shared library in its package that avoids conflict with the SQLite shared library used by other applications.


·        Support is added for the following new operating systems:

- Red Hat Enterprise Linux 5.8, 6.2 (32-bit and 64-bit)

- Red Hat Enterprise Linux Desktop 5.8, 6.2 (32-bit and 64-bit)

- Scientific Linux 5.7 (32-bit and 64-bit)

- Fedora 17 (32-bit and 64-bit)

- CentOS 5.7, 6.1, 6.2 (32-bit and 64-bit)

- Mandriva Enterprise Server 5 (32-bit and 64- bit)

- VMWare VIMA vsphere 5

- Linux Mint 12 (32-bit and 64- bit)

- Solaris 11 (x86_64 and SPARC)


·        Support is removed for the following new operating systems:

- All OpenSolaris versions

- AIX 5.1, 5.2

- VMware ESX 3.0.1, 3.0.2

- Fedora 13 and below (32-bit and 64-bit)

- Ubuntu 6.06, 8.10, 9.04, 9.10 (32 and 64 bit)

- Mac OS X 10.5 

2.8. New Features in DirectControl 5.0.1


·        Express mode

- Express mode is now supported and HPUX 11.31 and AIX 7.1 are added to the platform support list for Express.


·        DirectControl for Mac OS X

- DirectControl 5.0.1 is the first release on the Macintosh platform that provides support for Next Generation Zones.

- Support for OS X 10.7.x, including support for Apple's FileVault full disk encryption and Microsoft's Distributed File System (DFS) capabilities.

- Automated Certificate Enrollment for 802.1x and VPN services

- Improved support for Printer Management on the Mac using _lpadmin and _lpoperator printer groups on the local mac

- Simplified Group Policies for automatically mounted fileservers and home directories.

- Smart Card support for 10.6 and 10.7 for all CAC, CACNG, and PIV cards, including the Oberthur ID One 128 v 5.5 Dual Smart Card.

- New OCSP Enhancements and GUI for SmartCard configuration


·        User password expiration

- Fine-grained password policy is queried to determine user password expiration.


·        DirectControl MMC Snapin

- Now implemented in user mode rather than in author mode in order to co-exist better with group policies.


·        Support is added for the following new operating systems:

- Citrix XenServer 6.0

- Fedora 16 (32-bit and 64-bit)

- OpenSuSE 12.1 (32-bit and 64-bit)

- Ubuntu 11.10 Desktop (32 and 64 bit)

- Ubuntu 11.10 Server (32 and 64 bit)

- Solaris 11 Express 2010.11 (x86_64 and SPARC)

2.9. New Features in DirectControl 5.0.0


·        Hierarchical zoning


·        NIS map support added to NSS

The following NIS maps are supported:

- networks

- rpc

- auth_attr

- prof_attr

- user_attr

- exec_attr

- auuser

- protocols

- networks

- bootparams

- netmasks

- netgroup

- hosts

- printers

- project

- services

- ethers

- aliases

- ipnodes



·        Centrify Zone Provisioning Agent

Zone Provisioning Agent (ZPA) is now included with DirectControl. It has been updated to support hierarchical zoning, new in DirectControl 5.0.0.


·        Group Policies


1.  New group policy: Enable Auto Zone user home directory. This group policy adds the auto.schema.use.adhomedir property to /etc/centrifydc/centrifydc.conf.


2.  adm files are now shipped for Centrify group policies as well as xml.


·        Configuration parameters


1.  New configuration parameter: krb5.cache.clean.exclusion


This parameter defines an exclusion list for when adclient cleans users' cache files. For users in this list, adclient will not clean their krb5cc_* file. UNIX names of AD users should be used. The default value is empty.


2.  New configuration parameter: adclient.krb5.use.addresses


This parameter controls the MIT Kerberos HostAddresses option. If the parameter is set to true, adclient will add "noaddresses = false" to krb5.conf. The parameter is set to false by default.


3.  New configuration parameter: adclient.altupns


This parameter tells adclient to allow an otherwise unknown Kerberos realm as UPN suffix. The default is unconfigured. For example, to allow "mil" as a UPN suffix:


adclient.altupns: mil


·        New CLI features


- adcheck


adcheck now does a DNS TCP port check as well as a UDP port check in the "net" set of checks.


New --tmp_path (-m) parameter to use the given path for temporary files during check. If not specified the default is /tmp.   


- adfixid


- New --undo (-U) parameter to back out changes made since the last change marker. The log for undo is accumulated in




- adinfo


- New --debugcache command line parameter added to tar up /var/centrifydc cache files.


- -y parameter now accepts parameters. "config" dumps all property values, "dns" dumps the dns cache and "all" dumps all system information.


- --support parameter now includes contents of /etc/irs.conf, /etc/netsvc.conf and shows the ldd output for /usr/lib/netsvc/dynload/nss_cdc.so.


- New -G option to report the current GC.


- adjoin


- New --upn (-U) paramter for adjoin sets user's upn.


- adquery


- New parameter --attribute mail (-b mail) to return the email address of a user. Note that this can only be

        used users, it does not work for groups.


- adupdate


- New --principal (-P) parameter for adupdate user allows setting of user's upn.


- New --foreign-sid (-i) parameter allows setting / retrieving of a sid for a foreign user.


- Adupdate now allows changes to users from one-way trusted forests. To use it, retrieve the SID for the user to be changed via adquery user's -Z option, thenuse that SID in adupdate using the --foreign-sid option.


- New --userWorkstations (-W) option for adquery user shows the user's userWorkstations attribute. The -all (-A) option has been extended to include this attribute too.


·        Windows Console


An option has been added to the import Wizard to add a prefix or suffix to the name of a group or user, allowing name clashes to be avoided with already existing users and groups.


·        New DirectAuthorize reports


Two new reports have been added to report on user roles and rights grouped by zone. The new reports are:


- User Role Assignments Grouped by Zone

- User Privileged Command Rights Grouped by Zone


·        The DirectControl NIS server (adnisd) now derives the mail.byaddr map.


·        Reworked DirectAuthorize to integrate it with hierarchical zones.


·        Can now call a script every time a dzdo command is executed, allows addition of per-command logging or change ticket entry every time a privileged command is executed.


·        Centrify Putty "Auto-login username" group policy is default to "User principal name (require DirectControl)".


·        Support is added for the following operating systems:

- CentOS 4.9, 5.6, 6.0 (32-bit and 64-bit)

- Debian 6 (32-bit and 64-bit)

- Fedora 15 (32-bit and 64-bit)

- Mandriva 2011 One

- Oracle Linux 6 (32-bit and 64-bit)

- Red Hat Enterprise Linux 5.7, 6.1 (32-bit and 64-bit)

- Red Hat Enterprise Linux Desktop 5.7, 6.1 (32-bit and 64-bit)

- Scientific Linux 4.9, 5.6, 6.1 (32-bit and 64-bit)

- Ubuntu Desktop 11.04 (32-bit and 64-bit)

- Ubuntu Server 11.04 (32-bit and 64-bit)

3.   Bugs Fixed

3.1.  Bugs Fixed in Centrify DirectControl 5.1.2

DirectControl Agent


·       When running selinux in enforced mode we find that the executable map adauto.pl was blocked by selinux. This is fixed. (REF#: 37027)


·       We do not support a scenario that a zone is in one forest while a machine is joined to another forest. However, adjoin did not stop users doing it. This is fixed such that adjoin will reject such request. (REF#: 41017)


·       adjoin self-serve failed for precreated computer with hostname (samAccountName) > 14 chars if the domain name was entered in upper case. This is fixed such that adjoin will accept both upper case and lower case domain names. (REF#: 44297)


·       An AD user was incorrectly allowed to ssh into a machine that was not zone enabled. This problem only occurs if the machine has local user that matches the AD user that is logging in. This is fixed. (REF#: 45175)


·       When a computer was removed from a computer role group it did not correctly get updated on Linux. This is fixed. (REF#: 45632)


·       User cannot login with mixed case (REF#: 45965)


When users have set auto.schema.name.lower: true, all authentications will use lower case names for verification. However, previously some kerberized applications were still using case-sensitive verification with credentials. This is fixed.


·       autozone users failed to login in offline mode after a while (when the password cache, controlled by adclient.cache.expire, expired). This is fixed by keeping the cache live while in offline mode.  (REF#: 47494)


·       On AIX, if a member list in /etc/group is longer than 1000 characters, the system would not recognize the group membership after joining a domain, e.g. run “id user1” could not show all secondary groups of user1. This is fixed. Note: With the fix, you need to run adreload after you make changes to /etc/group. Otherwise the change won't take effect. (REF#: 48160)


·       Installation flags are relocated. (REF#: 48407)


With Installation script now uses /var/centrifydc/tmp, instead of /var/tmp, to hold installation directives, such as CENTRIFY_FORCE_DISCONNECTED_UPGRADE to force upgrade in disconnected mode. This is a change of behavior.


·       Added security check in configuration file access, e.g. file referenced by centrifydc.conf, or other, such as group.ovr, user.ignore, etc. (REF#: 48413, 53583)


When Centrify software tries to access a parameter in a user-defined configuration file (e.g. file reference in centrifydc.conf), the file referenced has to be owned by root and not world writable or otherwise it is ignored. If this happens, you may see warning messages in centrifydc.log like these:

-   Config file [<file name>] is not owned by root. Skip reading config file for property <property name>. Please change its owner to root to enhance security.

-   Config file [/tmp/allow.txt] is world writable. Skip reading config file for property adclient.prevalidate.allow.users. Please ensure the file is not world writable to enhance security.


Note: the default root umask on some HPUX is 0 which results in files created by root being world writable and hence being ignored if they are used in centrifydc.conf. The system will not work properly until you fix the file permission. It is recommended to change the default root umask to 022.


This is a security enhancement but also a change of behavior.


·       non-unique kerberos credential cache was removed prematurely. (REF#: 48286)


With centrifydc.conf parameter krb5.unique.cache.files: false, non-unique Kerberos credential cache should be shared by multiple concurrent sessions. However, it was incorrectly removed while one or more user sessions are still in open state. This is fixed.


·       Using auto.schema.allow.groups in centrifydc.conf to allow AD groups access to a machine did not work reliably. Sometimes users had to run ‘adquery group’ command to trigger the update of group information. This is fixed. (REF#: 48557, 51428)


·       In DirectControl version 5.1.0, the preferred site was incorrectly converted to lower case reported by adinfo. The impact could be that, e.g. DirectAudit installed on the same machine failed to find a valid Collector by referring site information because of the site name was not the same any more. This is fixed. (REF#: 48836)


·       adclient failed to remove decommissioned domain controllers from krb5.conf. (REF#: 49897)


adclient by default will update the Kerberos configuration file, krb5.conf, with new domain information. However, it will not remove lines that it does not know about because the file may contain some other information, such as target hosts, etc. In this release, we provide a new switch, adclient.krb5.conf.domain_realm.strict, in centrifydc.conf for users to decide if we should remove any unknown hosts for [default_realm] section of the joined domain or not.


·       Upgrade from 5.0.x to 5.1.0 or above failed to upgrade the authorization cache resulting in some users might not be recognized. This is fixed. (REF#: 50476)


·        Force enable smartcard support for RHEL (REF#: 51229)

- Enabling smart card support via Group Policy or 'sctool' utility will automatically turn on RHEL's 'Smartcard Authentication' option. Previously it did not.


·       adkeytab now disallows -m with the -r (--reset) option because this is not a valid combination. (REF#: 43682)


·       If dzcheck is executed by dzdo under the context of the runas user, so it can be executed by root.  As a security enhancement, before dzcheck is executed, dzdo will check if dzcheck is owned by root and not group/world writable.  It should not execute dzcheck if it is not trusted. A DEBUG log message, “Dzdo Validator: /usr/share/centrifydc/sbin/dzcheck does not exist or not executable or cannot be trusted.”, can verify this condition. If this happens, you may need to correct the file permission and ownership of dzcheck. (REF#: 50088)


·       If dzdo.search_path was set to path ending with “/”, e.g. “/usr/bin/” instead of “/usr/bin”, the path matching would fail. This is fixed. (REF#: 52662)


DirectManage Access Manager


·       ‘Show effective users’ failed to show any users if an AD group had a contact as one of its members. This is fixed such that the contact will be ignored. (REF#: 43912)


·       Precreating a computer account with hostname > 15 characters might result in a computer object with CN up to 19 characters but the samAccountName was truncated to 15 characters, resulting in failure of subsequent adjoin. This is fixed in DirectManage Access Manager. When users precreate a computer with hostname > 15 characters, the following warning will be shown to alert users: (REF#: 44349)


The computer name exceeds 15 characters. Please note that:

-   This will break the NTLM secure channel.

-   For adclient to work with long host name (up to 19 characters), you have to update the adjoin.samaccountname.length setting in centrifydc.conf.

Do you want to continue?


    Report Center


·        Export now supports csv format instead of excel format (which was in fact a html format). (REF#: 43745)


Zone Provisioning Agent


·       ZPA failed to provision if a Contact object was in the AD group. This is fixed. (REF#: 49585)


    Centrify OpenSSH


·        The previous version used SSHv2 protocol as default but yet did not show this in the corresponding configuration file and hence some security analyzer might incorrectly judge that it was using SSHv1 as default. This is made clear by explicitly specified ‘Protocol 2’ in the configuration file. (REF#: 53959)


3.2.  Bugs Fixed in Centrify DirectControl 5.1.1

DirectControl Agent


·        Active Directory user fails to find credential cache after login to a newly created WPAR on AIX


In a newly created WPAR, the /var/krb5/security/creds/ directory does not exist.  DirectControl post-install script will create it with root permissions.  However, it does not change its permission to make it a world-writable directory. Hence Active Directory user fails to find credential cache after login because the application cannot access the credential cache in that directory.  This issue is fixed in this release. (REF#: 39909)


·        The command utility, adcheck, had a potential security vulnerability of creating temporary files with world write access. This is fixed in this release. (REF#: 47636).


DirectManage Access Manager


·        Some roles may not appear in the Role Browser when creating new role assignment. This is related to the default role in older version. This is now fixed. (REF#: 39899, 40968)


·        The User Effective Rights Report shows only users in current forest. This is now fixed. (REF#: 40023)


·        The “Incomplete user UNIX Data” check in Analyze wizard may take a very long time to run if the zone has over thousands of users. This is now fixed. (REF#: 45896).


·        Prepare computer wizard may show error “Unable to find Zone” if the letter case of domain name appears different in object path and trustedDomain object. This is now fixed. (REF#: 43474)


·        Unexpected exception is thrown if user ‘Accept’ a pending UNIX group in computer zone. This is now fixed. (REF#: 44900)


Centrify OpenSSH


·        Fixed the following issues of Centrify openSSH’s helper scripts.

- Centrify SSH daemon does not start automatically after reboot on HPUX (REF#: 38294)

- "/etc/init.d/centrify-sshd status" gets unexpected result when cdc-sshd is stopped (REF#: 37157)

- condrestart in centrify-sshd.init does not work in the RHEL 6.x upstart (REF#: 43655)

- "/etc/init.d/centrify-sshd" does not show confirmation message on Solaris or Debian (REF#: 37798)


3.3.  Bugs Fixed in Centrify DirectControl 5.1.0

DirectControl Agent


·        DirectControl Agent has historically written working data to /tmp.  This version of DirectControl Agent uses /var/centrify/tmp for its working data.  It eliminates the symlink vulnerability issue exposed by the /tmp directory, which every user has the write access (REF#: 38474).


·        adclient crashed couple times a day doing its own internal health checks on AIX. It is due to a bug in the gcc shared library.  The gcc compiler is upgraded to resolve this issue (REF#:27370).


·        When the user moves from local domain to foreign domain in a one-way forest trust, the user cannot login in offline mode.  This issue is fixed in this release (REF#: 31031).


·        Fixed adclient in “down” status when a user in foreign group is migrated to current domain (REF#: 34512).


·        Fixed adclient core dump issue when authenticating bad password (REF#: 32320).


·        Fixed a bug that causes high CPU utilization if DirectControl agent switches to another domain controller while it is constructing the internal cache (REF#: 36663).


·        Join computer supports host name longer than 15 characters and containing dots (REF#: 32773).


·        Fixed the self-serve join problem after pre-create computer if the zone parameter is not specified.  Without the zone parameter, self-serve join would select the first zone in the list (REF#: 36662).


·        If a group contains more than 500 members, the defect that adquery or getent group command returned duplicate or missing members is fixed (REF#: 31128).


·        Fixed the problem that automatically mounts the file system when the group command is executed (REF#: 26467).


·        Fixed adquery listing users who have no listed or login role (REF#: 32486).


·        Roles can be inherited from more than 2 levels in hierarchical zones (REF#: 29982).


·        An LDAP user who has not been migrated to AD could not change their LDAP password upon logon on a server with Centrify installed.  This is fixed (REF#: 29383).


·        /tmp directory is filled up with random name files after running adauto.pl repeatedly.  A random name file is created by each invocation of adauto.pl.  This problem is now fixed (REF#: 34582).


DirectManage Access Manager


·        DirectManage Access Manager does not time out in a big forest when a computer zone is created (REF#: 33229).


·        When a zone is moved in DirectManage Access Manager, the new zone path was not changed in the Centrify Profile in ADUC. This problem is fixed (REF#: 33229).


·        DirectManage Access Manager can coexist with DirectManage Audit Manager and DirectManage Audit Analyzer in the same MMC console (REF#: 26113).


Zone Provisioning Agent


·        Zone Provisioning Agent copies users and groups correctly when there are duplicate samAccountName (REF# 33535).


·        Zone Provisioning Agent will now keep the configuration settings during upgrade.


·        Zone Provisioning Agent will not unprovision existing user profiles from a zone when ZPA detects one of the source groups has been deleted (REF#: 30025).


·        Zone Provisioning Agent fixed the issue causing "The server is not operational" error by reusing the LDAP connection (REF#: 31331).


Centrify OpenSSH


·        The Ticket Granting Ticket (TGT) is not forwarded by Centrify OpenSSH.  This problem is now fixed (REF#: 30610).


3.4. Bugs Fixed in Centrify DirectControl 5.0.5


·        Added group policies for Mac 0S/X 10.8. See the Group Policy Guide for details.


·        Centrify 4.5.5 OpenSSH does not remove /usr/local/bin in the PATH environment variable.

3.5. Bugs Fixed in Centrify DirectControl 5.0.4


·        This release contains new features and no bugs fix. See section 2.2 for the list of the new features.

3.6. Bugs Fixed in Centrify DirectControl 5.0.3


·        See the Centrify DirectControl for Mac OS X release notes in the Documentation directory for more information.

3.7. Bugs Fixed in Centrify DirectControl 5.0.2


·        User can login to Active Directory with sid in sidHistory in the tokenGroups attribute.


·        User can login to Active Directory through local cache after the machine is disconnected and restarted.


·        NTLM can login Active Directory domain through local cache when the machine cannot access the domain controller.


·        adedit create_zone API works for FIPS compliant license.


·        AD user will expire in cache if it is marked force expired even though AD user in cache is queried frequently.


·        Overridden AD user is visible although its name in cache has been flushed.


·        adsmb can successfully get a file.


·        Centrify 4.5.3 OpenSSH X11 forwarding works in IPv4 network.


·        Centrify 4.5.3 OpenSSH does not stall a few seconds when it logins Solaris SPARC machines.


·        Centrify 4.5.3 OpenSSH can coexist with Solaris SSH.


·        Imported users and groups from passwd and group files do not show "Incomplete user UNIX data" error message.


·        Deployment Manager can work with interactive prompt after ssh connection.


·        Rights are cumulated across multiple roles with restrictive shell.


·        Centrify 4.5.3 PuTTY release is updated with the latest open source PuTTY 0.62 release and adds all new features delivered in that release. PuTTY 0.62 contains a security fix that it no longer retains passwords in memory.

3.8. Bugs Fixed in Centrify DirectControl 5.0.1


·        SuSE 11 won't crash if tilde is used in ksh.


·        DirectControl can now be upgraded via Ubuntu apt-get.


·        User with effective rights of non-password cannot login with a password.


·        User gets restricted shell if "Login with non-Restricted Shell" in "System Rights" is not checked.


·        adsmb is able to use the current Active Directory user's credentials.


·        Upper case netgroup names are supported in LDAPProxy.


·        adnisd reads the correct NIS maps even if the DirectControl agent switches to another domain controller while adnisd is reading the NIS maps.


·        ZPA does not truncate the UNIX name to 8 characters if the "Truncate the UNIX name to eight characters" check box is not selected.


·        ZPA can collect debug log if "Turn on debug logging" is checked in the ZPA Configuration Panel.


·        When searching for users in a remote forest, the remote forest is shown in a separate tree.


·        Find Users now works even if orphans exist in zones.

4.   Known Issues


The following sections describe common known issues or limitations associated with this Centrify Suite release; they are categorized as follows:


- DirectManage Access Manager

- Group policies

- Zone Provisioning Agent

- DirectControl Agent

- Centrify NIS server (adnisd)

- Centrify Network Information Service

- Centrify LDAP Proxy

- Smart Card

- Zone Migration

- Interoperability with Centrify Samba


In addition to the known issues described in these sections, you should review the details in the appropriate platform-specific release-notes-agent.txt file for the operating environments you support.


For the most up to date list of known issues, please login to the Customer Support Portal at http://www.centrify.com/support and refer to Knowledge Base articles for any known issues with the release.

    DirectControl Agent


·        On AIX, no user is able to login except root if the stanza in methods.cfg is corrupted (REF#: 36849)


It is because the AIX framework is not able to handle the blank line in methods.cfg's stanza. As a preventive measure, we have added a new test case into adcheck to check if the format of methods.cfg is correct. If the format of methods.cfg is wrong, adcheck will show the test case failed so that users can fix methods.cfg before deploying DirectControl agent.


·        On AIX, upgrading DirectControl in disconnected mode may cause unexpected behavior (REF#: 39461)


On AIX, upgrading DirectControl from 5.0.2 or older versions in disconnected mode may cause unexpected behavior. The centrifydc service may be down after upgrade. It's recommended not to upgrade DirectControl in disconnected mode.


·        On some versions of AIX, user may not be able to login if LOGIN_NAME_MAX is set to 9 (REF#: 40731)


Some versions of AIX cannot handle user name longer than eight characters. As a preventive measure, we have added a new test case into adcheck to check if the parameter LOGIN_NAME_MAX is set to 9. If yes, adcheck will show a warning to this test case so that users may understand the potential risk and decide if it may be a problem in their environment or not.


·        On AIX with WPAR environment set up, in-memory credential cache provided by Centrify-KCM service does not work due to a bug in the System Resource Controller (SRC) area. (REF#: 54235)


You can use the file-based credential cache instead. If you need to use in-memory credential cache, you will need to start the Centrify-KCM service manually. If further assistance is needed, please contact Support for help.


·        On Solaris 8 and 9, user may fail to install DirectControl due to Perl not installed (REF#: 45722, 50863)


Some versions of Solaris, e.g. 8 and 9, may not have Perl version 5.8 or above pre-installed resulting in some DirectControl features, e.g. group policy, not running properly. Starting from DirectControl version 5.1.1, we have enforced the checking for the correct Perl version in adcheck. If Perl version is not 5.8 or above, adcheck will fail the test case. Users have to install a proper Perl version before proceeding to install DirectControl.


·        On HPUX 11.11 and 11.23, KCM server credential support may not work due to missing libc patches, resulting in some features not working, e.g AD users cannot access Samba server (REF#: 53496)


On HPUX 11.11, the patch PHCO_36184 is required whereas on HPUX 11.23, the patch PHCO_35744 is required. As a preventive measure, we have added a new test case into adcheck to check if the required patch is there. If the required patch is not available, adcheck will show the test case failed and advise users to install the required patch before deploying DirectControl agent.


·        PAM messages depend on operating system (REF#: 9880)


Configurable PAM messages will be shown inconsistently depending on the login method, daemon version and operating system version.


·        adclient -c no longer supported (REF#: 11074)


To modify core dump behavior you should edit the adclient.dumpcore property in




·        Logging-in in disconnected mode (REF#: 12975)


In disconnected mode the UNIX name or the Windows login name should be used for logging-in. The Active Directory display name is not guaranteed to be unique and may not allow the user to authenticate.


·        Cross forest groups are not supported in the pam.allow.group or pam.deny.groups property setting. (REF#: 13127)


·        Working with adclient.client.idle.timeout (REF#: 13325)


This property is only read at startup. Hence if it is changed, adclient must be restarted. There is a Group Policy setting for this property but changing it has no effect until adclient is restarted on affected machines.


·        Use of addns on computers that act as network gateways (REF#: 15381)


UNIX computers that act as gateways between different networks may require specification of the addns command line such that the correct network adapter IP address is registered in Active Directory's DNS. Set the adclient.dynamic.dns.command property in




to the addns command line necessary to select the correct network interface and IP address.


·        Working with users defined in a Kerberos realm (REF#: 17977)


DirectControl supports users defined in a Kerberos realm as long as the Kerberos domains / realms are resolvable by DNS. Kerberos realm names are case sensitive, so care should be taken to check the spelling / case of any realm used.


·        Use of rsh and rcp with DirectControl (REF#: 18570, 17392)


rsh and rcp are considered archaic methods and should not be used with DirectControl as their behavior cannot be guaranteed in all circumstances.


·        adedit cannot create AIX extended attributes in a SFU zone (REF#: 24421)


·        Change in behavior of users to ignore (REF#: 36182)


In DirectControl 4.x the nss.user.ignore and pam.ignore.users lists were treated separately and adclient only checked nss.user.ignore. In DirectControl 5.0.0 and later, both nss.user.ignore and pam.ignore.users are checked and the ignore list is the logical "or" of the two.


·        Failed to login as override user with NSCD running (REF#: 37182)


On Solaris, with NSCD running, attempt to login as override user using <username>@localhost fails.


·        Potential issues on Fedora 19 (REF#: 47516, 48825)


There are several potential issues on Fedora 19:

1)  Adcheck will fail if the machine does not have Perl installed.

2)  Group Policy will not be fully functional unless Text/ParseWords.pm is installed.


·        Using DirectControl 4.x agents with DirectControl 5.x (REF#: 90001)


DirectControl 4.x agents can join classic zones created by DirectControl 5.x. It is possible to join a DirectControl 4.x agent to a hierarchical zone as well, but this should be avoided as the behavior is undefined.


·        adclient and asymmetric DNS servers (REF#: 90001)


adclient expects all DNS servers to have the same information (i.e. they are symmetric), it has no concept of asymmetric DNS servers. This means that if multiple DNS servers are defined and the information in each is not the same, it is possible that the information in some domains may be inaccessible some or all of the time, depending on the speed of response of the DNS servers and the information they hold. The /etc/centrifydc/centrifydc.conf parameter dns.sort will turn off the random nature of the accessibility and allow specification of the order in which to attempt to use DNS servers. Note, however, that it will still not use the DNS servers as a "path", the highest placed DNS server will win.


·        Some non-alphanumeric characters are valid for Windows user or group names and are converted to underscore ("_") when changed to be UNIX names in the Access Manager, but cannot be used in adedit. (REF#: 90001)


The list is:

\ ( ) + ; " , < > =


·        Default zone not used in DirectControl 5.x (REF#: 90001)


In DirectControl 4.x, and earlier, there was a concept of the default zone. When DirectControl was installed a default zone could be created that would be the default zone used when none was specified. If no zone was specified when joining a domain with adjoin, the default zone would be used.


This concept has been removed from DirectControl 5.0.0 and later as it is no longer relevant with hierarchical zones. In zoned mode, a zone must now always be specified.


A zone called "default" may be created, and default zones created in earlier versions of DirectControl may be used, but the name must be explicitly used.


·        Change password and rsh / rlogin (REF#: 90001)


When using rsh or rlogin to access a computer that has DirectControl installed, and where the user is required to change their password, users are prompted to change their password twice. Users may use the same password each time they are prompted and the password is successfully changed.


·        Changing the password of an orphan user with adpasswd (REF#: 90001)


adpasswd should not be used to change the password of an orphan user.  If it is used, an error will be generated as follows:


Error: Unsuccessful IPC execute: system error


·        Working with /var mounted via NFS (REF#: 90009)


If /var is mounted via NFS then, in order for DirectControl to function correctly, it is necessary to use the adclient.clients.socket parameter in /etc/centrifydc/centrifydc.conf to point to a local directory. In addition, you should make a symlink from /var/centrifydc/daemon to the local directory you have chosen.


You should set no_root_squash option in order to let /var/centrify/tmp to work over NFS. Otherwise root will be mapped to anonymous user “nobody” in NFS server, which does not always have write access to the exported directory.


·        nss.minuid and nss.mingid are no longer used (REF#: 90009)


These have been replaced by user.ignore and group.ignore.  DirectControl will ignore the local uid and gid values which correspond to the users and groups in the .ignore file and generate a uid.ignore and gid.ignore file.   The values from nss.minuid and nss.mingid will be added to this file during the upgrade process.




   DirectAuthorize on Linux/UNIX


·        Use of common UNIX commands with DirectAuthorize restricted shells


The DirectAuthorize restricted shell allows users to be restricted to use only a predetermined set of commands; however several common UNIX commands may allow users to execute commands that are not allowed in the restricted shell. The following list provides general guidance and specific examples of the issues to be considered:


- The man command (REF#: 14354)


When adding a privileged command for the man command in a restricted environment, Centrify recommends:


* selecting Reset Environment Variables to allow users to use the default pager only.


* disallow the -P, -C, -B or -H options to allow users to use the default pager and man configuration file only, by adding the following commands in addition to the command for man:


!man -[PCBH]*

!man * -[PCBH]*


The PAGER, MANPAGER environment variables and -P, -C, -B, or –H option can allow a user to run a command not permitted by DirectAuthorize in the restricted environment.


- The Allow nested command execution option (REF#: 14726)


The Allow nested command execution checkbox on the Attributes tab of the property page for a privileged command allows the privileged command to execute another command. This option is deselected by default (so the command is not allowed to execute other commands), but not all operating systems honor this restriction:


Solaris           Honored in all cases

AIX 5.1, 5.2      Not honored in all cases

AIX 5.3, 6.1, 7.1 Honored except if a program is seteuid

HP-UX             Honored except if a program is seteuid

Linux             Honored except if a program is seteuid and

                  the Run As... user is not root


- The tar command (REF#: 14880)


When adding the tar command to a restricted environment, Centrify recommends adding the following commands to prevent the --use-compress-program option to tar in addition to the tar command itself.


!tar --use-compress-program*

!tar * --use-compress-program*


This prevents the user from using the --use-compress-program option to run other commands not allowed in the restricted environment.


- cron jobs (REF#: 14881)


Cron jobs are run by the crontab daemon and this has no dzsh restrictions, meaning that any restrictions placed on the user who created the cron job will not be in force when the job itself is run.


For this reason, Centrify recommends that users who run in the dzsh restricted shell are not given access to the crontab cmmand.


- Editors that allow shell escapes (REF#: 14883)


When adding the vi or view command to a restricted shell, the shell escape feature of the command can allow the user to execute a command not allowed in the restricted shell.


In addition, the perl, python and ruby support feature of vim, if available, can allow a user to execute a command not allowed in the restricted shell. To check if your version of vim command has perl, python or ruby support, run vim --version, and look for +perl, +python, or +ruby.


Centrify recommends the following:


* Configure the command to not allow nested command execution (this is the default) to prevent shell escapes


* Use the rvi or rview command instead if available.


Vim is used as an example here, this applies to other editors that include the ability to escape to the shell and/or include scripting language support.


- The rsync command (REF: 14885)


When adding the rsync command to a restricted environment, Centrify recommends adding the following commands, in addition to adding the rsync command itself, to prevent usage of the -e and --rsh options:


!rsync -e*

!rsync * -e*

!rsync --rsh*

!rsync * --rsh*


This prevents the user from using the -e or --rsh options to run commands not allowed in the restricted environment.


·        Cannot add cross domain or cross forest users to roles in classic zone (REF#: 90001)


DirectAuthorize does not currently support adding users from other domains into roles when the domain controllers are running Windows Server 2003 with security update 926122 or service pack 2.  This is a Microsoft issue and a hot fix is available to install on computers running the DirectAuthorize console that need to run in these domains. More information may be found here:




·        Cannot add cross forest groups to a role in classic zones (REF#: 90001)


DirectAuthorize does not support adding groups from a trusted forest into roles at this time; all groups added to roles should be defined in the local forest. However, users from a trusted forest may be added to groups in the local forest and then added to a role, or they may be directly added to a role.


·        DirectAuthorize reports do not include users in remote forest (REF#: 90001)


In this release the "Classic Zone - User Role Assignments Grouped by Zone" and “Classic Zone - User Privilege Command Rights Grouped by Zone" reports only show users in the local forest; any users in remote (trusted) forests are not included in the report.


·        UI elements occasionally do not appear when expected (REF#: 90009)


On occasion, the DirectAuthorize console does not show the expected results, or nodes do not appear in the tree on the left side of the console screen. When this happens, choose Refresh from the right-click menu and the screen should refresh to show the expected results. If this does not fix the problem, choose Refresh from the next higher point up the tree from where you expect the result to be shown and that should cure the problem.


   DirectControl Auto Zone mode


·        One-way cross forest trusts are not supported in Auto Zone mode (REF#: AG-0403)


   Smart Card


·        When a SmartCard user attempts to login on Red Hat 6.0 with a password that has expired, the authentication error message may not mention that authentication has failed due to an expired password. (REF#: 31765)


·        On RedHat, any SmartCard user will get a PIN prompt even if he's not zoned, even though the login attempt will ultimately fail. This is a divergence from Mac behavior - On Mac, if a SmartCard user is not zoned, Mac doesn't even prompt the user for PIN. (REF#: 33482)


·        If a SmartCard user's Active Directory password expires while in disconnected mode, the user may still be able to log into their machine using their expired password. This is not a usual case, as secure SmartCard AD environments usually do not allow both PIN and Password logins while using a Smart Card. (REF#: 33666)


·        When logging into a RedHat system using an Active Directory user that has the same name as a local user, the system will not warn the user of the conflict, which will result in unpredictable login behavior. The workaround is to remove the conflict or login with a different AD user. (REF#: 33719)

·        In order to login successfully in disconnected mode (REF#: 34372):

o   For a password user:

§  A password user must log in successfully once in connected mode prior to logging in using disconnected mode. (This is consistent with other CDC Unix behavior)

o   For a SmartCard user:

§  The above is not true of SmartCard login. Given a properly configured RedHat system with valid certificate trust chain and CRL set up, a SmartCard user may successfully login using disconnected mode even without prior successful logins in connected mode.

§  If certificate trust chain is not configured properly on the RedHat system, the SmartCard user's login attempt will fail.

§  If the SmartCard user's login certificate has been revoked, and the RedHat system has a valid CRL that includes this cert, then the system will reject the user.


·        After upgrading from Centrify DirectControl version 5.0.4 to version 5.1, a Smartcard user may not be able to login successfully. The workaround is to run the following CLI commands:


sudo rm /etc/pam_pkcs11/cacerts/*

sudo rm /etc/pam_pkcs11/crls/*

sudo rm /var/centrify/net/certs/*


then run adgpupdate. (REF#: 37872)


·        When CRL check is set via Group Policy and attempting to authenticate via Smartcard, authentication may fail. The workaround is to wait until the after GP Update interval has occurred and try again or to force an immediate Group Policy update by running the CLI command adgpupdate. (REF#: 38080)


·        After upgrading from Centrify DirectControl Version 5.0.4 to version 5.1.1, a SmartCard user may not be able to authenticate successfully. The workaround is to perform the following command sequence:


sctool -d

sctool -e

sudo rm /etc/pam_pkcs11/cacerts/*

sudo rm /etc/pam_pkcs11/crls/*

sudo rm /var/centrify/net/certs/*"



and then re-login using the SmartCard and PIN. (REF#: 39004)


·        A name-mapping user can unlock screen with password even though the previous login was with PIN. (REF#: 39693)


·        Need to input PIN twice to login using CAC card with PIN on RedHat. It will fail on the first input but succeed on the second one. (REF#: 46172)


·        Running “sctool –D” with normal user will provide wrong CRL check result. The work-around is to run it as root. (REF#: 46199)


·         Screen saver shows password not PIN prompt (REF#: 47625)

Most smart card users are allowed to log on with a smart card and PIN only and cannot authenticate with a user name and password. However, it is possible to configure users for both smart card/PIN and user name/password authentication. Generally, this set up works seamlessly: the user either enters a user name and password at the log on prompt, or inserts a smart card and enters a PIN at the prompt.

However, for multi-user cards, it can be problematic when the screen locks and the card is in the reader. When a user attempts to unlock the screen, the system prompts for a password, not for a PIN, although the PIN is required because the card is in the reader. If the user is not aware that the card is still in the reader and enters his password multiple times, the card will lock once the limit for incorrect entries is reached.


    DirectManage Access Manager


·        NIS domain name with adnisd (REF#: 11140)


The NIS domain name in the Access Manager Zone Properties page is currently ignored by adnisd. The NIS domain name defaults to the name of the zone, or can be overridden in /etc/centrifydc/centrifydc.conf via the property "nisd.domain.name".


·        Calculating effective users (Show Effective User Rights menu or reports) in large environment may fail or take a very long time. (REF#: 37342, 37496)


·        Import users and groups before importing sudoers file (REF#: 90001)


Sudoers Import creates the user roles but not the users. It is recommended that you import users and groups prior to importing the sudoers file.  Otherwise, no sysRights are created for the users.


·        Pre-create computers before importing computer role from sudoers file (REF#: 90001)


The computers contained in the sudoers file must either be joined to a zone or pre-created. 


·        Delegating zone administration permissions for SFU zones (REF#: 90001)


Delegate permissions to add, remove or modify users for SFU zone are not supported.


·        Users with rights to import user and groups into a zone also gain rights to modify profiles (REF#: 90001)


Any users who are given the right to "Import users and groups to zone" are automatically also given the right to "Modify user/group profiles".


·        Using domain local groups to manage resources (REF#: 90001)


Domain local groups can only be used to manage resources in the same domain as the group. So, for instance, a domain local group in domain A may be used to manage a computer in domain A but not one in domain B, despite a trust relationship between the two domains.


·        Domain local groups from other domains shown in search dialog (REF#: 90001)


When using the search dialog in the Access Manager to delegate zone control to a group, domain local groups from child domains will be shown incorrectly in the results and should be ignored. The search results when using the ADUC extension do not show these domain local groups.


·        Analyze forest and SFU zones (REF#: 90001)


The analyze forest feature in the Access Manager does not report empty zones or duplicated users or groups in a SFU zone.


·        Working with users that have more than one UNIX mapping (REF#: 90001)


DirectControl supports Active Directory users that have more than one UNIX profile in a zone. However, if you are upgrading from DirectControl 4.x or earlier and have existing users with more than one UNIX mapping, you should use a DirectControl 5.0.0 or later Access Manager to remove all but one of the UNIX profiles for each of these AD users and then re-add them.


In addition, you should always use a DirectControl 5.0.0 or later console when modifying these users.


·        In the Centrify Profile tab of the Properties page of a computer joined to a hierarchical zone, you cannot move this computer to a classic zone. Nor can you move it to a zone in another domain. There are no such limitations with a computer joined to a classic zone. (REF#: 90001)


·        Extra results when analyzing duplicate service principal names (REF#: 90001)


When running the Analyze / Duplicate Service Principal Names report, kadmin/changepw is incorrectly returned as a duplicate.  The SPN is actually found multiple times, but this is by Microsoft design as it is the default account for the Key Distribution Center service in all domains.


·        Secondary groups not imported from XML files (REF#: 90009)


Using the Import Wizard to import user information from XML files does not import secondary group membership.


    Report Center


·        Color and font change in Report Center occasionally fails (REF#: 90009)


Changing the font or colors in a report occasionally fails, even though the Format dialog shows the chosen font and color choices when they are made. Re-opening the Format dialog and changing color and/or font again will correctly set the choices for the report.


    Zone Provisioning Agent


·        Install's "repair" option reports files in use (REF#: 20170)


When using the repair install option, the installer may pop up a “Files in Use” dialog that does not contain any entries. It is safe to simply click the Ignore button and continue the repair operation. This may happen on all supported platforms, except Windows Server 2003 and Windows Server 2003, R2.


    Zone Migration


·        admigrate does not migrate classic SFU zone. (REF#: 31712)


·        admigrate does not migrate zone delegation rights. (REF#: 90002)


    Group policies


·        There are four group policies that can merge the lines of different GPOs to a resulting group policy. For the policies to merge, the policy in each GPO must be enforced. Policies with higher precedence will be placed lower in the resulting multi-line policy. (REF#: 16638)


·        Entering multi-line password prompt group policies (REF: 26285)


Multi-line group policies are supported; however an escape newline character "\\n" must be used.


·        Checking the location of the Perl environment (REF: 45493)


DirectControl group policies require a version of Perl to be installed and located in the path. If Perl is not found in the path or has been installed in a non-standard location, you may encounter errors when you attempt to set group policies or leave the domain. If Perl is installed on the local computer but not included in the path by default, you can manually edit the shell script /usr/share/centrifydc/perl/run to add the correct path to the front of the PERL_DIRS environment variable.


·        Disable does not function with “Allow Groups” group policy (REF#: 90001)


Disabling the group policy Computer Configuration > Centrify Settings > Centrify SSH Settings > Allow Groups does not disable the policy. To effectively disable groups of users, the groups should be removed from the Group Policy Object.


    Centrify Network Information Service


·        adnisd daemon fails to start on WPAR (REF#: 39911)


The adnisd service is not defined in the WPAR.


    Centrify LDAP Proxy


·        LDAP Proxy is not re-started after upgrade (REF#: KB-2743, 33344, 39402)


You need to restart the LDAP proxy process manually with the command /usr/share/centrifydc/libexec/slapd.


·        Wildcard use is not supported with LDAP Proxy (REF#: 26721)


This release of the LDAP Proxy does not support searches using wildcards in rfc2307 mode.


·        Require the prefix “auto” in the automount map (REF#: 90001)


If an automount map created with a 4.x or earlier version of the DirectControl Console does not start with the string "auto" (i.e. auto.home, auto_master, auto_net, etc), it will not be recognized by this release of the DirectControl LDAP Proxy as an automount map. Automount maps which do not start with the string "auto" must be exported and imported using this version of the DirectControl Console or adedit.


    Centrify OpenSSH


·        Centrify OpenSSH version 5.1.2 requires DirectControl version 5.1.2 or above. (REF#: 51889)


·        Failed to start Centrify OpenSSH on RHEL 6.4 PPC with DirectControl version 5.1.1 (REF#: 53153)


32-bit PAM is required for PowerPC platforms. On those platforms, please make sure pam-<version>.ppc package is installed before installing Centrify OpenSSH.


    Interoperability with Centrify Samba


·        Centrify Samba 4.5.4 or above (REF#: 35573, 33146)


Starting with version 5.1.0, DirectControl Agent does not work with any earlier Centrify Samba versions on AIX and SuSE 8. It only works with Centrify Samba 4.5.4 or above.


5. Additional Information and Support


In addition to the documentation provided with this package, you can find the answers to common questions and information about any general or platform-specific known limitations as well as tips and suggestions from the Centrify Knowledge Base.


The Centrify Resource Center provides access to a wide range of packages and tools that you can download and install separately.  For more information, see the Centrify Resource Center Web site:




You can also contact Centrify Support directly with your questions through the Centrify Web site, by email, or by telephone. To contact Centrify Support or to get help with installing or using this version of Centrify Suite, send email to support@centrify.com or call 1-408-542-7500, option 2. For information about purchasing or evaluating Centrify products, send email to info@centrify.com.