We're experiencing an issue with an older client version connecting to PA 2.0.4. We have a set of certificates that works perfectly when using perspectives or architect however we are using the VBA API to connect: TM1SystemServerConnectWithCAMNamespace and this is not working.
Is there a way to point the API at these working certs? We cannot (easily) change the certs in the location that come with the package the users have installed. I am guessing that this would perhaps solve the issue.
I am pretty confident this is a certificate issue as TM1_API2HAN works fine. We are also facing the same issue with sec mode 2.
We can't use the above piggyback approach as the code needs access to the rules via the API, and users won't have admin rights necessary for this.
The code works fine for me when using PA 2.0.x client.
Any help greatly appreciated.
1 post • Page 1 of 1