Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. D s config

  2. Configure the following settings:


    Enables use of SSO by the

    D s webapp

    Set this value to false.
    "webapp.sso.disableAuthGateway"When SSO is enabled, this value should be set to true to disable the use of the reverse proxy server, which is not used in SAML authentication.Set this value to true.
    "webapp.sso.enableAutoRegistration"Enables users to auto-register an account with the platform when they connect to the login page.To enable automatic access with SSO-authenticated users, set this value to true. To require administrator provisioning of user accounts, set this value to false. For more information, see Manage Users under SSO.

  3. Enable use of SAML by the 

    D s webapp

    D s triconf



    Set this value to true.
    "webapp.saml.server.entityId"Set this value to the URI of the enterprise SAML server.

  4. If your identity provider is sending attribute values that differ from the values expected by the platform, please configure those values in the following properties:

    D s triconf

    DescriptionSAML attribute
    "webapp.saml.mapping.ssoPrincipal"SAML profile attribute that defines a user's SSO principal.userPrincipalName

    SAML profile attribute that defines a user's name.



    SAML profile attribute that defines a user's Hadoop principal.



    SAML profile attribute that defines a user's email.


  5. Configure the path to IDP metadata file. This file was generated by the SAML setup script. 


    Tip: Unless you wish to move the file to a different directory, this value does not need to be changed.

    D s triconf



    Path to the IDP metadata file that you downloaded to the

    D s node


    NOTE: This value is required and should already be specified.



  6. Configure SAML call back URLs, if needed. These values do not require modifying in most cases.

    D s triconf



    URL to which user is redirected after logout. This value must end with /saml/logout/callback.
    "webapp.saml.server.callbackUrl"URL to which user is redirected after authentication. This value must end with /saml/login/callback?redirect_to=/.

  7. Configure paths to security certificates. Modify only if you have stored your keys in non-default locations or filenames: 

    D s triconf

    DescriptionDefault path
    ""This signing certificate must be a public certificate that matches the private key./opt/trifacta/conf/.key/saml-signing-public-key.cert
    ""This private key must match the public signing certificate. Authentication requests can be signed using RSA-SHA1. The private key must be in PEM format.
    Authentication requests can be signed using RSA-SHA1. To sign them you need to provide a private key in the PEM format.
    ""This private key is used for decrypting any encrypted assertions received by the platform. /opt/trifacta/conf/.key/saml-decryption-private-key.key
    ""This public certificate must match the private key for decryption./opt/trifacta/conf/.key/saml-decryption-public-key.cert

  8. Save the file.

  9. The following script must be run as the root user.

  10. On the

    D s node
    , navigate to the following directory:

    Code Block
    cd /opt/trifacta/webapp/bin

  11. Execute the following script:

    Code Block
    $ ./saml-sp-metadata-generator.js <hostname>

    where <hostname> is the host value for your 

    D s node
    . Do not include the protocol identifier (e.g. http://) or the port number as part of this value.

  12. The above script outputs the following:


    Tip: The objects, paths, and filenames generated by this script are automatically in place for use by the platform. To use other objects, you must configure the paths in the platform, as described later in this section.

    ItemDescriptionHow to Use
    Signing Private key Path to generated private key for signingPath was configured earlier. If the path is the default one and no asset exists there, then the setup script generates the asset for you.
    Signing Certificate Path to generated certificate for signingSee previous.
    Encryption Private keyPath to generated private key for encryptionSee previous.
    Encryption CertificatePath to generated certificate for encryptionSee previous.
    MetadataMetadata file saml-sp-metadata.xml for your identity providerSee next step.

  13. The saml-sp-metadata.xml file in the same directory where you executed the script can be uploaded to your identity provider.