Create or Edit a Connector

• Mode — Keep the default of Read Only for a Connector that will handle only import operations (such as adding Data Sets). Select Read/Write to also support export of selected data to an Export Data area or an entire Project to a Project Data Area.

  The ability to execute both dedicated Project Export and subsequent Project Import enables Project portability among Organizations or between different Digital Reef sites.

• PanFS^® — When selected, the NFS Connector supports PanFS DirectFlow^® mode rather than standard NFS mode.

  PanFS setup procedures are required; consult your System Administrator if needed.

• Server — The IP address or Fully Qualified Domain Name of the server hosting the share that will be the mount point. This information is automatically validated and the available shares on the server are listed in the Path window below.
• Filter — Before you select a mount point, you can filter the list of shares if needed to more easily find the one you want.
• Path — Select a share (or a folder underneath a share) as the mount point for the Connector. Optionally validate the Connector's access to the selected share or folder, then click Create Connector.

• Mode — Keep the default of Read Only for a Connector that will handle only import operations (such as adding Data Sets). Select Read/Write to also support export of selected data to an Export Data area.
• Protocol — Select either FQDN/IP (the default) or NetBIOS.
• Authentication type — Select an authentication mechanism from the drop-down:
  • NONE — Anonymous login. The user can connect to the server without providing credentials.
  • NTLM (the default) — Windows challenge/response authentication protocol used with SMB. NTLM is supported by most NAS devices and by pre-Windows NT 4. (SP4) systems. NTLM provides basic password encryption and username and password authentication.
  • NTLMI — Adds packet signing to NTLM.
  • NTLMV2 — NTLM Version 2 provides stronger password encryption as well as support for both NT 4.0 (SP4) and NT Server-based systems such as XP. This is the default behavior to the required protocol for Vista and MS Server 2008.
  • NTLMV2I — Adds packet signing to NTLMV2.

  If you select an authentication type other than NONE, you must supply valid credentials and a workgroup/domain for connecting to the specified server.

  If you are configuring the Connector as Read/Write to perform CIFS-CIFS migration, you must include the workgroup or domain (even if you chose select NONE) to replicate permissions between source and destination.

• Support Legacy Mode — Select to have the CIFS Connector use the older Server Message Block (SMB) protocol version 1 to establish the connection, rather than a recent version (such as SMB 3) which should be suitable for most CIFS Connectors. Try selecting Support Legacy Mode if you have trouble validating your CIFS Connector and know that the other provided CIFS information is correct.
• Server — If you selected FQDN/IP for Protocol above, specify the IP address or Fully Qualified Domain Name of the server hosting the share that will be the mount point. If you selected NetBIOS, provide the NetBIOS name of the device exporting the storage. Either way, the information is automatically validated and the available shares on the server are listed in the Path window below.
• Filter — Before you select a mount point, you can filter the list of shares if needed to more easily find the one you want.
• Path — Select a share (or a folder underneath a share) as the mount point for the Connector. Optionally validate the Connector's access to the selected share or folder, then click Create Connector.

To connect to any Exchange configuration, select MS Exchange as the Connector type. The Connector mode is always Read Only.

Before you create an Exchange Connector, you must have a complete Windows Active Directory Server configuration with DNS support.

Local

To define a local Microsoft Exchange configuration, supply the following required information:

• Username/Password — The credentials the Connector will use to authenticate to local Microsoft Exchange server. The account they represent must have the rights needed to collect from the mailboxes of other accounts, and must itself have a user mailbox. For Office 365, use the name portion of the Global Administrator account name (for example, for Administrator@tenant.com, you enter Administrator.
• Domain name — The name of the domain the Exchange server is part of, for example eng.acmeinc.com.
• Server — The URL for the Exchange server, for example https://exchange01.eng.acmeinc.com.

When all of the information is entered, validate and create the Connector.

Office 365

To create an Office 365 Exchange Connector:

• The Office 365 registration and setup procedure must have been completed on the Exchange server. (These are described in a separate document, available upon request from Digital Reef Customer Support.)

• Your application must be registered with Office 365 using the Microsoft portal and you must be able to supply its Tenant Domain, Application ID, and Application Secret values.

Define the Office 365 Exchange connector by supplying the following required information:

• Tenant Domain — The Tenant Domain information (Primary domain) you specified when you registered your application with Office 365, in the format tenant.onmicrosoft.com. Example: acmeinc@onmicrosoft.com
• Application ID — The Application ID you received when you registered your application with Office 365.
• Application Secret — The Application Secret (also known as the Client Secret) that was generated when you registered your application with Office 365.

• Refresh Token — Optionally specify a Refresh Token value that will ensure access until it expires (for example, every 6 months). Expiration of the Refresh Token is determined by the policies in place for the associated Azure Active Directory account. The Refresh Token can be generated as part of the Connector Setup procedure (described in a separate document available upon request from Digital Reef Customer Support).

When all of the information is entered, validate and create the Connector.

If you have already configured a SharePoint Configuration for Office 365, you can use the same Tenant Domain, Application ID, and Application Secret values for the Exchange Connector. Once the Connector has been established, you can click Edit to view and/or change the Connector information. The Refresh Token field is displayed with a Last Updated date that indicates when the Refresh Token was last generated.

To connect to any SharePoint configuration, select MS SharePoint as the Connector type. The Connector mode is always Read Only.

Local

To define a local Microsoft SharePoint configuration, supply the following required information:

• Username/Password — The credentials the Connector will use to authenticate to local Microsoft SharePoint server.
• Domain name — The name of the domain the SharePoint server is part of, for example eng.acmeinc.com.
• Server — A Fully-Qualified Domain Name (FDQN) representing the root URL for the SharePoint server, for example https://sharepoint01.eng.acmeinc.com.

Office 365

To create an Office 365 SharePoint Connector:

• The Office 365 registration and setup procedure must have been completed on the SharePoint server. (These are described in a separate document, available upon request from Digital Reef Customer Support.)

• Your application must be registered with Office 365 using the Microsoft portal and you must be able to supply its Tenant Domain, Application ID, and Application Secret values.

Define the Office 365 SharePoint connector by supplying the following required information:

• Tenant Domain — The Tenant Domain information (Primary domain) you specified when you registered your application with Office 365, in the format tenant.onmicrosoft.com. Example: acmeinc@onmicrosoft.com
• Application ID — The Application ID you received when you registered your application with Office 365.
• Application Secret — The Application Secret (also known as the Client Secret) that was generated when you registered your application with Office 365.

• Refresh Token — Optionally specify a Refresh Token value that will ensures access until it expires (for example, every 6 months). When the Refresh Token expires is determined by the policies in place for the associated Azure Active Directory account. The Refresh Token can be generated as part of the Connector Setup procedure (described in a separate document available upon request from Digital Reef Customer Support).

If you have already configured an Exchange Configuration for Office 365, you can use the same Tenant Domain, Application ID, and Application Secret values for the SharePoint Connector.

When all of the information is entered, validate and create the Connector.

The information you supply applies to both Public and Private sites. Once the Connector has been established, you can click Edit to view and/or change the Connector information. The Refresh Token field is displayed with a Last Updated date that indicates when the Refresh Token was last generated.