When running the IGA Xpress installer (./install) in an environment using Active Directory (AD) for back-end authentication, the installation fails with the following error:
This occurs even if the igx user exists in Active Directory. Because AD uses the sAMAccountName attribute for both users and groups, many organizations cannot have both a user and a group named exactly "igx." The installer previously required a group name that matched the user name.
IGA Xpress 1.0.8 and earlier.
The IGA Xpress installer (version 1.0.8 and earlier) had a hard-coded constraint requiring the primary group of the installation user to be named "igx." If the user was pre-created in Active Directory with a different primary group name (e.g., igx:igx_group), the installer would fail to identify the group and attempt to create it, resulting in a conflict or a "not found" error.
The installer logic has been updated to relax the igx group constraint. The installer will now only attempt to create an igx group if the igx user is not already present on the system. If the user is already present (e.g., via AD or LDAP), the deployment will use that user's existing primary group, regardless of its name.
This fix is scheduled for inclusion in the following releases:
These releases are currently targeted for the end of April 2026.
For environments that require immediate deployment before the release of Xpress 1.1:
igx) for initial installation in lower/test environments.igactl backup, reinstalling with the new version using the AD account, and then performing an igactl restore. This ensures all file permissions and user-mode services are correctly mapped to the new AD identity.