Setting the owner on sources and workflows

[josephcasale]

I have created a source and an identity profile for use as machine accounts etc.

I hoped to assign one of the users as the owner on several sources and workflows.

However, the identities don’t appear in the drop downs.

Might that be because none of them have a lifecycle state mapped or configured?

[sidharth_tarlapally (TARLAPALLY SIDHARTH)]

Hi @josephcasale,

I don’t think that’s the reason—I’m able to view identities in my tenant even when the Identity Profiles don’t have LCS configured.

Would you mind sharing how you created the source for these machine accounts, and what attribute mappings you’ve configured in the Identity Profile?

Appreciate your insights—thank you!

[kdfreeman (Kapil Dahal)]

Hi @josephcasale ,

You can also manually update source and workflow json and include the owner there.

For example, the owner in workflow is saved in workflow JSON as follows: You can update it.

  "owner": {
      "type": "IDENTITY",
      "id": "provide identity id",
      "name": "provide sailpoint username"
    }

Same info can be updated in source.

Thanks.

[josephcasale]

Hi @sidharth_tarlapally ,
I created a generic flat file source and an identity with that source selected.

I have the following attribute mapped corresponding identity attribute:

• id
• name
• displayName
• comments
• email
• familyName
• givenName

I believe this is similar to the identitynow admins.

[sidharth_tarlapally (TARLAPALLY SIDHARTH)]

@josephcasale

were you able to see the identity in the identities page ?

[josephcasale]

Yes, sorry about omitting that, I can also log in as the identity.

Looking at what the options are in the owner dropdown, it appears it only enumerates identities from the Identitynow Admins profile.

[josephcasale]

The user was missing the necessary permissions.

It appears that only an admin can own a workflow…