Jason,
Agree with your answer, however there is a CA (trusted or self-signed) that was used to be able to login to the maximo / MAS Core server, since it tried to start with downloading the configuration. If sa self-signed certificate was used (and the user followed this instruction for IBM: https://www.ibm.com/docs/en/mas-cd/maximo-manage/continuous-delivery?topic=mobile-installing-maximo-app-devices), then the user should have expected that this was also available on the end points used. If trusted SSL certificate was installed on *.xxx.xxx.xxx level, it would have worked Out of the Box. So ASR, please reply which approach was used (self-signed or trusted on DNS level) to understand better where it goes wrong. In some cases even the self-signed or trusted certificates must be added to the Manage install (Admin -> manage -> update configuration -> add certificate and then add at manage or end-point level (similar as adding certificates for e.g. Autodesk when using BIM viewer)>
Regards,
JW
------------------------------
Jan-Willem Steur
Manager Business Development
ZNAPZ b.v.
Breda
+31 6 25639950
Jan-Willem
------------------------------
Original Message:
Sent: Mon July 15, 2024 05:14 PM
From: Jason VenHuizen
Subject: MAS Mobile 9 Error - maximo mobile error java.security.cert.CertPathValidatorException: Trust anchor for certification path not found
The error indicates that your device does not have the Certificate Authority that signed your MAS endpoint certificate in its store of trusted CAs. This is likely because your MAS endpoint is using a self signed cert and your device does not have that CA.
Jason
Original Message:
Sent: 7/15/2024 5:12:00 PM
From: ASR
Subject: MAS Mobile 9 Error - maximo mobile error java.security.cert.CertPathValidatorException: Trust anchor for certification path not found
Hi, I am logging into an android device and encountering this error on the initial data sync. Any ideas how this can be fixed?
------------------------------
ASR
------------------------------