I am currently working on a web service connector that utilizes client certificate authentication. Currently, we input the client certificate and certificate key directly through the UI. However, we’re facing challenges in maintaining this approach within the target properties file, which already contains 79 lines of content. It becomes cumbersome to handle such a large amount of data in the properties file. Additionally, when a new deployment occurs via the UI, the certificate is removed, requiring manual reinsertion each time.
How can we effectively manage this and maintain the client certificate and key within the target properties file for smoother deployments?
Hi @DM00924201 , I hope this question is related to IDN (not IIQ).
Just wondering if you could share more insights on:
Which target properties file and how you load it to IDN Web Service source?
How client certificate gets auto-removed during deployments? Do you just push a new build which doesn’t has the client certificate so it overrides it or some other way?
Is there any other properties file or secret file that you can create which can hold the content of client certificate and reference it in your build, have you tried that already?
