This is needed to be able to access resources on external (to Bluemix) servers in SoftLayer that the client manages. Resources on these servers need to be accessed over https during CF operations (such as application staging) and by runtime operations. Without the self-signed certificates, the connections over https are not trusted and are failing, most likely due to security prompts. (The same connections over http: are working fine.)
One example of what the client is doing is specifying a custom buildpack on the CF push (ie, -b https://buildpack.mycustomdomain.com). CF is not able to download the buildpack due to the un-trusted connection.
Without having the certificate in CF, the https requests to the client-managed external servers will not be trusted and the connections will fail.
| Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
PLEASE IGNORE MY PREVIOUS COMMENT (April 4, 2018 15:50). It was for another ER, sorry
This requirement was requested directly from client to me.
It has been implemented in March 2018 and I have verified that it covers exactly what requested by client and it works fine, so it can be closed now.
Thanks for adding this requirement. We have accepted this for our longer term roadmap.
We're also evaluating a short-term possibility where customers would be able to open a support request to add their self-signed certificates. In the meantime, we recommend that customers use commercially signed certificates for solving this problem if they need it sooner.
Hi BM OM team,
LBG is asking an update here. Can you please let me know your evaluation and the status?
Note that we asked to add a trusted certificate into container root store, as described here: https://docs.cloudfoundry.org/adminguide/trusted-system-certificates.html