Unannounced Change in Source Technical Name Format Impacting BP Rules

Identity Security Cloud (ISC) ISC Discussion and Questions
, , , ,
1

Hello Team,

We’ve identified an unannounced change in the format of source technical names that has impacted our recent Salesforce deployment.

:counterclockwise_arrows_button: Change Overview:

  • Previous Format: sourceName [source]

  • New Format: sourceName [source-unique-identifier]
    (Note: The unique identifier is not the source ID)

:pushpin: Scope of Impact:

  • Affected: All new source deployments/configurations

  • Unaffected: QA tenant remains stable due to pre-existing source configurations

Impact:

1. Integration Dependencies

  • Our Salesforce integration relies on referencing delimited source names via BP rules during access provisioning and de-provisioning. The format change disrupts this dependency on new deployments.

2. BP Rule Integrity

  • BP rules reference sources by their technical name. The format change leads to:
    • Broken object references, causing BP rule functionality to diverge from documented behavior
  • The change creates a problematic scenario where QA environments function correctly while production deployments fail, making it difficult to validate configurations before go-live.

We have raised a informational support ticket with SailPoint, to confirm the issue.

2

We have deployed the updated BP rule with new format and this seem to have worked and is currently functioning as expected

ie. sourceName [source-unique identified] not source id