Since we’ve reached the limit of 6 searchable attributes, we attempted to configure a simple account correlation on a new source through a cloud correlation rule.
Unfortunately, from posts I’ve read, it seems that it also requires the identity attribute to be searchable, despite not being specified in the documentation.
Other possibilities to handle the correlation process would be to have a workflow triggered on source account creation, or an external script.
Are there any other solutions to handle this problem?
A suggestion as you mentioned “AccountCreation”. Accounts created by ISC during provisioning has the attribute: manuallyCorrelated=true. This correlation stays regardless of the correlation config in the source.