Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-3232: How to verify if a notification handler has been enabled.

Authentication Service ,  

12 April,16 at 11:43 AM

Applies to: All versions of Centrify DirectControl Console/DirectManage Access Manager 

 
Question:
 
How to verify if a Notification Handler has been enabled?

 
Answer:
 
If a Notification Handler is setup properly, when deleting an AD user that was added to a Zone, the following should be seen: 

Centrify Notification handler. Are you sure you want to delete user name 'abc'? The selected object has other associated objects. Select those associated objects that you also want to delete. Centrify DirectControl Data
 
 
To verify it in detail, check the following two locations: 
 
1) AD display specifier 

Using ADSI Edit, browse to domain/Configuration/DisplaySpecifiers/LanguageID/DS-UI-Default-Settings
 
Note:
The default naming context of ADSIEdit may not show the Configuration container. You can, however, specify it manually.
  1. Select Action -> Connect to... In the "Connection Point" frame,
  2. choose "Select a well known Naming Context".
  3. Choose "Configuration" from the drop-down box.
  4. Hit OK,
The Configuration container, and its sub-containers such as CN=Services and CN=Sites, will now be visible.
 
For example, if the Active Directory domain is ajax.org and the language support is US-English (CN=409), the entry to this object would be found in:
ajax.org/Configuration/DisplaySpecifiers/409/DS-UI-Default-Settings
 
object path: CN=DS-UI-Default-Settings,CN=<localeID>,CN=DisplaySpecifiers,CN=Configuration,DC=domain,DC=com
 
Check if the dSUIAdminNotification attribute of the above object contains the following values by right clicking on the object (DS-UI-Default-settings), and choosing properties: 
 
<any number>,{D0D2C2AE-C143-4C81-A61C-BE95C3C5EEDF} 
<any number>,{DD3941B8-CD2E-4759-AE77-02E9CCD84BD6} 
 
 
 
2) COM objects is installed 
 
Check if the following keys exist in the registry: (On machine where ADUC Notification Handler is needed) 
 
HKEY_CLASSES_ROOT\CLSID\{D0D2C2AE-C143-4C81-A61C-BE95C3C5EEDF} 
HKEY_CLASSES_ROOT\CLSID\{DD3941B8-CD2E-4759-AE77-02E9CCD84BD6} 
 
In the "InprocServer32" key under the above keys, the value of "CodeBase" should be the path of the installed aduc.mmc.dll. 

 
For further detail, please see: 

Centrify Unix Deployment Guide, Section Registering the administrative notification handler
https://docs.centrify.com/en/css/suite2016/centrify-unix-deployment-guide.pdf#page=240

http://msdn.microsoft.com/en-us/library/windows/desktop/ms675001(v=vs.85).aspx

 

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 article[How To] Enable Symantec VIP MFA for Centrify Server Suite on Linux Part I article[How To] Enable Symantec VIP MFA for Centrify Server Suite on Linux Part II article[How To] Enable Symantec VIP MFA for Centrify Server Suite on Linux Part III article[LABS] Testing the Local UNIX User/Group Management feature of Centrify Server Suite 2016 article[Labs] Setting-up an AWS Test Lab for Centrify articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6044: How to configure users for automatic Kerberos Credentials for infinite renewal even after users have logged out? articleKB-6050: How to configure a group for automatic Kerberos Credentials for infinite renewal? articleCentrify 18.2 Release Notes