Keystore Certificate (Expired)

Hi team,
Im using EMA to connect to RCC and make contributions, everything was working right but since yesterday i cant connect due to certificate expiration, i tried to make another keystore and same problem is showing.
I've checked the certificate and it says valid until 2029
i created keystore.jks following example in :
Building a keystore file to be used with an HTTPS (or ENCRYPTED) connection type for real-time Java-based APIs | Refinitiv Developers
I used comodo certificate as mentioned
*** Important updated on October 2018: The TRCC servers now use a certificate from comodo, please download it from "http://crt.comodoca.com/COMODORSAOrganizationValidationSecureServerCA.crt" instead. ***
Steps to create keystore and import certificate
Code where i used keystore
Error
Error text Error initializing channel: errorId=-1 text=Invalid certificate (Expired): NotAfter: Sat May 30 05:48:38 CDT 2020
Any idea what can i do?
how i know when the certificate will not be anymore valid since i can see that it expires until 2029?
Best Answer
-
I was contacted directly by Carlos, and we determined that he needs to contact the owners of the RCC product for help.
0
Answers
-
What version of EMA Java are you running, and what JVM version are you using?
EMA Java 3.5.1.L1/RTSDK version 1.5.1.L1 was enhanced to not require a specific jks file. Instead, it will pull the JVM's default JKS file if no file is specified in the EMA config. Java JRE ships with compatible Sectigo/Comodo certificates used by Refinitiv.
For JVM, please make sure that you are running at least the equivalent to Java JRE 8u51: https://support.sectigo.com/articles/Knowledge/Sectigo-AddTrust-External-CA-Root-Expiring-May-30-2020
Thanks,
Mitchell
0 -
Im using EMA Java 3.6.0.0 and Java SKD 8u261 Java JRE 8u281
Still having the same error if file is not specified
the thing is that everthing was working and yesterday for no reason that error was showing0 -
Hello @mitchell.kato
Could you please help the client on this follow up question?
0 -
Right, issue has been solved, it seems it was a trouble in the aws platform some changes were causing the problem so they did a rollback, but now everything is working
0 -
There was an expired intermediate certificate in the RCC certificate chain, which was affecting older OpenSSL 1.0 based clients. This issue has now been fixed and should all be working.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 685 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 252 ETA
- 556 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 651 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛