So I am trying to do a build server, but running into a issue. We all know author's are on port 4502, but when I get my dev environment from AMS I get an IP address like XX.X.XX.XX and if go using that IP address I get certificate error (and I should because that IP is not on the certificate). They also give me a url like https://XXXXXX.adobecqms.net .. that is fine with no certificate error, but I can't access /crx/packmgr/service.jsp since you can only access that via IP address. So when I try to create a build -PautoInstallPackage and make it install on either the IP address or a Host name which is virtually IP address I get a maven build issue because we have a certificate problem. Does anyone know a work around for this?
Solved! Go to Solution.
On an AMS managed instance SSL/TLS is terminated at the ELB. So they install a local SSL certificate when going to the Author / Publish IP. HTTP access via port is locked down heavily.
- work with your CSE to whitelist your IP so you can hit the Author over http://<Ip>:4502
- connect over https as you are doing and tell maven to use a flag like : -Dmaven.wagon.http.ssl.insecure=true