Hello Everyone,
I’m looking for ways to use this created event attribute as an identity attribute for the target identity. Is it currently possible in ISC through any means or anyone has inputs?
Hello Everyone,
I’m looking for ways to use this created event attribute as an identity attribute for the target identity. Is it currently possible in ISC through any means or anyone has inputs?
Hi @varshini303,
You cannot pull the event search outputs through a transform.
What is the use case that you are trying to solve.? This may be achievable with a workflow.
Hi @jesvin90 ,
Our requirement is to include this password last changed detail for the identity. We are having a governance connector source and need to include this attribute in the source.
Unfortunately, our customer does not have license to workflow.
Yes, it’s possible — but with some constraints. In SailPoint Identity Security Cloud (ISC), event attributes (like those captured from triggers or workflows) are not directly persisted to the identity object by default. To use a value from an event as an identity attribute, you can pass it into a workflow and then update the identity using a PATCH call to /v3/identities/{id} with the desired attribute.
Alternatively, store the event value in a custom identity attribute via a transform if it can be derived during aggregation. This setup allows dynamic or event-driven attributes to be part of identity evaluation logic.
Hi,
Thanks for your input, I don’t think so we can update the identity attribute of an identity with such API, and we also do not have workflow license. We have created a custom identity attribute and we are frequently populating this as an account attribute (of Loopback connector source) through a scheduled script that derives values from the events.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.