Understand Legacy Alerts

Before the introduction of JumpCloud's Device Monitoring and Alerting service, the JumpCloud Admin Portal generated configuration alerts to notify users of changes related to security, users, and groups, allowing proactive resolution. These alerts are now available in the Legacy Alerts section.

To view Legacy Alerts:

1. Log in to the JumpCloud Admin Portal.
2. Go to the top menu and click the Alerts bell icon.
3. On the Alerts page, click Legacy Alerts.
4. The Configuration Alerts page displays all the configuration alerts generated by the system.

Security Alert(s)

The following conditions create a Security Alert:

• File changes - A change to either of these files external to the agent, such as a manual change with useradd (Linux only):
• /etc/passwd
• /etc/shadow

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.

User Conflict(s)

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.
• Group Conflict(s)

GID conflict binding a user

• Notification: Existing User. "Conflicting group that has other users assigned to it for GID n."
• Detail: The GID assigned to the user in JumpCloud is already assigned to another group of users on the system.
• 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

• Notification: "Group groupname wasn't created. There is already a group on the system with a GID of n." 
• Detail: A 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 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 Group of Users must match the system. To create a new group, both the group name and the GUID must be unique.