Who is this article for?

Administrators responsible for user management.

Administration module access is needed.

When integrating security groups with Azure Directory groups, you may run into a number of issues.

This article outlines the troubleshooting steps to take if you experience problems.

1. Issue

This article doesn't target a specific issue, but rather provides a list of commonly missed things when attempting integration.

2. Solution

To resolve majority of common issues, make sure you have checked the following:

• Application server must be a member of the domain.
• Ideagen Quality Management Server service must be running under the context of an account with the required Active Directory access rights. This account must be able to read the values stored within users' memberOf attributes.
• Correct Active Directory group name must be entered into the Associated Active Directory Group field. This field must contain a group's cn (Common Name) attribute value as shown in Active Directory. 
• Firewalls may block communication between the application server and one or more of your domain controllers. When integration is determining Active Directory group memberships, it queries membership information from Active Directory using LDAP over port 389 by default. This port must not be blocked.