Pratiksha
Mega Sage
Mega Sage

Recently, we began working with a new client who wanted to implement the Agent Client Collector (ACC). As part of the setup process, we installed the MID Server, which successfully appeared in the system and was validated. Following this, we proceeded with the ACC configuration, which was completed successfully.

 

Next, we need to share the MID Server's IP address, port, and API key to proceed with the agent installation. However, when we clicked on the API key, it appeared encrypted. Below is a sample screenshot for reference.

 

Screenshot 2025-01-29 at 1.47.22 PM.png

 

o resolve this, we raised a case with ServiceNow. In parallel, we conducted an internal review by checking the UI link and related scripts to identify any potential bugs. ServiceNow later responded, confirming that a Module Access Policy had been created, which was set to Reject.

To access the API key, the following steps need to be followed:

  1. You must have the Key Management role, which cannot be assigned directly.
  2. First, elevate your role to Security Admin.
  3. Navigate to Key Management Administration and add your name to the list.
  4. Go to the table sys_kmf_crypto_caller_policy.
  5. Locate the policy associated with the user who initially clicked on "View API Key."
  6. In the Result column, the value will be set to Reject. Update it to Track.
  7. Save the changes, and the API key will become visible.

With this update, we were able to successfully retrieve the API key and proceed with the installation.

 

I hope the article helps.

 

Regards, 

Pratiksha Khandelwal

Comments
SK Chand Basha
Giga Sage

Very Helpful!!

Version history
Last update:
‎01-29-2025 12:34 AM
Updated by:
Contributors