Forum OpenACS Q&A: Re: Problems with https login

Collapse
Posted by Jade Rubick on
Bart figured out the cause of this.

It runs out that because the format for nsopenssl has changed with nsopenssl 3 (used by Aolserver 4), the acs-tcl/tcl/security-procs.tcl get_https_port proc was getting the wrong port number. It was trying to get it from

[ns_config ns/server/[ns_info server]/modules nsopenssl]

and it defaults to 443 if nothing is found.

So if you're using a non-standard port for SSL, it uses 443 anyway.

I'll fix this hopefully tomorrow.

Collapse
Posted by Jade Rubick on
I've committed a fix to the bug in get_https_port in both HEAD and oacs-5-1.

However, that still actually does not fix the problem. I'm looking into it right now.

Collapse
Posted by Bruno Mattarollo on
Hello Jade,

can you confirm that this is a problem only with nsopenssl 3/AOLServer 4? Or is it something we should look into for nsopenssl 2.1a/AOLServer 3.x?

Cheers
/B

Collapse
Posted by Bruno Mattarollo on
I have applied your patch on some instance that we have internally and it solved some of the issues we were having as well, so THANKS! :) (btw nsopenssl 2.1a and AOLServer 3.3.1)