How to secure webaccess with SSL ?

[organman]

I'm running Groupwise 6.5.2 on a NW 5.1 SP6 server.
I want to secure users webaccess with SSL to the web server.
How do I configure this ?
The web server is NetWare Enterprise Web server 5.10f.

I've found these articles that I think could be the correct solution for me but I need someone elses opinon.

http://support.novell.com/cgi-bin/search/searchtid.cgi?/10051598.htm

(Basically tells how to turn on encryption on the web server)

http://www.novell.com/connectionmagazine/2003/10/tech_talk_3.html

Section "Securing Users' Webaccess Sessions with SSL" and the step "Add a reference to SSL Certificate DNS to Novonyx web server" is the one I'm thinking of using.
My intention was to skip the other steps in the document since they describe how to secure access to the GW agents.

Am I right in my assupmtion that I can skip these steps ?

I'm thankful for any opinon on this matter.

Regards
Lars-Gunnar

 

[ITsmyfault]

fwiw when I confronted this, I opted to run Apache. i had run apache on other OS's before so it was a more natural choice.. that said, it runs fine on 5.1 (it's just not supported) You have to run 1.3.7 (2.0.x requires a differend Clib) Adding SSL is uncommenting 1 line of code in the conf file when you run apache on Netware. It's like falling out of bed.
If this is an option, here is the how to guide I used:

http://www.caledonia.net/apache-wa.html

It's very well written, easy to follow and inexpensive. Better still, it *works*.

SSL code looks like this:
SecureListen 192.168.0.23:443 "SSL CertificateDNS"

How easy was that?

hth - Joe

 

[organman]

Thanx for your info, but this is not an option right now.
I must use NetWare Enterprise Web server 5.10f.

When we upgrade to NetWare 6.5 Apache will be used.

/Lars-Gunnar

 

[a228380]

hi I was on enterprise server and you can do ssl but we ran into a small problem. we encrypted the url but if someone book marked a directory lower than the url they could still get in un-encrptyed. if you encrypt the whole server this will not be a problem. I think if the server is named the same as the url it will help also. we named the server webacc and the url is webacc.

we did run into a conversation time out problem that novell could not resolve and they basically said they do not support netscape any longer and to upgrade to apache. we did and our problems minimized but we still get the conversation time out problem from time to time.

good luck
al