Data source parameters
Here’s a summary of the parameters you need to fill for each data source when you set it up.
Microsoft Exchange on Premise
Common fields:
Field
Description
Exchange User
A user who has read access to the data you want to crawl and the ability to read mailboxes using Microsoft Identity Impersonation †. The Exchange User must have a valid mailbox.
Exchange Password
Password for the Exchange user.
Target
If you specify mailbox, NOW Privacy crawls just that mailbox. If you specify LDAP query, NOW Privacy crawls all the mailboxes that match the results of the query.
† Therefore, we only support objects that are accessible through impersonation.
Fields when the target is a mailbox:
Field
Description
Exchange Protocol
HTTP or HTTPS.
Exchange Server
The IP address or fully qualified domain name of the target Exchange server.
Mailbox
Specify one mailbox to crawl. For example: me@example.com.
Fields when the target is defined by an LDAP query:
Field
Description
Use Exchange Details
Check this if you want to use the Exchange User as the Directory User.
Directory User
User name for the connection to the Active Directory Server.
Directory Password
Password for the Directory user.
Exchange Protocol
As above.
Exchange Server
As above.
Directory Server
The IP address or fully qualified domain name of the target Active Directory server.
LDAP Protocol
The protocol used by the LDAP server: LDAP or LDAPS.
LDAP Port
The port that the LDAP server listens on. Defaults to port 389.
Directory Search Base
For more information, see Microsoft Exchange: Directory Search Base.
Directory Filter
For more information, see Microsoft Exchange: directory filter.
Microsoft Office 365 Exchange
Field
Description
Domain
The id of a Microsoft tenant-held domain. For example: nowvertical.onmicrosoft.com.
If the ingestion scope is Group Email, this is an email address that identifies a user group. For example: group@example.com. If the ingestion scope is User Email, this is the email address for an individual user.
Enterprise Vault
Field
Description
User Name
A user with read permissions to the Enterprise Vault archives you want to crawl.
Password
The password for the user.
Domain
The domain for the user.
HTTP Protocol
HTTP or HTTPS.
Service Host
The IP address or fully qualified domain name to the target server. Example: enterprisevault.mydomain.local
googledrive_connector
Field
Description
Admin Account ID
The email address of the admin account you created. This is the account NOW Privacy will impersonate for domain and group crawls. Required.
Service Account ID
The email address of the service account you created. This is the account NOW Privacy will use for impersonation. Required.
Private Key PEM String
The private key for the service account. This is the content of the PEM file, not the file name. NOW Privacy needs an exact copy of the content so be careful here. Required.
Crawl Level
Domain
Group
User
Domain
The domain where the crawl happens. Required for all crawl levels.
Group ID
The email address for the user group you will crawl. Required for user group crawls.
User Account ID
The email address for the individual user you will crawl. Required for individual user crawls.
MySQL
Field
Description
Host
The IP address or the fully qualified domain name of the target server.
Database/Schema
The name of the database you want to crawl. You can only target one database at a time.
Port
The port that MySQL is using. For example: 3306.
Username
A user who has read access to the data you want to crawl.
Password
The password for the user.
Microsoft SQL Server
Field
Description
Host
The IP address or fully qualified domain name of the target server. Can be server\instance or just server.
Database Name
The name of the database you want to crawl. You can only target one database at a time.
Port
The port that SQL Server is using. For example: 1433. Choose port 0 if SQL Server is using dynamic ports.
Schema Name
The schema name of the target database tables/views.
Username
A user who has read access to the data you want to crawl.
Password
The password for the user.
If you use port 0 you must include the instance in the host
If you specify both a port and instance, the port will take precedence and the instance name will be ignored
For SQL to look up the port when specifying port 0:
The firewall must allow traffic on UDP port 1434
For Microsoft SQL Server 2005 or later the SQL Server Browser Service must be running