Unexpected Hexnode API key generatedSolved

Hello @stevenhere ,

An API key generation email is sent to technician email addresses when API access is enabled or when an API key is generated in the portal.

To check which technician account triggered the action, review the audit logs:

1. Navigate to the Reports tab.
2. Open Built-in Reports.
3. Go to  Audit > Integration Events > Hexnode API.
4. Look for the API-related event and the technician account associated with it.

If the key is not required, revoking it is the correct immediate action. You can generate or enable API access again later if needed.

If the Admin > API section is accessed for the first time, the API key may be generated automatically. In that case, the audit log can show the signed-in technician as the user associated with the event, even if they did not manually create a key for active use.

Regards,
Simon Scott
Hexnode UEM

Okayy got it. Also, is there a way to switch technician MFA from email codes to a third-party authenticator app?

For switching MFA from email codes to an authenticator app, update the technician profile assigned to that user:

1. Go to Admin > Technician and Roles.
2. Open Profiles.
3. Select the profile assigned to the technician.
4. Click Edit.
5. Go to Two Factor Authentication.
6. Enable Ask this user to set up Third Party Authenticator.
7. Save the profile.

Once enabled, the technician must log out and log back in to configure MFA using a supported third-party authenticator app instead of relying only on emailed codes.