On Mar 27, 2017, at 1:52 AM, =Jan Huijsmans <jan.huijsmans@baruch-ict.nl> wrote:Hi,
Ok, we managed to secure =/WebCatalog/ dir with a permanent redirect to https, but the Admin dir =itself is placed in cgi-bin dir, which has a special status and can't be =handled in the same way. (other then redirecting the complete cgi-bin =dir)
To be honest, I'm surprised that the application itself =doesn't do anything to improve security, other then username/password =over an unencrypted link. Personally I'm glad we can contain WebDNA in =virtual 1 server. I wouldn't want to provide services for several =customers on 1 server with it. It shows it's age.
On March 9, 2017 at 2:46 PM =Jan Huijsmans <jan.huijsmans@baruch-ict.nl> wrote:Hi,
With all the help, the =environment we're setting up is running as I (and more importantly, the =customer) expect it to.
Is there an official way to =secure the admin interface within WebDNA so connects are only accepted =on https? We're trying to add a rewrite via apache config for the =WebCatalogEngine/Admin dir, but somehow it feels as the wrong way to =secure the admin interface.
Vriendelijke groet,
<Mail =Attachment.png>
--------------------------------------------------------- =This message is sent to you because you are subscribed to the mailing =list
--------------------------------------------------------- =This message is sent to you because you are subscribed to the mailing =listVriendelijke groet,
<Mail =Attachment.png>
. =To unsubscribe, E-mail to: =div>archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us
|
On Mar 27, 2017, at 1:52 AM, =Jan Huijsmans <jan.huijsmans@baruch-ict.nl> wrote:Hi,
Ok, we managed to secure =/WebCatalog/ dir with a permanent redirect to https, but the Admin dir =itself is placed in cgi-bin dir, which has a special status and can't be =handled in the same way. (other then redirecting the complete cgi-bin =dir)
To be honest, I'm surprised that the application itself =doesn't do anything to improve security, other then username/password =over an unencrypted link. Personally I'm glad we can contain WebDNA in =virtual 1 server. I wouldn't want to provide services for several =customers on 1 server with it. It shows it's age.
On March 9, 2017 at 2:46 PM =Jan Huijsmans <jan.huijsmans@baruch-ict.nl> wrote:Hi,
With all the help, the =environment we're setting up is running as I (and more importantly, the =customer) expect it to.
Is there an official way to =secure the admin interface within WebDNA so connects are only accepted =on https? We're trying to add a rewrite via apache config for the =WebCatalogEngine/Admin dir, but somehow it feels as the wrong way to =secure the admin interface.
Vriendelijke groet,
<Mail =Attachment.png>
--------------------------------------------------------- =This message is sent to you because you are subscribed to the mailing =list
--------------------------------------------------------- =This message is sent to you because you are subscribed to the mailing =listVriendelijke groet,
<Mail =Attachment.png>
. =To unsubscribe, E-mail to: =div>archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us
DOWNLOAD WEBDNA NOW!
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...