Buildkite Troubleshooting and Validation

This section provides guidance to validate and troubleshoot your Buildkite integration with SailPoint Entro.

---

Navigation Path

Management → Accounts & Integrations → Buildkite → Troubleshooting and Validation

---

Validation Steps

1. In the SailPoint Entro Dashboard, go to Management → Accounts & Integrations → Buildkite.

2. Confirm the connection status shows Verified.

3. Check that Last Synchronization Timestamp is recent.

4. Validate that pipeline and build data appear in Findings → Inventory.

5. Review connector logs under Worker Group (Connector) for successful sync entries.

---

Command-Line Verification (Optional)

You can test token validity directly using the Buildkite API.

1. Verify token with the Buildkite API:

curl -H "Authorization: Bearer <API_TOKEN>" https://api.buildkite.com/v2/user

Note

Expected Output: A JSON object with user and organization metadata, confirming API access.

---

Common Issues and Resolutions

Issue	Possible Cause	Resolution
Token rejected	Incorrect or expired token	Generate a new token and re-enter in SailPoint Entro
“Permission denied”	Insufficient read scopes	Ensure token includes all required read scopes
No data visible in SailPoint Entro	Network restrictions	Verify outbound HTTPS access to app.entro.security
Sync delay	API throttling	Allow scheduled retry or reduce concurrent requests

---

Advanced Diagnostics

• Check SailPoint Entro Worker logs for Buildkite sync events and error codes

• Validate token activity in Buildkite’s API Access Token Settings

• Ensure TLS certificates are valid for outbound HTTPS requests

---

Security & Compliance Notes

• All Buildkite integrations operate under read-only access

• Tokens and credentials are encrypted using AES-256

• All communications occur over TLS 1.2+

• Integration complies with SOC 2 Type II, ISO 27001, and GDPR frameworks