BigFix Client Error: NoAuthorizedSignature

Usage and Config Platform
1

We are encountering intermittent synchronization failures on BigFix clients while gathering the ActionSite. The primary error observed is:

  • NoAuthorizedSignature (21) – BigFix could not verify the authenticity of the site content

This results in repeated “ FAILED to Synchronize - BigFix could not verify the authenticity of the site content. - 21NoAuthorizedSignature” messages, although client reports continue to post successfully in between.

The issue is observed across all client platforms (Windows, Linux, and macOS).

We already have an open case with HCL Support (Case #CS1438462), but wanted to check if anyone in the community has experienced similar behavior.

Observations and activities so far:

  • Operator sites were propagated using BESAdmin

  • Gather reset was performed across all relays

  • Switching relay for a test client temporarily resolved the issue, but it reoccurred

  • Impact is seen across all client types

  • Only Master Operator actions appear to be affected; Non-MO actions are working as expected

  • A one-time error was observed related to the BES Support site

  • Some MO actions remain stuck with no applicability; however, triggering a blank action with the same MO account and targeting often restores applicability

  • Checked Procmon not found any blocking

  • Checked internal Endpoint Control tools but no luck

Has anyone encountered similar ActionSite synchronization or signature verification issues? Any insights into potential root causes (e.g., relay/master sync, certificate/signature issues, or gather process problems) would be greatly appreciated.

Thanks in advance!

Update Note:
To address the most frequently asked question “What infrastructure changes were made recently?” the answer is… none, really :slightly_smiling_face:

The only recent change was related to licensing compliance, where the CIS Checklist for macOS 26 was not appearing and was later updated from the HCL side. While this shouldn’t have caused any impact, as we all know, sometimes things can be a bit… sensitive :grinning_face_with_smiling_eyes:

The issue started approximately 3 weeks ago and is still ongoing.

2

Hi @vk.khurava ,
I would have tried here Force a gather of site CIS Checklist for macOS site and one thing which I attempted in past with one custom site(not external) change the subscription to none for the site and after few hrs changed it back to all computers.
I hope manual replacement of masthead file does not happen :frowning: this is scary situation if happening for most of the clients

3

We do not use any CIS external sites, and none of our clients are subscribed through a single CIS site. Therefore, this possibility can be ruled out.

1 Like
4

Is this issue fixed? I am curious here to see if license update caused this issue or was it something else

5

Yes, the issue is now resolved. After nearly two weeks of troubleshooting, support confirmed that it is a bug. There is an associated KB article, but it does not clearly describe the actual issue or list relevant errors, which likely made it difficult to identify during troubleshooting.
The bug is present in BigFix version 11.0.3. The recommended fix is to upgrade to version 11.0.5 or apply the available hotfix.
I’m currently away from my machine, but I will share the KB article link later.

2 Likes
6

Yes, the known issue is related to Relays unable to sync opsites properly - Customer Support.

7

Thank you @EmilianoN and @vk.khurava we will keep this information as we might move towards 11.0.5 as 11.0.6 is already released