Re: SSL and public facing web site on the i

I don't know if you were being cheeky here or not. :) Those directives are
required, and they can easily be added by editing the config file.

You just have to make sure that the name you use on SSLAppName matches the
name assigned to the certificate (which you do in DCM).


On Tue, Apr 23, 2013 at 2:36 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

I didn't like all the extra things the web interface would put into my
config files.

Yeah, same here. The GUI interface adds a couple HTTP directives such as:

SSLEngine On

SSLAppName QIBM_HTTP_SERVER_RDWEB

I've tried adding the SSLAppName directive using EDTF and such, but the
GUI must be doing something extra that enables the "application name" to
"appear" in DCM, which is used to link the certificate to the application
name.

So, this appears to be one case where the GUI is needed.

-Nathan

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.