# SailPoint Oracle Solaris Connector Documentation > Oracle Solaris Connector Documentation # Documentation # Connecting SailPoint and Oracle Solaris To connect SailPoint with Oracle Solaris, 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:** 1. Sign in to SailPoint. 2. Go to **Admin \> Connections \> Sources**. 3. Select **Create New**. 4. Search for the connector by entering the name in the search box, and then select **Configure**. 5. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters. 6. 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. 7. 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](). 8. 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. 9. 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. 10. (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](). 11. 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](). 12. 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. 1. Enter a unique name and description for the source. 2. In the **Source Owner** dropdown list, select the identity that owns this source. - To find a source owner, begin entering their name. 3. 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](). 4. (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](). 5. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information. 6. (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](). 7. (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. 8. Select **Save**. ## Connection Settings Provide the information required to connect and interact with the source. > [!NOTE] > > **Screenshot** > > [![Connection Settings]()]() 1. Enter the Solaris **Unix Server Host** name or IP address that is managed by the source. 2. Enter the **Solaris SSH Port** number used for SSH communication. The default is port 22. 3. Enter the **Username** and **Password** of the sudo or root user that has the necessary permissions, as noted in [Required Permissions](). 4. Select the **Sudo User** checkbox if the user account is not the root user. 5. (*Optional*) Enter the **Set Prompt** to set the source shell prompt. 6. (*Optional*) Enter the **SSH Shell** that is present on the Solaris system. 7. Select **Save**. ## Additional Settings Configure the file transfer protocol you want to use for aggregation operations. > [!NOTE] > > **Screenshot** > > [![Additional Settings]()]() 1. Select one of the following: - **SFTP** uses the Secure File Transfer Protocol for aggregation operations. This is the default. - **SCP** uses the Secure Copy Protocol for aggregation operations. 2. Select **Save**. ## Review and Test Perform a test to confirm the connection to SailPoint. 1. Go to **Review and Test**. 2. Confirm that the entries in each field are correct. If you note any mistakes, return to the section and make corrections. 3. 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. # Integrating SailPoint with Oracle Solaris > [!IMPORTANT] > > SailPoint has announced the deprecation of the Oracle Solaris SailPoint connector. For more information, refer to [Oracle Solaris Connector Deprecation Announcement on SailPoint](). Effective January 1, 2025, the Oracle Solaris Connector will enter its deprecation period. > > - During this time, existing Oracle Solaris sources will continue functioning as expected, but no new enhancements, bug fixes, or support will be provided. > - Customers will not be able to create new sources in SailPoint for Oracle Solaris. > - The End-of-Life (EOL) date for the Oracle Solaris connector is January 1, 2026, at which point all existing sources utilizing this connector will cease to operate. > > To learn more about SailPoint's deprecation and EOL policies, refer to [SailPoint Support Policy for Connectivity](). This document is designed to give specific information about the requirements and field definitions needed to get a working instance of an Oracle Solaris source in SailPoint. If you have user accounts in a Solaris source that you want to load into SailPoint, create a direct connect source for Solaris and load that data into your system. To manage that data, either create an [identity profile]() based on the source or verify that the accounts you load are [correlated]() to an existing identity. > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features SailPoint's Oracle Solaris source supports the following features: ### Source Features - Load and \*provision accounts - \*Password management - \*Access certifications (certification of entitlements connected to accounts) - Aggregate the last login details - Enhanced to prevent shell injection attacks - Allows changes to the `disable.account` attribute value to use the `usermod -s /bin/false` command to disable users - Supports MD5, SHA-1, and SHA-2 cryptographic hash functions > [!NOTE] > > Before you can use any item above marked with an asterisk (\*), SailPoint must activate the feature for your site. ### Password Management If Password Management is enabled for your organization, you can change the password for a user of the source. After enabling password management on the source, be aware of the following: - The password policy defined in SailPoint applies to accounts on this source. - If you change the password for an application connected to this source, the change will automatically be made to the source itself. For more information on configuring password management, refer to [Password Management Overview](). ## Supported Managed Systems SailPoint supports the following Solaris versions: - Solaris 11.4 SPARC x86 ## Prerequisites - Configure at least one virtual appliance cluster and successfully test the connection. For more information, refer to the [Virtual Appliance Reference Guide](). - SSH should be installed on the Solaris computer. - To use sudo users for SailPoint operation, ensure that the required packages for executing sudo commands are installed on the managed system. - Sudo users and permissions for the Solaris source: - The admin user must have rights to execute the `/usr/bin/awk` command. - You must update the `/etc/sudoers` file entry for the admin user with the `/usr/bin/awk` command. - The user and group schema must add a new multivalued schema attribute as `sudoCommands` that collects all the necessary user commands and stores them as a part of the attribute. - If you want to aggregate the sudo commands from multiple sudo files, you must provide the list of files as a separate configuration attribute in the source config.xml file. For example: ```text ``` - The default command that collects the sudo commands is: `awk '/^[^#]/' /etc/sudoers`. In this command, the commented lines are skipped and the remaining content of the `/etc/sudoers` file is aggregated in a temporary file on the Solaris system. The temporary file on the Solaris system gets copied to the local SailPoint system and processes all the sudo user and group commands. If you want to use a custom command for aggregating file data, configure this command as part of the source config.xml file. For example: ```text [!NOTE] > > - If any part of the command is modified in the source XML, then the respective changes in the `/etc/sudoers` file entry should also be performed. Verify command paths on the Solaris systems as they might differ from the values mentioned here. > - If you want to use a sudo user to perform the provisioning operations, configure the home directory with proper write access for this sudo user. For example, if the sudo user is using the Guest home directory, then ensure it has proper write access over this directory. ## Read Only Permissions If you want to use a sudo user to perform read only operations, you must configure the sudo user with the following rights and permissions. **For Account Aggregation only** Rights to execute the following commands with root privilege: ```text /bin/echo, /bin/cat /etc/group, /bin/grep, /bin/rm -f spt_tmp_*, /bin/cat /etc/passwd, /bin/cat /etc/shadow, /bin/cat /etc/user_attr, /usr/bin/date, /bin/grep -i 'RETRIES=' /etc/default/login, /bin/grep -i 'Lock_After_Retries=' /etc/security/policy.conf ``` An entry in the `/etc/sudoers` file must look similar to the following: ```text username ALL = (root) PASSWD: /bin/echo, /bin/cat /etc/group, /bin/grep, /bin/rm -f spt_tmp_*, /bin/cat /etc/passwd, /bin/cat /etc/shadow, /bin/cat /etc/user_attr, /usr/bin/date, /bin/grep -i 'RETRIES=' /etc/default/login, /bin/grep -i 'Lock_After_Retries=' /etc/security/policy.conf ``` **For Entitlements Aggregation only** Rights to execute the following commands with root privilege: ```text /bin/echo, /bin/cat /etc/group, /bin/rm -f spt_tmp_*, /bin/grep ``` An entry in the `/etc/sudoers` file must look similar to the following: ```text username ALL = (root) PASSWD: /bin/echo, /bin/cat /etc/group, /bin/rm -f spt_tmp_*, /bin/grep ``` # Provisioning The Oracle Solaris connector supports provisioning, allowing you to create and manage accounts and entitlements in Oracle Solaris directly from SailPoint. **Prerequisite:** Your system is configured for provisioning. When SailPoint provisions new accounts to the source, it uses the attributes on the **Create Account** page as instructions or a template for what to include in the account. This page is also referred to as the *provisioning policy*. When new access is granted on a source where a user does not already have an account, SailPoint automatically includes account creation in the provisioning. This applies whether provisioning is started from an access request or from an automated role or lifecycle state assignment. For direct-connect sources, SailPoint automatically creates the account from this configuration. If the source is not configured as a direct-connect source, SailPoint creates and assigns a provisioning task to the source owner and includes the values for the source owner to use in manually creating the account. > [!IMPORTANT] > > This section describes the default **Create Account** configuration. SailPoint recommends that you work with Services to define a provisioning configuration specific to your company's needs. Be sure to verify large changes to the provisioning policy before implementation. Failure to do so might cause provisioning to fail. ## Default Create Account Attributes | Account Attribute | Generator | Description | | --- | --- | --- | | username | Create Unique Account ID | This generator uses the value in the **Pattern Used** field to generate a unique user name for the new account. | | password | Create Password | This generator creates an initial password for the new account that matches the password policy assigned to the associated Solaris source in SailPoint. | | uid | Disable | The numeric identity of a user. | | dupuid | Static | The duplicate identity of a user. | | primgrp | Disable | An existing group integer ID or character-string name. Without the `-D` option, it defines the new user primary group membership and defaults to the default group. You can reset this default value by invoking `useradd -D -g group`. GIDs 0-99 are reserved for allocation by the Solaris Operating System. | | home | Disable | The home directory of a user. | | shell | Disable | The default shell of a user. | | create\_home\_dir | Static | The creation of the home directory of a user. | | expire | Disable | Specifies the expiration date for a login. After this date, no user is able to access this login. The expire option argument is a date entered using one of the date formats included in the template `/etc/datemsk` file. If the date format that you choose includes spaces, the space must be quoted (" "). | | inactive | Disable | The maximum number of days allowed between uses of a login ID before that ID is declared invalid. Normal values are positive integers. A value of *0* defeats the status. | | lock\_after\_retries | Disable | Specifies whether an account is locked after a number of failed logins as defined by `RETRIES` in `/etc/default/login`. Possible values are *yes* or *no*. The default is *no*. Account locking is only applicable to local accounts and accounts in the LDAP name service repository, if configured with an `enableShadowUpdate` of `true` as specified in `ldapclient(1M)`. | | profile | Disable | An ordered, comma-separated list of profile names selected from `prof_attr`. Profiles are enforced by the profile shells `pfcsh`, `pfksh`, and `pfsh`. If no profiles are assigned, the profile shells do not allow the user to execute any commands. | | auths | Disable | One or more comma separated authorizations defined in `auth_attr`. Only a user or role that has grant rights to the authorization can assign it to an account. | | pwdwarn | Disable | The number of days, relative to max, before the password expires and the system issues a password expiration warning. | | pwdminage | Disable | The minimum number of days required between password changes for the user. `MINWEEKS` is found in `/etc/default/passwd` and is set to NULL. | | pwdmaxage | Disable | The maximum number of days the password is valid for the user. `MAXWEEKS` is found in `/etc/default/passwd` and is set to `NULL`. | | forcepwdchange | Static | Use this attribute to force the user to change their password on next logon. | | project | Disable | The name of the project that the added user is associated. | | comment | Disable | Any text string. It is generally a short description of the login, and is currently used as the field for the user's full name. This information is stored in the user's `/etc/passwd` entry. | # Schema Reference The application schema is used to configure the objects returned from a connector. > [!NOTE] > > - The **Account Schema** tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as **Entitlement** or **Multi-Valued**. Refer to [Managing Source Account Schemas]() for more information. > - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified. The Oracle Solaris connector uses the following default correlation and object configurations. ## Default Account Schema Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location. The set of account attributes each source stores and how they're organized is known as the account's *schema*. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to [Managing Source Account Schemas]() for more information. ### Default Account ID SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as *account IDs*. > [!CAUTION] > > Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts. > > To resolve issues caused by changing account IDs, reconfigure them to their default values. The following table lists the default account IDs for this connector: | Account ID | Schema Object Type | | --- | --- | | username | Account | | groupname | Group | ### Default Account Attributes The Oracle Solaris connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified. | Attribute Name | Description | | --- | --- | | username | The name of the user. This is an Account ID which must not be changed. | | uid | The Numeric ID for the user. | | primgrp | An existing group integer ID or character-string name. Without the `-D` option it defines the new user primary group membership and defaults to the default group. You can reset this default value by invoking `useradd -D -g group`. GIDs 0-99 are reserved for allocation by the Solaris Operating System. | | groups | Secondary groups of the user. The list of groups assigned to the user. | | roles | Contains the list of roles for each user. | | home | The home directory of the user. | | shell | The default shell of the user. | | comment | Any text string. It is generally a short description of the login and is currently used as the field for the user's full name. This information is stored in the user's `/etc/passwd` entry. | | auths | One or more comma separated authorizations defined in auth\_attr(4). Only a user or role who has grant rights to the authorization can assign it to an account. | | project | The name of the project with which the added user is associated. See the projname field as defined in project(4). | | expire | Specify the expiration date for a login. After this date, no user will be able to access this login. The expire option argument is a date entered using one of the date formats included in the template file `/etc/datemsk`. See getdate(3C). If the date format that you choose includes spaces, it must be quoted. For example, you can enter 10/6/90 or October 6, 1990. A null value (" ") defeats the status of the expired date. This option is useful for creating temporary logins. | | inactive | The maximum number of days allowed between uses of a login ID before that ID is declared invalid. Normal values are positive integers. A value of 0 defeats the status. | | lock\_after\_retries | Specifies whether an account is locked after the count of failed logins for a user equals or exceeds the allowed number of retries as defined by `RETRIES` in `/etc/default/login`. Possible values are *yes* or *no*. The default is no. Account locking is applicable only to local accounts and accounts in the LDAP name service repository if configured with an `enableShadowUpdate` of `true` as specified in `ldapclient(1M)`. | | limitpriv | The maximum set of privileges a user or any process started by the user, whether through su(1M) or any other means, can obtain. The system administrator must take ensure that when deleting the privileges from the limit set. Deleting any basic privilege has the ability of crippling all applications; deleting any other privilege can cause many or all applications requiring privileges to malfunction. | | defaultpriv | The default set of privileges assigned to a user's inheritable set upon login. | | profiles | Contains an ordered, comma-separated list of profile names selected from prof\_attr(4). Profiles are enforced by the profile shells, pfcsh, pfksh, and pfsh. See pfsh(1). A default profile is assigned in `/etc/security/policy.conf` (see policy.conf(4)). If no profiles are assigned, the profile shells do not allow the user to execute any commands. | | failedretries | Indicates if the user account is locked. Possible values include: **true**: The user account is locked. The values "yes", "true", and "always" are equivalent. The user is denied access to the system. **false**: The user account is not locked. The values "no", "false", and "never" are equivalent. The user is allowed access to the system. Default value. | | pwdminage | The minimum number of days required between password changes for user. MINWEEKS is found in `/etc/default/passwd` and is set to NULL. | | pwdmaxage | The maximum number of days the password is valid for user. MAXWEEKS is found in `/etc/default/passwd` and is set to NULL. | | pwdwarn | The number of days relative to max before the password expires and the name are warned. | | pwdlastchg | The date the password was last changed for the name. All password aging dates are determined using Greenwich Mean Time (Universal Time) and therefore can differ by as much as a day in other time zones. | | lastLogin | The last login time of the user on the Solaris computer. | | audit\_flags | Specifies per-user Audit pre selection flags as colon-separated **always-audit-flags** and **never-audit-flags**. For example, `audit_flags=always-audit-flags:never-audit-flags`. | ## Default Entitlement Attributes Entitlement attributes define the entitlements, such as groups or roles, that can be assigned to the managed system's user accounts. Refer to [Managing Entitlements]() for more information. > [!CAUTION] > > Changing the attribute marked as the Entitlement ID after aggregating accounts or entitlements can result in duplicate entitlements being created, or access profiles and roles breaking. To avoid this, edit the entitlement schema before performing any aggregations. ### Default Group Attributes The Oracle Solaris connector also supports groups. The following attributes must be configured on the managed system and in the SailPoint source schema to manage groups. | Attribute Name | Description | | --- | --- | | groupname | The name of the account group. This is an Account ID which must not be changed. | | groupid | The Numeric ID of the account group. | # Enable Connector Logging This topic provides the steps needed to enable logging on SailPoint using REST APIs. > [!NOTE] > > This topic only applies to VA-based integrations. > [!NOTE] > > The examples provided might not match your configuration. Use the logging levels and logging classes reference at the bottom of the topic to configure your API responses to match your connector. This process is broken up into four steps: 1. Identify the Virtual Appliance (VA) cluster on which you want to enable logging. 2. Get the logging configuration for the existing VA cluster. 3. Update the VA cluster to enable logging levels. 4. Observe logging changes to the logging levels. ### Identify the Virtual Appliance Cluster Select the VA on which you need to enable logging using REST API. If you already know the VA application's `id`, proceed to [Get the Logging Configuration](<#get-the-logging-configuration>). 1. Make the following call to the REST API to return a list of available VA clusters: GET /v3/managed-clusters The REST API returns a response that looks similar to the following: ```json [ { "id": "2c9180866166b5b0016167c32ef31a66", "name": "Development Cluster", "description": "Development Cluster", "clientType": "CCG", "ccgVersion": "373_535_70.2.0", "pinnedConfig": true, "logConfiguration": null }, { "id": "2c9180846a93ce60016ab29f039944de", "name": "Cloud Cluster", "description": "Cloud Cluster", "clientType": "CCG", "ccgVersion": "373_535_70.2.0", "pinnedConfig": true, "logConfiguration": { "clientId": null, "durationMinutes": 60, "expiration": "2020-12-15T19:13:36.079Z", "rootLevel": "DEBUG", "logLevels": { "sailpoint.connector.ADLDAPConnector": "DEBUG" } } } ] ``` > **Note** > > The previous example code shows two VA clusters. One VA cluster has a log configuration and the other does not (refer to the `logConfiguration` value in each returned VA cluster). This is because one of the clusters already has logging enabled. This is just an example configuration, and your environment may not have logging enabled on a cluster. 2. Identify the VA cluster that you want to enable logging on by its name or description and record its `id` attribute. ### Get the Logging Configuration Get your selected VA's cluster logging configuration and identify the values you need to update. 1. Make the following call to the REST API to return the VA cluster's logging configuration. Replace `{id}` with the VA cluster's `id` attribute value recorded earlier. GET /v3/managed-clusters/{id}/log-config - If the VA doesn't have a logging configuration currently set, it returns `204 No Content` as a response. - If the VA has an existing logging configuration, it returns something similar to the following: ```json { "clientId": null, "durationMinutes": 60, "expiration": "2020-12-15T19:13:36.079Z", "rootLevel": "DEBUG", "logLevels": { "sailpoint.connector.ADLDAPConnector": "DEBUG" } } ``` You'll need to configure the following information in the response: - `durationMinutes` is the number of minutes logging should remain enabled. - `rootLevel` is the default level for all logs. For more information, refer to [Logging Levels](<#logging-levels>). - `logLevels` is a map object with logging classes as keys and logging levels as values. - For keys, refer to [Logging Classes](<#logging-classes>) for commonly used logging classes. - For a list of available values, refer to [Logging Levels](<#logging-levels>). ### Update Logging Configuration Update the VA cluster configuration returned by the REST API to update the logging settings as needed. 1. Make the following call to the REST API to update the VA cluster's logging configuration. Replace `{id}` with the VA cluster's `id` attribute value recorded earlier. PUT /v3/managed-clusters/{id}/log-config 2. Submit your configuration changes to the REST API in a JSON body. - If the VA cluster did not already have a logging configuration and you received a `204 No Content` response, you can create a new one. - If the VA returned a configuration, you can edit it to include the changes. The JSON body should be as follows: ```json { "durationMinutes": 60, "rootLevel": "DEBUG", "logLevels": { "sailpoint.connector.ADLDAPConnector": "DEBUG" } } ``` Consider the following as you edit the JSON: - `durationMinutes` is the number of minutes logging should remain enabled. - `rootLevel` is the default level for all logs. For more information, refer to [Logging Levels](<#logging-levels>). - `logLevels` is a map object with logging classes as keys and logging levels as values. - For keys, refer to [Logging Classes](<#logging-classes>) for commonly used logging classes. - For a list of available values, refer to [Logging Levels](<#logging-levels>). If the update was successful, the REST API should return a response similar to the following: ```json { "clientId": null, "durationMinutes": 60, "expiration": "2020-12-15T19:13:36.079Z", "rootLevel": "DEBUG", "logLevels": { "sailpoint.connector.ADLDAPConnector": "DEBUG" } } ``` ### Observe Logging Changes Approximately five minutes after you update the configuration, the VA cluster starts generating log files you can review. You can view the log files in **ccg.log**. ### References The tables in this reference section list information that can be helpful when creating the JSON body you'll use to configure the VA cluster's configuration file. #### Logging Levels | Logging Level | Description | | --- | --- | | ERROR | Designates error events that might still allow the connector to continue. | | WARN | Designates potentially harmful situations. | | INFO | Designates information messages that highlight process at a coarse-grain level. | | DEBUG | Very verbose. Fine grain logging levels used for development and debugging. | | TRACE | Most verbose. Finer grain logging levels than debugging. | #### Logging Classes | Connector | Logging Class | | --- | --- | | Active Directory | sailpoint.connector.ADLDAPConnector sailpoint.connector.LDAPConnector | | AIX | openconnector.connector.unix.AIXConnector openconnector.connector.unix.UnixConnector | | Amazon Web Services | logger.aws.name=openconnector.connector.aws logger.aws.level=trace logger.aws.additivity = false logger.aws.appenderRef.rolling.ref = STDOUT | | Atlassian Suite Cloud | sailpoint.connector.OpenConnectorAdapter openconnector.connector.atlassian.AtlassianConnector | | Atlassian Data Center | sailpoint.connector.OpenConnectorAdapter openconnector.connector.atlassian.AtlassianDataCenterConnector | | Microsoft Entra ID | sailpoint.connector.AzureADConnector | | Box | openconnector.connector.BoxNetConnector sailpoint.connector.OpenConnectorAdapter | | Cerner | openconnector.connector.CernerConnector sailpoint.connector.OpenConnectorAdapter | | Delimited File | logger.DelimitedFileConnector.name = sailpoint.connector.DelimitedFileConnector logger.DelimitedFileConnector.level = debug logger.DelimitedFileConnector.additivity = false logger.DelimitedFileConnector.appenderRef.rolling.ref = STDOUT | | Dropbox | openconnector.connector.DropBoxConnector sailpoint.connector.OpenConnectorAdapter | | Epic | openconnector.connector.EPICConnector sailpoint.connector.OpenConnectorAdapter | | GE Centricity | openconnector.connector.GECentricity sailpoint.connector.OpenConnectorAdapter | | Google Apps / G Suite | openconnector.connector.GoogleAppsDirect sailpoint.connector.OpenConnectorAdapter | | IBM i | openconnector.connector.IBMiConnector | | Lotus Domino | sailpoint.connector.LotusDomino | | JDBC | sailpoint.connector.JDBCConnector | | Sun One LDAP | sailpoint.connector.LDAPConnector | | Linux | openconnector.connector.unix.LinuxConnector sailpoint.connector.OpenConnectorAdapter sailpoint.connector.UnixConnector | | Microsoft Office365 | sailpoint.connector.Office365Connector | | Microsoft SQL Server | sailpoint.connector.mssql.serviceimpl.MSSQLServerConnectorV2 | | Okta | logger.openconnector.name = openconnector.connector.okta.OktaConnector logger.openconnector.level = debug logger.openconnector.additivity = false logger.openconnector.appenderRef.rolling.ref = STDOUT | | Oracle Database | sailpoint.connector.OracleDBConnector sailpoint.connector.JDBCConnector | | Oracle E-Business | sailpoint.connector.OracleEBSConnector sailpoint.connector.JDBCConnector | | Oracle Fusion HCM | openconnector.connector.oraclefusionhcm.OracleFusionHCMConnector sailpoint.connector.OpenConnectorAdapter | | Oracle HCM Cloud | sailpoint.connector.oraclehcmcloud.OracleHCMCloudConnector | | Oracle HRMS | sailpoint.connector.OracleAppsHRMSConnector sailpoint.connector.JDBCConnector | | Oracle Netsuite | openconnector.connector.netsuite.NetsuiteConnector | | PeopleSoft ERP | openconnector.connector.PeopleSoftConnector sailpoint.connector.OpenConnectorAdapter | | PeopleSoft HRMS | sailpoint.connector.PeopleSoftHRMSConnector | | RemedyForce | sailpoint.connector.ForceConnector | | RSA Authentication Manager | openconnector.connector.RSAConnector openconnector.connector.rsa.RSAHTTPClient sailpoint.connector.OpenConnectorAdapter | | Salesforce | sailpoint.connector.ForceConnector | | SAP Concur | openconnector.connector.sapconcur.SAPConcurConnector | | SAP - Direct | sailpoint.connector.SAPConnector sailpoint.connector.SAPInternalConnector | | SAP GRC | logger.SAPGRCConnector.name = sailpoint.connector.sapgrc logger.SAPGRCConnector.level = debug logger.SAPGRCConnector.additivity = false logger.SAPGRCConnector.appenderRef.rolling.ref = STDOUT | | SAP HR/HCM | sailpoint.connector.SAPHRInternalConnector | | SCIM 1.1 | openconnector.connector.SCIMConnector sailpoint.connector.OpenConnectorAdapter | | SCIM 2.0 | openconnector.connector.scim2.SCIM2Connector sailpoint.connector.OpenConnectorAdapter | | ServiceNow | openconnector.connector.servicenow.ServiceNowConnector openconnector.connector.servicenow.ServiceNowRestClient sailpoint.connector.OpenConnectorAdapter | | ServiceNow Service Desk Integration | openconnector.connector.servicedesk.ServiceNowServiceDeskConnector sailpoint.connector.OpenConnectorAdapter | | Siebel | openconnector.connector.SiebelConnector sailpoint.connector.OpenConnectorAdapter | | Snowflake | openconnector.connector.snowflake.SnowflakeConnector sailpoint.connector.OpenConnectorAdapter | | Solaris | openconnector.connector.unix.SolarisConnector openconnector.connector.unix.UnixConnector sailpoint.connector.OpenConnectorAdapter | | SuccessFactors | sailpoint.connector.SuccessFactorsConnector | | Sybase | sailpoint.connector.SybaseDirectConnector sailpoint.connector.JDBCConnector | | Webex | openconnector.connector.Webex sailpoint.connector.OpenConnectorAdapter | | Workday | openconnector.connector.WorkDay sailpoint.connector.OpenConnectorAdapter | | Workday Accounts | openconnector.connector.workdayaccounts openconnector.connector.workdayaccounts.WorkdayAccountsConnector sailpoint.connector.OpenConnectorAdapter | | Web Services | sailpoint.connector.WebServices | | XML | openconnector.connector.XMLConnector sailpoint.connector.OpenConnectorAdapter | | Yammer | openconnector.connector.YammerConnector sailpoint.connector.OpenConnectorAdapter | | Zoom | openconnector.connector.zoom.ZoomConnector sailpoint.connector.OpenConnectorAdapter | # Troubleshooting If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support. For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information: - [SailPoint Identity Services Documentation]() - [SailPoint Support Knowledge Base]() - [SailPoint Developer Community]() > [!NOTE] > > For more information on SailPoint's REST APIs, refer to [Best Practices: REST API Authentication]() and [REST API - Update Source (Partial)]() in the SailPoint Developer Community. ## Test connection Fails with an Error The following error message appears when test connection fails: ```text [InvalidConfigurationException] [Possible suggestions] Provide right credentials. [Error details] Failed to authenticate the ssh credentials for user: to the host: XXX.XX.XX.XXX ``` **Resolution**: Update `/etc/ssh/sshd_config` file for the following entry and restart sshd: `PasswordAuthentication yes` ## Aggregation Fails with an error The following error message appears when aggregation fails: ```text Exception during aggregation of Object Type account on Application Solaris. Reason: Unable to create iterator sailpoint.connector.InvalidResponseException: [InvalidResponseException] [Possible suggestions] Make sure standalone command works with the UNIX terminal. The standalone command is - cat /etc/group | grep -v '^+' | grep -v '^-' [Error details] Command failed. Status: 1, Output: sh: spt_tmp_groupsb257b857860c4518a5fcac11f789a133: cannot create [Permission denied] ``` **Resolution**: Create a home directory for the sudo user and run aggregation again. Ensure that the sudo user is able to create files in its home directory. ## Aggregation/Test Connection Fails with Timeout Error Aggregation/test connection fails with the following timeout error: ```text Exception during aggregation of Object Type account on Application Solaris. Reason: Unable to create iterator sailpoint.connector.TimeoutException: [TimeoutException ] [Possible suggestions] Tune the parameter . [Error details] Timeout occurred while reading output stream for the executed command. ``` Test Connection fails with following timeout error: ```text [TimeoutException] [Possible suggestions] Tune the parameter . [Error details] Timeout occurred while reading output stream for the executed command. ``` **Resolution**: Change the value of the `sshWaitTime` (in milliseconds) attribute per your requirement using the REST API. The default value is `500`. ## Timeout Error Occurs When Third-Party Software Is Installed There is a timeout error for the Solaris instances. If your Solaris system has third-party software (for example, Centrify) installed, then it does not display a custom prompt. > [!NOTE] > > If setting `sshWaitTime` does not solve the problem, connect to the Solaris machine using the sudo user to check the system's behavior. After executing the following command, it should prompt for `%SAILPOINTSUDO` where the user enters the sudo's password: ```text sudo -p %SAILPOINTSUDO echo TestConnection ``` However, because of third party software (for example, Centrify) that is installed on the Solaris system, it does not prompt for the `%SAILPOINTSUDO`, it displays a different prompt. In this case, the connector does not detect that it is asking for the sudo's password. For example, if the system prompts for the CSO Password. Then the source understands that it is a prompt for the sudo user's password. **Resolution**: Set the custom prompt in the `SudeoPassPrompt` attribute using the REST API. ## Aggregation Fails with an Error for Solaris The following error message appears when aggregation fails: ```text Exception during aggregation of Object Type account on Application Solaris. Reason: Unable to create iterator sailpoint.connector.InvalidResponseException: [InvalidResponseException] [Possible suggestions] Make sure standalone command works with the UNIX terminal. The standalone command is - date '+%m/%d/%Y %H:%M:%S' [Error details] Command failed. Cannot collect systems current date. Status: SAILPOINT>echo $? 0 ``` **Resolution**: Set the `DEFAULT_SSH_SHELL` attribute to the default shell, as set in the Solaris system using the REST API. The default value is `bash`. # Timeout Errors and Settings Timeout errors might occur when SailPoint is waiting for a response from the Virtual Appliance (VA). These errors are applicable to all connectors and tend to occur during the setup of sources or when sources are down. This document is designed to give specific information that can be used to resolve these errors. Each timeout attribute has a default time value that is listed in seconds or minutes. Increasing the time value may resolve the error as it will allow for longer communication time between the two systems, thus avoiding the timeout error. > [!IMPORTANT] > > Add the necessary attributes or values before performing the "replace" operation, as missing attributes will cause the operation to fail. To increase the communication time, increase the value of the appropriate timeout attribute. Then submit the change to the VA using the SailPoint REST API. > [!NOTE] > > For more information on SailPoint's REST APIs, refer to [Best Practices: REST API Authentication]() and [REST API - Update Source (Partial)]() in the SailPoint Developer Community. ### aggregateTimeout **Description:** This parameter is set for the aggregation timeout, measured in seconds. **Resolution:** Increase the `aggregateTimeout` value gradually to optimize aggregation. Start with 180, then increase to 600, 900, and finally 1800. The maximum value is 3600 seconds. For example: If your current time value is 180 seconds, update the `aggregateTimeout` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/aggregateTimeout", "value": 600 } ] ``` ### healthCheckTimeout **Description:** This parameter is set for the test connection and health check timeout. **Resolution:** The default value is 30 seconds. If the timeout error continues, increase the value in 15 second increments and try again. For example: If your current time value is 30 seconds, update the `healthCheckTimeout` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/healthCheckTimeout", "value": 45 } ] ``` ### provisioningTimeout **Description:** This parameter is set for provisioning timeout. **Resolution:** Increase the `provisioningTimeout` value gradually to optimize provisioning. Start with 180, then increase to 360, and finally 600. The maximum value is 600 seconds. For example: If your current time value is 180 seconds, update the `provisioningTimeout` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/provisioningTimeout", "value": 360 } ] ``` ### timeout **Description:** This parameter is set for pass-through authentication timeout. **Resolution:** The default value is 15 seconds. If the timeout error continues, increase this value in 15 second increments and try again. For example: If your current time value is 15 seconds, update the `timeout` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/timeout", "value": 30 } ] ``` ### apiTimeout **Description:** This parameter is set for API time tracking; customers can check it using an external tool. **Resolution:** The default value is 60 seconds. If the error continues, increase the value by 15 second increments and try again. For example: If your current time value is 60 seconds, update the `apiTimeout` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/apiTimeout", "value": "75" } ] ``` ### timeoutInSeconds **Description:** This parameter helps prevent the VA from waiting indefinitely for an API response, ensuring efficient handling of API requests. For example: If your current time value is 30 seconds, update the `timeoutInSeconds` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/timeoutInSeconds", "value": "15" } ] ```