Overview 💥
Following Webroot’s migration to OpenText Secure Cloud, authentication methods used by existing Liongard Webroot Parent Inspectors may become invalid.
As a result, Webroot inspections configured with legacy credentials may begin failing until updated API credentials are configured.
Expected Error :
Inspection failed at https://******api.webrootcloudav.com/auth/token with status code 400: Response Error:400 Bad Request
This article walks through updating the existing Webroot Parent Inspector while preserving:
✅ Child Inspector relationships
✅ Historical inspection data
✅ Auto-discovery functionality
⚠️ Important:
A new inspector does not need to be created. Updating the existing Parent Inspector restores functionality.
Why Does This Happen? 🤔
Webroot’s transition to OpenText Secure Cloud introduces a new authentication model based on API Client credentials.
Previously configured Webroot Parent Inspectors may still rely on legacy authentication details that are no longer accepted after migration.
Because all Webroot Child Inspectors depend on the Parent Inspector for discovery and synchronization:
Parent authentication failures prevent inspections from completing
Child inspectors stop updating automatically
Inspection data becomes outdated
Updating credentials restores communication between Liongard and OpenText Secure Cloud.
Impact 🚨
After migration, partners may observe:
Webroot Parent Inspector failures
Authentication or inspection errors
Child Inspectors no longer updating
Auto-discovery stopping
Older inspection timestamps in Liongard
✅ No inspector data is lost.
This is strictly an authentication update requirement.
Steps To Resolve👨💻
Step 1 — Generate New API Credentials in OpenText Secure Cloud
Log in to OpenText Secure Cloud using an administrator account.
Navigate to: Settings → API Access
Generate the following credentials:
Client ID
Client SecretNavigate to: Account Information
Copy the GSM Parent Keycode.
💡 Important:
Store these credentials securely. They will be required when updating the Liongard inspector.
Step 2 — Update the Existing Webroot Parent Inspector in Liongard
Log in to your Liongard instance.
Navigate to: Admin → Inspectors
Locate your Webroot Parent Inspector.
Select Edit.
⚠️ Do NOT create a new Parent Inspector.
Creating a new inspector breaks child relationships and historical data mapping.
Update the following fields:
Portal Admin Username
Portal Admin Password
API Client ID
API Client Secret
GSM Parent Keycode
Click Save.
Step 3 — Validate Inspector Functionality
After saving the updated credentials:
Run the Parent Inspector in Clear Cache + Debug Mode
Confirm the inspection completes successfully.
Verify:
✅ Parent inspection status shows Success
✅ Child inspectors resume updating
✅ New inspection timestamps appear
✅ Auto-discovery resumes normally
Child inspectors will automatically reconnect once the Parent Inspector authenticates successfully.
Expected Result ✅
After completing these steps:
Parent Inspector successfully authenticates with OpenText Secure Cloud
Child Inspectors resume automatic discovery
Existing environments remain unchanged
Historical inspection data remains intact
Troubleshooting 🔍
If inspections continue to fail:
Confirm API credentials were generated under Settings → API Access
Verify the GSM Parent Keycode matches the OpenText account
Ensure administrator permissions were used when generating credentials
Re-run inspection using Debug + Clear Cache
Confirm credentials were copied without extra spaces or formatting
When to Contact Liongard Support 🦁
Contact Liongard Support if:
Parent Inspector continues failing after credential update
Child Inspectors do not resume updates
Authentication errors persist
Inspection completes but data does not refresh
Information to Include in a Support Ticket 📩
Please provide:
Liongard Instance URL
Environment name
Webroot Parent Inspector name
Screenshot or copy of inspection error
Confirmation new OpenText API credentials were generated
Timestamp of most recent failed inspection
Frequently Asked Questions 🙋♂️
1️⃣ Do I need to recreate child inspectors?
No. Child inspectors automatically resume once the Parent Inspector authenticates successfully.
2️⃣ Will historical inspection data be lost?
No. Updating credentials preserves all inspection history and relationships.
3️⃣ Do all environments require updates?
Only environments migrated to OpenText Secure Cloud require credential updates.
4️⃣ Can I create a new Parent Inspector instead?
This is not recommended, as it breaks inspector relationships and requires rediscovery.
Additional Notes 🗒️
Liongard continues to use the existing Webroot Inspector framework.
Only authentication credentials change following migration.
Updating credentials is a one-time action per affected environment.