Can the UCF-Archer Web API be configured not to use https/ssl?
I have tried using http-only on that interface without success. My concern is the impact changing from mixed https/http to https-only has on other interfaces, i.e. they too must use https/ssl, a challenge on some data feeds.
If I am misunderstanding, I would appreciate a clarification.
Thanks for you response, as you seem to confirm that Archer must be configured HTTPS only, despite that it forces every interface, including data feeds, to also use HTTPS; this may impact availability of some data sources and/or alter related workflows to incorporate new data sources. There is also an administrative burden to manage the certificate lifecycle for the SSL certificates used on these interfaces. These impacts are not obvious byproducts of integrating UCF and Archer, so when presenting the them to management, I want to be certain as can be that my facts are correct.
Administration of the SSL certificates is minor, unless we are talking about the use of self-signed ones. Traditional certs from external or internal CA's are good for 2+ yrs. Updating Archer and the UCF Archer Endpoint is also a very minimal task. To date, we have not seen any issues with data feeds when Archer is SSL enabled. The only issue I can recall had to do with only allowing TLS protocol which was resolved a while ago. I hope this helps.