When the

• If auto-provisioning is not desired, after completing the basic configuration, you can disable auto-provisioning using the steps listed in the Advanced Configuration section.
• Single Sign-On (SSO) authentication enables users to authenticate one time to access multiple systems. The SSO platform must translate its authentication into authentication methods executed against each system under SSO control. For more information, see https://en.wikipedia.org/wiki/Single_sign-on.
• When enabled, SSO also applies to the

  D s deskapp

  , if it is installed.

Supported authentication models:

Users can authenticate with the

• Azure AD is the identity provider,
• Azure AD is federated through a trust setup with a supported external identity provider,
• Azure AD is federated with on-premises Active Directory and Active Directory Federation Services (ADFS).

Azure Data Lake Store: Users can obtain OAuth access and refresh tokens from AzureAD and use the tokens to access ADLS.

Domain-Joined Clusters: Using Azure AD, the

Azure Databricks Clusters: If you have integrated with an Azure Databricks cluster, please complete this configuration to enable SSO authentication for Azure. No additional configuration is required to enable SSO for Azure Databricks.

Pre-Requisites

1. You have installed the

   D s platform

   on Microsoft Azure. See Install for Azure.
2. You have performed the basic configuration for Azure integration. See Configure for Azure.
3. Your enterprise uses Azure SSO for User Identity and Authentication.
4. The

   D s platform

   must be registered as a Service Provider in your Azure AD tenant.
5. Please acquire the following Service Provider properties:

   1. The Service Provider Application ID (Client ID) and Key (Secret) are used for user authentication to the Azure Key Vault, Azure AD, and Azure Data Lake Store (if connected). These properties are specified in the

      D s platform

      as part of the basic Azure configuration.

      Info
      NOTE: The D s platform must be assigned the Reader role for the Azure Key Vault. Other permissions are also required. See the Azure Key Vault Permissions section below.

   2. The Service Provider Reply URL provides the redirect URL after the user has authenticated with Azure AD.
   3. The Service Provider should be granted Delegated permissions to the Windows Azure Service Management API so it can access Azure Service Management as organization users.

Limitations

Scheduled jobs are run under the access keys for the user who initially created the schedule. They continue to run as scheduled until those keys are explicitly revoked by an admin.

Configure Azure AD for

D s platform

Please verify or perform the following configurations through Azure.

Azure Key Vault Permissions

For the Azure Key Vault:

• The

  D s item
  item application

  must be assigned the Reader permission to the key vault.
• For the Key Vault Secrets, the application must be assigned the Set, Get, and Delete permissions.

Configure

D s platform

for Azure AD

Azure AD Properties

Please configure the following properties.

https://<trifacta-app-host>/sign-in/azureCallback

User Management

Configure auto-registration

Enabling auto-registration:

Auto-registration must be enabled for the

How users are managed depends on whether auto-registration is enabled:

• If auto-registration is enabled, after users provide their credentials, the account is automatically created for them.
• If auto-registration is disabled, a

  D s item
  item administrator

  must still provision a user account before it is available. See below.

Enabled:

After SSO with auto-registration has been enabled, you can still manage users through the Admin Settings page, with the following provisions:

• The

  D s platform

  does not recheck for attribute values on each login. If attribute values change in LDAP, they must be updated in the User Management page, or the user must be deleted and recreated through auto-provisioning.
• If the user has been removed from AD, the user cannot sign in to the platform.
• If you need to remove a user from the platform, you should consider just disabling the user through the User Management area.

For more information, see Manage Users.

Disabled:

To disable auto-provisioning in the platform, please verify the following property:

1. D s config

2. Set the following property:

   Code Block
   "webapp.sso.enableAutoRegistration" : false,

3. Save your changes and restart the platform.
4. New users of the

   D s platform

   must be provisioned by a

   D s item
   item administrator

   . See below.

Provision new users under SSO without auto-registration

If SSO auto-registration is disabled, admin users can provision new users of the platform through the following URL:

https://<hostname>/register

http://<host_name>:<port_number>/register 

• The user's password is unnecessary in an SSO environment. You must provide the SSO principal value, which is typically the Active Directory login for the user.

• If you are connected to a Hadoop cluster, you must provision the Hadoop principal value.
• See Create User Account.
• Admin accounts can be created through the application. See Create Admin Account.

Disable user

For more information on disabling user accounts, see Manage Users.

User Access

Users access the application through the

https://<hostname>

SSO Relational Connections

For more information, see Enable SSO for Azure Relational Connections.