Click HERE to see how Saviynt Intelligence is transforming the industry. |
07/05/2023 10:19 AM
Solved! Go to Solution.
07/05/2023 10:22 AM
When you launch the certification ,in Application section , select All (this way it will launch AO campaign for all applications where endpoint certifier is present with rank as primary certifier at endpoint level)
07/05/2023 10:34 AM
@dgandhi However, I don't want to launch it for all applications. There are specific applications that I'd like to launch for. Some of these are applications that are set up using the endpoint filter in the AD connection and some are disconnected applications.
For example: I am trying to launch a campaign for the following three applications that I selected in the configuration of the campaign: Saviynt, Firewall Rule Exception and Diligent. When I launch the preview, I only see the certification for Diligent. Please see screenshots below:
I also tried to launch another campaign with the same results. I am also seeing this for another user where only one or two certifications are being launched in a campaign, even when more applications were selected.
07/05/2023 10:37 AM
All these 3 apps have owner assigned as Primary certifier? Also is it like same user is owner for all the three application that you mentioned?
07/05/2023 10:44 AM
@dgandhi Yep this was the first thing I checked. All three applications have a primary certifier assigned. Only two of them have the same owner.
Saviynt and Firewall Rule Exception have the same owner and Diligent has a different owner.
07/05/2023 10:58 AM
Can you check if the owners assigned to Saviynt and Firewall Rule Exception application is active?
07/05/2023 11:02 AM
@dgandhi Yes the user record under Identity Repository for the user is active and they also have ROLE_CERTIFIER role.
07/05/2023 11:38 AM
Can you paste the campaign config.? It seems there is some advance config in your configuration which is not satisfying with the data that you have in that particular application and hence no records are populated in the campaign.
07/05/2023 12:43 PM
@dgandhi I was able to figure out the issue in the configuration of the account specification query.
Thank you for all of your time and help! I really appreciate it.
07/05/2023 01:27 PM
So it was an issue with account query in your advance config.