# SailPoint Cerner Healthcare Connector Documentation > Cerner Healthcare Connector Documentation # Documentation # Connecting SailPoint and Cerner Healthcare To connect SailPoint with Cerner Healthcare, 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. ## Connection Settings Provide the information required to connect and interact with the source. > [!NOTE] > > **Screenshot** > > [![Connection Settings]()]() To configure your source connection, complete the following: 1. Enter the **Host URL** of the provisioning servlet. The provisioning servlet enables the SailPoint Cerner Healthcare source to communicate with Cerner through SPML calls. For example: `http:///security-provisioning/ProvisioningServlet` 2. Enter the **Millennium Target ID** with the required permission to perform provisioning on Cerner. The Millennium Target ID must be created and considered to be a service account used by the Cerner Healthcare source. You must get the Millennium Target ID from Cerner using some form of service request. For example: `millennium_xxxxxx` 3. Select **Save**. ## Aggregation Settings Provide the settings for your aggregation. > [!NOTE] > > **Screenshot** > > [![Aggregation Settings]()]() To configure your aggregation settings, complete the following: 1. Select an option from the **Manage Accounts** dropdown menu to aggregate users by user status. The available choices are: - Active and Suspended - Active - All 2. Enter the **Aggregation Timeout** in seconds. If the system reaches the aggregation timeout, it stops the aggregation attempt. The timeout setting is required if the response is getting delayed from the Cerner system. By default, timeout is set to 900 seconds. 3. Select **Save**. ## Advanced Settings The **Advanced Settings** tab lists additional configuration options available in the Cerner Healthcare connector. > [!NOTE] > > **Screenshot** > > [![Advanced Settings]()]() To configure advanced settings, complete the following: 1. Clear the **Disassociate Account** checkbox to only remove the User Name and not disassociate an account. 2. Specify a custom **Delimiter** for separating ID and names during provisioning operations. The default is `#~#`. 3. Specify the **HTTP Client Connection Timeout** in minutes. 4. 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 Cerner Healthcare > [!NOTE] > > **Integration** > > This is an integration and requires additional licensing or subscriptions to utilize it. For more information, contact your customer success manager. Cerner Corporation is a global supplier of health care information technology (HCIT) solutions, services, devices, and hardware. Cerner solutions optimize processes for health care organizations. This document is designed to give specific information about the requirements and field definitions needed to get a working instance of a Cerner Healthcare connector. This document is intended for the Cerner Healthcare source and SailPoint System Administrators and assumes an advanced level of technical knowledge. > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features The Cerner Healthcare connector supports the following features: ### Account Management - Aggregate and refresh accounts - Create, update, and delete accounts - Enable or disable accounts - Change account passwords - Add or remove entitlements (position and organization groups) ### Account - Group Management - Aggregation ## Prerequisites The Cerner Enterprise Provisioning Service exposes the provisioning mechanism to external requests and responses using the SPML (Service Provisioning Markup Language), which is a standard Cerner Millennium provisioning language. Through this service, it's possible to support external provisioning solutions to create and maintain users. > [!NOTE] > > These details are provided by Cerner to individual customers. As a result, these details may vary between customers. The following details are required: - Configure at least one virtual appliance cluster and successfully test the connection. For more information, refer to the [Virtual Appliance Reference Guide](). - **Provisioning Servlet** - The Cerner connector accesses the provisioning servlet URL, a customer-specific enterprise provisioning service to perform all the aggregation and provisioning related operations. - **Target ID** - Along with the servlet, a customer-specific Millennium Target ID is required for SailPoint to connect to the Cerner Provisioning adapter (through Cerner API's access). - **Permissions** - The Cerner provisioning adapter requires one Millennium account having Manage Accounts privilege, which modifies the users within Millennium. The service account is mapped to Millennium Target ID, which is required to make calls to the provisioning adapter. All the above prerequisites are mandatory as Cerner does not define users having the authority to send requests in any method. > [!IMPORTANT] > > To receive support from SailPoint Support, you must provide access to the Cerner test or development environment. # Provisioning The Cerner Healthcare connector supports provisioning, allowing you to create and manage accounts and entitlements in Cerner Healthcare 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. > [!NOTE] > > The `confidentialityLevel` attribute must be configured in the new application provisioning policy with the following details: > > - Type as String > - Review required > > For better governance, ensure that the value of the `confidentialityLevel` attribute is the same as the managed system. ## Default Create Account Attributes The following table lists the provisioning policy attributes for Create Account: | Account Attribute | Description | | --- | --- | | username | The user name associated with the account. The value of the user name field must be unique within the target Cerner Millennium domain `[1-48 characters]`. | | password | The password for the user account. Any value, assuming that value meets all criteria defined in the Cerner Millennium password policy maintained in AuthView. The password is only required when the user being provisioned is a non-LDAP user (when the user will authenticate against the Cerner Millennium user directory). | | first name | Given (first) name for the personnel. | | lastname | Surname (last name) for the personnel. | | confidentialityLevel | The confidentiality level set for organization or organization groups. | ## Update Account Attributes The following table lists the provisioning policy attributes for Update Account: | Account Attribute | Description | | --- | --- | | confidentialityLevel | The confidentiality level set for organization or organization groups. | ## Dormant Account Support If you want to remove the user name and not disassociate an account, clear the **Disassociate Account** checkbox on the [Advanced Settings]() page. To remove the user name, configure the following attribute in the provisioning policy: `` If you set the attribute to `true`, the source removes the user name and disassociates the account from personnel. This disassociated user name can then be assigned to any other account. ## Additional Provisioning Attributes The following are additional provisioning attributes: | Account Attribute | Description | | --- | --- | | personnelAlias | To provision `personnelAlias` through the update account provisioning policy, enter the input format for the attribute as follows: `beginEffectiveDateTime=2021/10/01#~#endEffectiveDateTime=2100/12/30#~#alias=677001#~#type=DOCDEA#~#aliasPool=DEA` | | credential | To provision `credential` through the update account provisioning policy, enter the input format for the attribute as shown in the following example: `name=BLS#~#type=Certificate#~#renewalDateTime=2035/01/01#~#state=NY#~#beginEffectiveDateTime=2021/10/01#~#endEffectiveDateTime=2100/12/30#~#addToNameIndicator=true` | | address | To provision `address` through the update account provisioning policy, enter the input format for the attribute as shown in the following example: `streetAddr=1200 Northside Forsyth Dr#~#streetAddr2=Times Square#~#addressTypeCd=Business#~#state=NY#~#city=Cumming#~#zipCode=30041#~#beginEffectiveDateTime=2021/10/01#~#endEffectiveDateTime=2100/12/30` | | phone | To provision `phone` through the update account provisioning policy, enter the input format for the attribute as shown in the following example: `phoneNumber=0001112222#~#phoneType=Business#~#phoneFormat=FreeText#~#extension=09#~#description=A phone number#~#beginEffectiveDateTime=2021/10/01#~#endEffectiveDateTime=2100/12/30` | | roleProfile | To provision `roleProfile` through the update account provisioning policy, enter the input format for the attribute as shown in the following example: `position=0001112222#~#display=Displayname#~#beginEffectiveDateTime=2021/10/01#~#endEffectiveDateTime=2100/12/30` | # 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 Cerner Healthcare 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. ### 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 | | --- | --- | | ID (numeric) | Account | | Id | Group | | Id | organizationGroup | ### Account Attributes The Cerner Healthcare 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 | | --- | --- | | ID | Identifies an object that exists on a target that is exposed by a provider. This is an Account ID which must not be changed. | | username | The user name associated with the account. The value of the user name field must be unique within the target Cerner Millennium domain. Can be any value between 1 and 48 characters. | | directoryIndicator | Contains an indicator on whether the user is an LDAP directory user or not. Values: True (LDAP user), False (non-LDAP user). | | birthdate | Personnel's birthdate. | | firstname | Personnel's first name. | | lastname | Personnel's surname (last name). | | middleName | Personnel's middle name. | | displayName | Personnel's display name. | | suffix | Personnel's suffix. | | privilege | Privileges assigned to the Cerner account. | | gender | A coded value representing the gender of the personnel. | | restriction | A restriction to be assigned to or unassigned from the account. | | title | Personnel's title (or list of titles). For example, Dr., Mrs., or Mr. | | physicianInd | An indicator if the personnel is a physician or not. | | position | A coded value representing the position assigned to the personnel that is treated as a Group entity. | | beginEffectiveDateTime | Date and time at which the personnel becomes or became effective. | | endEffectiveDateTime | Date and time at which the personnel ceases or ceased to be effective. | | organization Group | When a personnel record is unassigned from an organization group, all organizations in the group are also unassigned from the personnel record, unless they are associated to another organization group that is still assigned to the personnel. It is a read-only field and data is displayed during account aggregation. | | confidentialityLevel | A coded value representing the confidentiality code that applies to the relationship. | | personnelAlias | Personnel alias information. | | personnelGroup | Contains personnel group information. | | credential | Credentials are used to highlight the level of education and specialty of a care provider. | | email | Personnel's email address. | | roleProfile | Role profile information with multiple positions that applies to the relationship. For an already existing source, the user must add the `roleProfile` attribute [manually](<#adding-a-roleprofile-schema-attribute>). | #### Adding a Roleprofile Schema Attribute 1. In the Account Management section, select **Account Schema**. 2. Select **Add New Attribute**. The Add Attribute window appears. 3. Enter the following details: - **Name**: `roleProfile` - **Type**: string - **Description**: Contains role profile information - **Attribute Property**: Multi-Valued 4. Select **Save** to apply the changes. #### Including Permissions in Account Schema When permissions are aggregated (for example, when `includePermissions="true"` is set to true in the account schema definition and the `privilege` attribute is included in the account schema), the permissions are aggregated under the `directPermissions` attribute, not the `privilege` attribute itself. This data is not visible in the UI but is included in the link or identity XML/JSON. ## 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 Cerner Healthcare 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 | | --- | --- | | ID | The Id of the group. This is an Account ID which must not be changed. | | Display | Display name of the group. | ### Default Organization Group Attributes | Attribute Name | Description | | --- | --- | | Id | Unique identifier of the organization group. This is an Account ID which must not be changed. | | Display | Display name of the 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]() ## An Error Message Is Displayed While Performing the Operations The following error message is displayed while performing the operations: `xml.soap.SOAPException: Read timed out" OR "call: Connection Refused: connect` **Resolution**: Ensure that the Cerner server is up and running. ## Aggregation Task Fails with an Error Message The aggregation task fails with the following error message even when the test connection is successful: `An error has occurred retrieving user: XXXXXXX` **Resolution**: Verify the read and write privileges for the Cerner Administrator account provided in the application configuration. ## Insufficient Privileges Displayed in the Managed System Due to Authorize Server Not Running in the Domain If insufficient privileges are displayed in the Managed System for a particular account and the domain server is not available, then the permissions of the account are disabled. This issue is related to the Authorize server not running in the domain. This is caused by an issue with the server controller service. **Resolution**: Perform the following to cycle the Millennium domain and resolve the issue: - Run `mbt -ctrl` to verify if there were no orphaned processes. - Run `mbs -ctrl` to restart. ## An Error Message Appears During Aggregation During group aggregation the following error message may appear: `"Exception during aggregation of Object Type Group on Application CernerOLD. Reason: sailpoint.connector.ConnectorException: Group Aggregation failed : [Unable to unmarshall request, error: Unexpected end of element {urn:cerner:xmlns:security-provisioning:refData}:refData]"` **Resolution**: Ensure that the **position** account schema attribute is set to **group** instead of **string**. ## Some Accounts Are Missing in the Account Aggregation Process of the Cerner Connector **Resolution**: In the application settings, set the Manage Accounts filter to All and remove the following `customCharSet` entry from the application.xml file: ```xml Z=Z z=z ```