ADSDOMAIN: The following fields are compulsory and need to be filled: Forest

What version are you using?
Where exactly are you getting the error, during the connection Wizard?
What type of permissions are you using to log into the synchronization editor?
What type of permissions are you having for your synchronization user in AD? All of the recommended ones?

What version are you using?
Where exactly are you getting the error, during the connection Wizard?
What type of permissions are you using to log into the synchronization editor?
What type of permissions are you having for your synchronization user in AD? All of the recommended ones?

Hello Markus,

I have the same problem on a customer.

I am using the OIM version 8.2.1.

At the end of creation of new synchronization project for AD, at saving I received this error.

I defined a lot of AD Synchronization processes without error. May be possible that it is due to a bad AD domain configuration ?

Any suggestion ?

Thank you very much and best regards

Ermes

This potential error should be fixed in 8.2.1. Can you check thre following as suggested by the documentation?

For successful authentication, the domain controller and the domain can be resolved via DNS request. Is the DNS resolution not possible, the connection to the target system is rejected with an error message

Hi Markus,

Thanks for your help. I found on AD definition a DC with no DNS associated.

After resolving this problem the synchronization editor works fine.

Thank you very much and best regards,

Ermes

In 9.2 still same issue. its annoying that it occurs when trying to save the newly create syncproject to the datbase even all wizard steps were successfull.

Not entierly sure how it tries to resolve the forest at that point....

Are you using the native Active Directory Connector or the Active Roles connector?

Native Active Directory

The customer has a very restrictive network, where you have to open every port explicitely.

The wizard is successfull and when you try to commit to the database the error occurs.

I solved it by creating the syncproject on a less restricted "workstation". Running the synchronization works from the server that threw the exception after it has been created.