wso2 / wso2/docs-apim

Doc Feedback: Adding Choreo Certificate For Analytics

Open Beginner friendly
#9,428 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
CSS
Stars
99
Forks
708
Avg merge
1d 7h
Merged PRs (30d)
22

Description

Location : https://apim.docs.wso2.com/en/latest/monitoring/api-analytics/choreo-analytics/getting-started-guide/

If customers encounter the following error:
TID: [] [] [2025-06-16 15:25:25,791] ERROR {org.wso2.am.analytics.publisher.client.EventHubClient} - Recoverable error occurred when creating Eventhub Client. Retry attempts will be made in 5 min. Reason :Provided authentication endpoint https://analytics-event-auth.choreo.dev/auth/v1 is not reachable.

Then they need to do the following:
This occurs when the "DigiCert Global Root G2 root" and the “Choreo root certificate” are not available in the client-truststore.jks of the gateway node.

Add those certificates to the client-truststore.jks, restart the gateway node, and then share the results with us?

You can use the following command to import the certificate into the client-truststore.jks.
Example: keytool -import -alias choreoroot -keystore client-truststore.jks -file ISRGRootX1.pem

Multiple customers have run into this issue per internal ticket.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open the Choreo Analytics getting-started guide at the linked documentation location and review its troubleshooting content. Add guidance for the unreachable authentication endpoint error, including the DigiCert Global Root G2 and Choreo root certificates, client-truststore.jks, restart step, and keytool example. Done means the page clearly explains this customer scenario and remediation.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
documentation, security
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.