Inserting Variables for Connection Parameters
Variables can be inserted for any connection parameter in a connection definition. The variables are passed to the connection string via custom attributes specified in the user definition or dynamically in the custom attributes specified in the SAML or LDAP configurations for your Composer installation.
You can also specify user attributes for use in the connection parameters of a connection definition. See Using User Attributes for Connection Parameters.
Step 1: Define Custom Attributes for the Variables
A custom attribute must be defined for every variable you want to use. The only exceptions are the Composer context variables${User.composerUserName}
and ${User.accountId}
, which automatically exist and can be used to insert the name or account ID of the user that is currently logged in.
You can define custom attributes in several ways:
- Individually for every user definition. If you use this method, the variable names must be the same for every user. See Specifying Custom User Attributes.
- Dynamically in the LDAP or SAML configurations for your Composer instance. See Using Lightweight Directory Access Protocol (LDAP) With Composer and Configuring Composer to Support SAML.
Details about specifying custom attribute values are provided in Specifying Custom User Attributes.
Step 2: Define Connections Using Variables
To define connections using variables:
Log into Composer as an administrator.
Create or edit a connection definition. See Adding Data Store Connections and Modifying Data Store Connections.
If custom attributes have been defined, they can be directly entered in a connection parameter box on the Connections page using the following syntax:
${User.<custom-attribute-name>}
When custom attributes are referenced in connection definitions they take the form
User.<custom-attribute-name>
.Select
to validate the connection. If the connection is valid, it is saved.
Comments
0 comments
Please sign in to leave a comment.