The JumpCloud Administrator Console will display Configuration Alerts in the Notifications area in the top right, the number indicating the number of active alerts:
The following conditions will create a Configuration Alert:
A change to either of these files external to the agent, such as a manual change with useradd (Linux only)
Notification: Your /etc/passwd file has changed outside of JumpCloud on system_name
Action: This alert can be dismissed and may justify further investigation of the change on the system itself.
UID conflict when binding a user
Notification: Existing User. "Conflicting UID with user username."
Detail: The user will not be provisioned to the system until the conflict is resolved.
Action: Correct the UID in either JumpCloud or the system.
GID conflict binding a user
Notification: Existing User. "Group doesn't exist. Please add group for GID n"
Detail: A User already exists on the system with a GID different than the one specified within JumpCloud. Action: The GID discrepancy should be resolved either in the console or the system in order to take over the account.
GID conflict creating linux group in tag
Notification: "Group groupname wasn't created. There is already a group on the system with a GID of n"
Detail: A Tag/Group of Users has been created where the GID is the same as a GID that already exists on the system and the group name in the Tag/Group of Users does not match the group name on the system.
Action: To manage an existing group on a system, the group name and GID in the Tag/Group of Users must match the system. To create a new group, both the group name and the GUID must be unique.