It's a long time since I wrote that post, so my memory is fuzzy (but it certainly did work at the time). You don't need to create a BKS for the app because the scenario unpacks the public certificate and stores it in the file system, and then the setTrustedCertificates reads it from the file system.
The things to check, if you are trying to reproduce the post, are:
- Have you started the ML server using the self-signed certificate?
- Have you unpacked the client-side cert into the file system?
- I seem to recall an issue that the "root" of the file path is not obvious (there is a mismatch in "/data" somewhere). Are you sure you are accessing the certificate properly?
If you want to eliminate sources of error, I would recommend using the SYNCHRONIZE statement in ISQL and synchronizing from the desktop. If you use trusted_certificate and get a successful sync, you know that the certificates are compatible.
To some extent, it's an atypical scenario as you would be more likely to have a server-side certificate that is in a chain to some certificate authority (instead of a self-signed cert) and you would use a client-side cert in the device's certificate store that knows about that authority.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.