...
- SAML 2.0 only. SAML 1.1 is not supported.
By default, our SP uses transient NameID format. Not all SAML providers will accept transient. You may have to change the metadata file to use something like the following:
Code Block <NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</NameIDFormat>
Info |
---|
NOTE: Spaces are not supported in values for hadoopPrincipal and ssoPrincipal. Suggested format: |
Prep
Warning | |
---|---|
Before you begin, you should create a backup of your |
...
Acquire SAML claims from your identity provider
...
Check the following SAML claims in your identify provider. Verify that it is sending the following pieces of information. Below are the default attributes that are expected by the platform:
...
Tip | ||
---|---|---|
Tip: If you do not have access to the IDP configuration, you can search the response back from your IDP for the following:
The full value inside the double quotes must be set as the second value in the MellonSetEnv properties file. To see the decoded SAML response, you can use a Chrome plugin like 'rcFederation SAML, WS-Federation and OAuth tracer'. |
...
Configure SAML for the platform
...
D s config method a Configure the following settings:
Setting Description Value "webapp.sso.enable" 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 tofalse
. For more information, see Manage Users under SSO.Enable use of SAML by the
:D s webapp
settingD s triconf Description "webapp.saml.enabled"
Set this value to true
."webapp.saml.server.entityId" Set this value to the URI of the enterprise SAML server. 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:
settingD s triconf Description SAML attribute "webapp.saml.mapping.ssoPrincipal" SAML profile attribute that defines a user's SSO principal. Spaces are not supported. userPrincipalName "webapp.saml.mapping.name" SAML profile attribute that defines a user's name.
name "webapp.saml.mapping.hadoopPrincipal"
SAML profile attribute that defines a user's Hadoop principal. Spaces are not supported.
userPrincipalName "webapp.saml.mapping.email"
SAML profile attribute that defines a user's email.
mail Configure the path to IDP metadata file. This file was generated by the SAML setup script.
Tip Tip: Unless you wish to move the file to a different directory, this value does not need to be changed.
settingD s triconf Description "webapp.saml.idpMetaDataPath"
Path to the IDP metadata file that you downloaded to the
.D s node Info NOTE: This value is required and should already be specified.
Configure SAML call back URLs, if needed. These values do not require modifying in most cases.
settingD s triconf Description "webapp.saml.server.logoutCallbackUrl"
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=/
.Configure paths to security certificates. Modify only if you have stored your keys in non-default locations or filenames:
settingD s triconf Description Default path "webapp.saml.security.signingCertPath" This signing certificate must be a public certificate that matches the private key. /opt/trifacta/conf/.key/saml-signing-public-key.cert "webapp.saml.security.privateCertPath" 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./opt/trifacta/conf/.key/saml-signing-private-key.key "webapp.saml.security.decryptionPvkPath" This private key is used for decrypting any encrypted assertions received by the platform. /opt/trifacta/conf/.key/saml-decryption-private-key.key "webapp.saml.security.decryptionCertPath" This public certificate must match the private key for decryption. /opt/trifacta/conf/.key/saml-decryption-public-key.cert Save the file.
The following script must be run as the
root
user.On the
, navigate to the following directory:D s node Code Block cd /opt/trifacta/webapp/bin
Execute the following script:
Code Block $ ./saml-sp-metadata-generator.js <hostname>
where
<hostname>
is the host value for your
. Do not include the protocol identifier (e.g.D s node http://
) or the port number as part of this value.The above script outputs the following:
Tip 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.
Item Description How to Use Signing Private key Path to generated private key for signing Path 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 signing See previous. Encryption Private key Path to generated private key for encryption See previous. Encryption Certificate Path to generated certificate for encryption See previous. Metadata Metadata file saml-sp-metadata.xml
for your identity providerSee next step. The
saml-sp-metadata.xml
file in the same directory where you executed the script can be uploaded to your identity provider.
...