Source Updated Event Trigger Not Always Firing

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

Just FYI for any DR folks reading, I opened up a support case on this (CS0242500) 22 days ago and there hasn’t been much progress.

I am wanting to use the Source Updated event trigger to take a snapshot/backup of a source config whenever it’s changed so I have that history.

Problem is, the event is only triggered on certain types of SOURCE_MANAGEMENT events. Examples:

  1. If I modify account/entitlement schemas, an event is fired

  2. If I modify something in the config, like the user search LDAP filter in an AD source, or modify the account query in a JDBC source, the event does not fire, despite there being a SOURCE_UPDATED audit event fired.

This shouldn’t be by design, right? The docs on the trigger seem to imply that it should fire on all source updates

image
image925×58 6.21 KB

2 Likes
2

We shared same concern, was told to add as idea on idea portal for future consideration, sadly.

1 Like
3

That is unfortunate. It seems my ticket is at least “awaiting engineering feedback”, so I hope I don’t have the same result.

I was hoping to get some input from the DR team like @colin_mckibben. Is it reasonable to expect that this event would fire the same way audit events do with the search query

type:SOURCE_MANAGEMENT AND operation:UPDATE

Specifically, the documentation says the trigger fires when configuration changes are made to a source, and not when SOME configuration changes are made to a source

4

Since support already has a query open with them, let’s see what engineering comes back with first.

5

FYI @tranetechnologies they confirmed it was a bug

Hello Mark,
The problem you noticed [Trigger not firing on all events - idn:source-updated] has been confirmed as a bug and notified to our Product Engineering. The issue will be getting internally tracked under Ticket → PLTCONN-3928

1 Like
6

Excellent, we will add to our list to track. Thanks for sharing!

7

Have there been any updates on the status of this bug with engineering? We’re running into similar, and also need this trigger to demonstrate to our auditors that sources aren’t modified inappropriately.

8

Honestly, I have no idea how one tracks bugs like this, but I haven’t heard anything back.

9

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.