Provisioning in Sequence

Lifecycle & Governance
, , ,
1

Hello All,

We have the below use case for Access Request :

1. Provision an account of App A with the attribute value of App B.

2. If App B is not found, first provision App B, then use the attribute value in App A provisioning.

We tried using “Application Dependencies” but somehow the provisioning policy is not able to fetch the App B during App A provisioning as I tried putting a logger in Create Policy.

Any way to achieve such use cases?

Thanks and regards.

2

Hello,

I understand your use case but I’d like to discuss it with you, I’m not sure it’s possible in a simple way.

  • Why would the attribute of app B be empty?
  • And how is the arribute of app B provisioned (identity attribute, calculated or other)?

Depending on your answer, we can discuss it, because I would have said to force the provisioning of app B in the provisioning policies with a fieldValue rule of application A so that the value would be put before in application B.
But that’s complex logic for simple provisioning and what happens if it fails for app B…

Let’s me know :slightly_smiling_face:

3

It’s a JDBC connector application (App A) who are relying on Mainframe ID to be available (App B) before provisioning to JDBC.

4

Try configuring it in a before provisioning rule of app A. If app B account does not exist for the user, then create it first via the before provisioning rule.

5

Thank you! this worked for us. Though, it would have been great if some OOTB solution was available :slightly_smiling_face: