This would also be for NCM as well. I'd like the ability to enable SSL for the website during configuration. I dislike having to use port 80 for configuration. Could this be worked into the next release?
Hi damien--
Thanks for this. I've marked it for the PM to review.
M
Will add to the list and will consider it for future releases.
Francois Caron - Snr Product Manager
We have been complaining about this in NPM before (this works well in NPM 10.1 now, running the config wizard does not destroy our website anymore, a manual entry in the database saying that we use SSL now also fixed some links in e.g. pdf-reports, have not tested this with a new installation though)...
We only use SSL and even deactivate HTTP, not much of an issue for us with NCM as we integrate NCM into NPM and delete the NCM website.