After upgrading to connector 2016.3.1.0 or later, you may need to configure some settings.

Rejoin Domain with Kerberos Authentication

If you use Kerberos authentication or Active Directory (Integrated Windows Authentication) directories, you must leave the domain and then rejoin it. This is required for all the connector virtual appliances in your deployment.

  1. Select Administration > Directories Management > Connectors

  2. In the Connectors page, for each connector that is being used for Kerberos authentication or an Active Directory (Integrated Windows Authentication) directory, click Leave Domain.

  3. To join the domain, you need Active Directory credentials with the privileges to join the domain. See Join a Connector Machine to a Domain for more information.

  4. If you are using Kerberos authentication, enable the Kerberos authentication adapter again. To access the Auth Adapters page, in the Connectors page click the appropriate link in the Worker column and select the Auth Adapters tab.

  5. Verify that the other authentication adapters you are using are enabled.

Update Domains Page

If you are using Active Directory (Integrated Windows Authentication), or Active Directory over LDAP with the This Directory supports DNS Service Location option enabled, save the directory's Domains page.

  1. Select Administration > Directories Management > Directories

  2. Select the applicable directory to edit it.

  3. Provide the password for the Bind DN user and click Save.

  4. Click Sync Settings on the left of the page and select the Domains tab.

  5. Click Save.

DNS Service Location and Domain Controllers

Note:

In connector 2016.3.1.0 and later, a domain_krb.properties file is automatically created and auto-populated with domain controllers when a directory with DNS Service Location enabled is created. When you save the Domains page after upgrade, if you had a domain_krb.properties file in your original deployment, the file is updated with domains that you may have added subsequently and that were not in the file. If you did not have a domain_krb.properties file in your original deployment, the file is created and auto-populated with domain controllers. See About Domain Controller Selection for more information about the domain_krb.properties file.