You must configure the Kerberos configuration file on the Data Integration Service machine to match the Kerberos realm properties of the Hadoop cluster. Verify that the Hadoop Kerberos properties are configured in the Data Integration Service and the Metadata Access Service.

If the cluster uses Kerberos and does not use the Enterprise Security Package, you can configure Ranger authorization separately to grant permissions to Informatica users.

You must import security certificates to the Data Integration Service and the Metadata Access Service machines. See Configuring Access to an SSL/TLS-Enabled Cluster.

If the transparent encryption uses Cloudera Java KMS, Cloudera Navigator KMS, or Apache Ranger KMS, you must configure the KMS for Informatica user access.

If the cluster uses Enterprise Security Package and ADLS Gen1 or Gen2 storage, perform the following tasks:

Create a keytab file on any one of the cluster nodes for the specific user. To create a keytab file, see Using the ktutil Utility to create a Keytab File.
Configure proxy users in core-site.xml. Populate the following properties:
hadoop.proxyuser.<SPN username>.groups=user1,user2,user3
hadoop.proxyuser.<SPN username>.hosts=user1,user2,user3
hadoop.proxyuser.<SPN username>.users=user1,user2,user3
... where <SPN username> is the Kerberos Service Principal User. For more information, see Configure *-site Files for Azure HDInsight.
If the cluster uses ADLS Gen1 storage, assign the Owner role to the Azure HDInsight cluster service principal display name. See Assigning the Owner Role to the Service Principal User.

If the cluster uses WASB storage, configure the storage account access key in core-site.xml. Populate the following property:

fs.azure.account.key.<your account>.blob.core.windows.net

For more information, see Configure *-site Files for Azure HDInsight.