Veritas Data Insight 6.1 Administrator's Guide
- Section I. Getting started
- Introduction to Veritas Data Insight administration
- Configuring Data Insight global settings
- Overview of Data Insight licensing
- About scanning and event monitoring
- About filtering certain accounts, IP addresses, and paths
- About archiving data
- About Data Insight integration with Symantec Data Loss Prevention (DLP)
- Configuring advanced analytics
- About open shares
- About bulk assignment of custodians
- Section II. Configuring Data Insight
- Configuring Data Insight product users
- Configuring Data Insight product servers
- About node templates
- About automated alerts for patches and upgrades
- Configuring saved credentials
- Configuring directory service domains
- Adding a directory service domain to Data Insight
- Configuring containers
- Section III. Configuring native file systems in Data Insight
- Configuring NetApp file server monitoring
- Configuring clustered NetApp file server monitoring
- About configuring secure communication between Data Insight and cluster-mode NetApp devices
- Configuring EMC Celerra or VNX monitoring
- Configuring EMC Isilon monitoring
- Configuring Hitachi NAS file server monitoring
- Configuring Windows File Server monitoring
- Configuring Veritas File System (VxFS) file server monitoring
- Configuring monitoring of a generic device
- Managing file servers
- Adding filers
- Adding shares
- Renaming storage devices
- Configuring NetApp file server monitoring
- Section IV. Configuring SharePoint data sources
- Configuring monitoring of SharePoint web applications
- About the Data Insight web service for SharePoint
- Adding web applications
- Adding site collections
- Configuring monitoring of SharePoint Online accounts
- About SharePoint Online account monitoring
- Adding SharePoint Online accounts
- Adding site collections to SharePoint Online accounts
- Configuring monitoring of SharePoint web applications
- Section V. Configuring cloud data sources
- Section VI. Configuring ECM data sources
- Section VII. Health and monitoring
- Section VIII. Alerts and policies
- Section IX. Remediation
- Section X. Reference
- Appendix A. Backing up and restoring data
- Appendix B. Data Insight health checks
- Appendix C. Command File Reference
- Appendix D. Data Insight jobs
- Appendix E. Troubleshooting
- Troubleshooting FPolicy issues on NetApp devices
Add/Edit LDAP domain options
Use this dialog box to add a LDAP directory service server to Data Insight.
Table: Add/Edit LDAP properties options
Field | Description |
---|---|
Fully Qualified Domain Name | Enter the fully qualified name of the domain that you want to scan. Entering the FQDN will automatically populate the User and Group search Base DN fields. |
LDAP server address | Enter the hostname and the port of the LDAP server. By default, the LDAP server runs on HTTPS port 389. If TLS is enabled, the LDAP server runs on port 636, by default. |
Type | The type of LDAP schema used by the directory service. Data Insight extracts the attributes from the schema attribute file when scanning the domain. Select one of the following:
You can also create a schema attribute file with customized attributes for each LDAP implementation that does not match the defaults. Ensure that you name the file as |
Search base DN | The Organization Unit (OU) in which all users and groups have been defined. |
This directory uses secure connection (TLS) | Select this check box if the LDAP server uses the TLS protocol. |
Scanning details | Select the saved credentials from the drop-down or specify new credentials. The credentials should belong to an LDAP user who has appropriate privileges to scan the LDAP domain. If you are specifying scanning credential other than the directory administrator, then make sure that you have specified the correct DN for that user. For example, uid=ldapuser,ou=People,dc=openldap,dc=com. You can connect to the LDAP database to verify the DN for an LDAP user. The example below shows the DN of a sample user, ldapuser, created on a Linux openLDAP server: uid=ldapuser,ou=People,dc=openldap,dc=com. The DN string may change depending upon the LDAP schema used. Refer to the LDAP schema to get correct DN for the user. If specifying a user other than the directory administrator, ensure that the following limits have been set appropriately on the LDAP server:
The schema attribute names for setting these limits may vary depending upon the LDAP implementation. The above example is for Sun ONE. |
Test Credentials | Click to verify that the given credentials are correct and to test the availability of network connection between the Management Server and the LDAP server. Veritas recommends that you test the connection before proceeding to ensure that the Management Server is able to scan the LDAP server. |
Bind anonymously | Select the check box if you want to allow Data Insight to connect to the LDAP server without a credential. Select this option only if the LDAP server permits anonymous connections. |
Disable scanning | Select the check box to disable the scanning of the directory server. |