Connecting SailPoint and Linux
To connect SailPoint with Linux, perform the following tasks:
Adding the Source in SailPoint
To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs.
Important
By default, the provisioning feature is disabled, and the connector only supports read-only operations. To support provisioning operations, you must manually enable the feature in the source configuration.
To configure a new source:
- Sign in to SailPoint.
- Go to Admin > Connections > Sources.
- Select Create New.
- Search for the connector by entering the name in the search box, and then select Configure.
- In the Source Name field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters.
- In the Description field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters.
- In the Source Owner field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to Assigning a Source Owner.
-
Under Connection Type, select Direct Connection or Flat File.
- Direct Connection - A direct connection fetches data from the Virtual Appliance Cluster you choose as the application connector for the source. A direct connection configuration allows for real-time updates. For more information about configuring and deploying virtual appliances, refer to the Virtual Appliance Reference Guide.
- Flat File - Select the flat file if no connector is available, or if another system restricts the connection. This option allows only reading and aggregating data as a generic/delimited application. Provisioning activity is unsupported, and additional configuration pages like connection settings and aggregation settings are unavailable.
-
If you selected Direct Connection, in Virtual Appliance Cluster, select the virtual appliance cluster that will be used as the application connector for the source.
- (Optional) Select a governance group to grant its members source or role sub-admin level oversight of the source and its access. For more information, refer to Creating and Managing Governance Groups.
- If this source represents a primary system containing your organization's personnel records, select the Authoritative Source checkbox. For more information, refer to Creating Identity Profiles.
- Select Continue. The source is created, and you are navigated to the Source Setup > Base Configuration page. Continue to configure your connected source there.
Base Configuration
Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary.
- Enter a unique name and description for the source.
-
In the Source Owner dropdown list, select the identity that owns this source.
- To find a source owner, begin entering their name.
-
In the Virtual Appliance Cluster dropdown list, select the virtual appliance to use when communicating with your organization's systems. For more information, refer to SailPoint Virtual Appliances.
-
(Optional) If enabled for your organization, select the Use a Credential Provider checkbox to manage the source's authentication using a credential provider.
Note
To add a credential provider, go to Admin > Connections > Credential Providers. For more information about credential providers, refer to Credential Providers.
-
Configure the authentication to allow SailPoint to connect to the source. Refer to Connection Settings for more information.
-
(Optional) In the Governance Group for Source Management dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to Associating Governance Groups with a Source.
-
(Optional) Choose whether to enable or disable provisioning for the source. Provisioning is disabled by default.
-
Enable Provisioning - Set the toggle to Enabled to allow the source to create, update, and deactivate accounts in the connected source system.
-
Disable Provisioning - Set the toggle to Disabled to disable provisioning for the source. Disabling provisioning will prevent the creation, updating, or deactivating of accounts on this source.
-
-
Select Save.
Connection Settings
This section contains the information that the source uses to connect to and authenticate with the Linux managed system. After you select Connection Settings, the following page displays.
- In the Unix Server Host field, enter the Hostname/IP address of the computer.
- In the SSH Port field, enter the configured SSH port. Default value:
22. -
In the Username field, enter the User ID of the machine conducting connector operations.
If the specified User ID is not a root user, select the Sudo User checkbox.
-
In the Password field, enter the associated password for the User ID.
- (Optional) In the Set Prompt field, enter the prompt that must be set up on the Linux system.
-
(Optional) In the SSH Shell field, enter the Linux Shell on which operation must be performed.
Note
The default command for setting the shell prompt on the UNIX computer is:
<entry key="SetPrompt" value="PS1='SAILPOINT>'"/>If the command for setting a shell prompt is different than the default command, change the value of the source attribute.
Note
- The Linux source is enhanced to prevent shell injection attacks.
- For the Linux source, if the wrong re-enter password is configured in the debug, a wrong password entry prompts an error message along with the end user's password on the UI and in the log files. Previously, these sources did not display passwords on the UI or in the log files.
Additional Settings
This section contains the information that the source requires to configure the other required parameters. After you select Additional Settings the following page displays.
- The Linux source only supports the SFTP file transfer protocol used during aggregation.
-
Enter the command as follows to enable the account:
passwd -u -
In the Get Lock Status Command field, set the command used to get the status of all locked user accounts.
Default:
pam_tally2 | awk '{print $1} {print $2}' -
In the Get Login Limit Command field, set the command used to get the count limit of user logins.
Default:
cat /etc/pam.d/system-auth -
In the Unlock Account Command, set the command used to unlock a user account.
Default:
pam_tally2 -u -
In the Get Account Failed Login Count Command field, set the command used to obtain the count for failed login accounts.
Default:
pam_tally2
Note
The Linux source allows you to change the disable account attribute value to the usermod -s /bin/false command.
Disable Accounts Password Change
In the Linux source, you can deny change password operations for disabled accounts. You can reject the password change if the account is locked.
You can use the REST API to enable the denychangepassword attribute for a disabled account as follows:
POST <url>/api/source/update/<sourceID>
where:
<url>is the URL for the customer's SailPoint instance<sourceID>is the Source ID (number) obtained through the UI
In the body of the POST, use the form-data as follows:
- Key -
connector_denyChangePasswordForDisabledAccount - Value -
true
Review and Test
Perform a test to confirm the connection to SailPoint.
- Go to Review and Test.
-
Confirm that the entries in each field are correct.
If you note any mistakes, return to the section and make corrections.
-
Select Test Connection.
SailPoint Application Onboarding
SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to Discovered Applications in the SailPoint user interface.
For more information, refer to Application Onboarding in the SailPoint SaaS documentation.
Documentation Feedback
Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.

