# Integrating SailPoint with BMC Remedyforce

The SailPoint BMC Remedyforce source has been extended and tested to support the BMC Helix platform. The information contained in this guide can be used while working with either of these target systems.

SailPoint's BMC Remedyforce and BMC Helix sources offer a complete access management of accounts and groups contained in a BMC Remedy action request system.

If you have user accounts in BMC Remedyforce that you want to load into SailPoint, you can create a direct connect source for BMC Remedyforce 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. For more information about identity profiles and correlation, refer to [SailPoint Identity Services](<https://documentation.sailpoint.com/saas/help/index.html>).

> [!NOTE]
>
> To configure a BMC Remedyforce source for provisioning, follow the instructions in this guide. If further assistance is required, you may work with [Support](<https://community.sailpoint.com/knowledge/collection/working-with-services>).

> [!NOTE]
>
> To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes](<https://community.sailpoint.com/release-notes/saas>) page.

## Supported Features

> [!NOTE]
>
> Before you can use any item marked with an asterisk (\*), SailPoint must activate the feature for your site.

SailPoint's BMC Remedyforce source supports the following features:

- Load and \*provision Remedyforce Accounts
- \*Access Certifications (certification of entitlements connected to accounts)
- \*Password management

For more information on features, refer to [Source Features](<https://community.sailpoint.com/knowledge/Identity-Security-Cloud-Source-Features>).

### Direct Permissions

The BMC RemedyForce source supports reading direct permissions for Group Profiles.

Perform the following steps to enable direct permissions:

1. Use the [listSources](<https://developer.sailpoint.com/docs/api/list-sources-v-1/>) API to get the source ID for your source.
2. Use the [listSchemas](<https://developer.sailpoint.com/docs/api/get-source-schemas-v-1/>) API to get the schema ID for the account or group schema for which you want to enable direct permissions.
3. Use the [updateSchema](<https://developer.sailpoint.com/docs/api/v3/update-source-schema/>) API and enter the following content in the body.

   Method: PATCH

   ```text
   URI: /beta/sources/<source-id>/schemas/<group-profile-schema-id>
   {

   "op": "replace",

   "path": "/includePermissions",

   "value": true

   }
   ```
4. Execute the entitlement aggregation to fetch the Direct Permissions associated to the corresponding Group Profile. By default, the Direct Permissions feature is not enabled on the source. You must enable it explicitly.

### 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](<https://documentation.sailpoint.com/saas/help/pwd/index.html>).

## Prerequisites

- Configure at least one virtual appliance cluster and successfully test the connection. For more information, refer to the [Virtual Appliance Reference Guide](<https://documentation.sailpoint.com/saas/help/va/index.html>).