Administration of Microsoft Dynamics CRM Connector
If you use Active Directory to access Microsoft Dynamics CRM data, perform the following steps before you use Microsoft Dynamics CRM connections:
1. Configure Java security for a Microsoft Dynamics CRM instance that uses self-signed certificates.
2. Resolve hosts.
3. Edit the Kerberos configuration files.
4. Download Java security policy files.
After you perform the required configuration, restart the Secure Agent.
Step 1. Configuring Java Security
Configure Java security for Microsoft Dynamics CRM instances that use Active Directory and self-signed certificates.
1. Generate root and intermediate SSL certificates for HTTPS URL (.cer files).
2. Use the command line to navigate to the following directory:
<SecureAgent_InstallDir>/jre/bin/
3. Use the following command to import HTTPS certificates to the Informatica Java Runtime Environment (JRE):
keytool -importcert -alias <certificate alias name> -file " <certificate path>
\<certificate filename>" -keystore ..\lib\security\cacerts -trustcacerts
The Certificate Alias Name is any unique name and certificate file name includes the full path to the .cer files used in Step 1. The default JRE password is "changeit".
Step 2. Resolving Hosts
Resolve hosts for Microsoft Dynamics CRM instances that use Active Directory authentication.
To resolve the hosts used for Microsoft Dynamics CRM deployment, add the Microsoft Dynamics CRM IP address and the name to the hosts file.
In Windows 7, you can find the hosts file in the following directory:
<Windows_InstallDirectory>\Windows\System32\drivers\etc
Step 3. Editing the Kerberos Configuration Files
Edit the Kerberos configuration files for Microsoft Dynamics CRM instances that use Active Directory authentication.
1. Go to <Secure Agent installation directory>/apps/Data_Integration_Server/ext directory and create deploy_to_main/bin/rdtm-extra folder.
2. Copy the msdcrm folder from <Secure Agent installation directory>/downloads/package-MicrosoftDynamicsConnector.<version of Microsoft Dynamics CRM Connector package>/package/rdtm directory to <Secure Agent installation directory>/apps/Data_Integration_Server/ext/deploy_to_main/bin/rdtm-extra directory.
3. Open the krb5.conf.sample configuration file, located in the following directory: <Secure Agent installation directory>/apps/Data_Integration_Server/ext/deploy_to_main/bin/rdtm-extra/msdcrm/conf
4. Configure the following values in the configuration file:
[libdefaults]
default_realm = <fully qualified domain name>
default_tkt_enctypes = rc4-hmac
default_tgs_enctypes = rc4-hmac
permitted_enctypes = rc4-hmac
[realms]
<fully qualified domain name> = {
kdc = <domain controller hostname>.<fully qualified domain name>default_domain = <fully qualified domain name>
}
[domain_realm]
.<fully qualified domain name> = <fully qualified domain name>
5. Rename the krb5.conf.sample configuration file as krb5.conf.
6. Open the login.conf.sample login configuration file, located in the following directory: <Secure Agent installation directory>/apps/Data_Integration_Server/ext/deploy_to_main/bin/rdtm-extra/msdcrm/conf
- - If the Microsoft Dynamics CRM server pool identity is set to a specific user account, add the serverprincipal="<user name>" entry to the file as follows:
spnego-client {
com.sun.security.auth.module.krb5LoginModule required
serverprincipal="<user name>"
storePass=true;
};
The user name is the user account used by the application pool and defined in the Active Directory properties.
- - If the Microsoft Dynamics CRM server pool identity is set to a network service, add the serverprincipal="<URL>" entry to the file as follows:
spnego-client {
com.sun.security.auth.module.krb5LoginModule required
serverprincipal="<URL>"
storePass=true;
};
The URL is the HTTP SPN entry for the Microsoft Dynamics CRM instance.
7. Rename the login.conf.sample login configuration file as login.conf.
Step 5. Downloading Java Security Policy Files
Download Java security policy files for Microsoft Dynamics CRM instances that use Active Directory authentication.
Unzip the zip package and copy the local_policy.jar and US_export_policy.jar files to the following directory:
<Secure Agent installation directory>\jre\lib\security
Overwrite the existing files in the directory.