Which IIQ version are you inquiring about?
8.3p4
Has anyone else come across this? Provisioning of the group actually does succeed in Azure, but within about 20 seconds of clicking approve, the provisioning transaction returns this message. On the next full group aggregation, the entitlement will be recreated (with the submitted IIQ meta-data missing of course).
Some things worth noting:
Veeery occasionally the entitlement succeeds correctly. In our pre-production Azure tenancy (which has a magnitude less users/groups) it succeeds more often, but not consistently.
Trial and error has revealed that it’s very likely related to our connectors group filter:
(dirSyncEnabled NE true)
We have to filter out the on-prem groups from the connector without exploding out the size of our entitlement catalogue.
As this is an advanced filter, I need to remove the ‘owners’ attribute, and I suspect the connector is having trouble reading the new group back in due to it not being in the schema. I can see the provisioning transaction submits a null value for ‘sysOwner’ even though I do supply it in the provisioning form. I have no idea why it returns the access denied error, however.
Any ideas?