Home » Blogs » bwalker's blog

Luminis upgrade problems - http vs https

Submitted by bwalker on Mon, 2010-06-28 16:40

Upgrading from 4.2.0.67 to 4.2.2.68 and have encountered the following problem (in development testing): The login screen no longer displays.

When we attempt to login by going to the portal login page (http://devbox.bc.ca) we are immediatately redirected to https://devbox.bc.ca/cp/home/displaylogin and 'Unable to Connect' browser message comes up. Note that we do not have the extended site-wide SSL enabled, and so ignore the 'Reenable SSL' steps in the upgrade guide.

Interesting that plain 4.2.2.0 works fine, even unpatching back to 4.2.2.0 allows a login. Also that non-portal pages work fine (http://devbox.bc.ca/local/mypage.jsp)
Any ideas?
thanks, bob

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

https login is now the default

Submitted by bwalker on Mon, 2010-06-28 19:07.

Answering my own post...

It would appear that as of 4.2.1, the login page is no longer a secure frame within an unsecure frame, but is now a single html SSL page. So, it should now be normal that
http://devbox.bc.ca redirects the user to https://devbox.bc.ca/cp/home/displaylogin.

Can someone verify this ? If so, it's a shame there's nothing in the release guide about this, it's a great change.

However, still doesn't solve my problem of why patching to 4.2.2.0, then 4.2.2.34, then back to 4.2.2.0, then 4.2.2.68 results in login page not displaying!

bob.

Login

Submitted by ToddTrann on Tue, 2010-06-29 11:56.

Bob,

Ever since we've been on Luminis 4 (and even back to Luminis 3), our login page has been https (the whole thing). However, we did have ssl_lock_on_login=true in configman.

Todd

solved

Submitted by bwalker on Wed, 2010-06-30 13:17.

Thanks to everyone, especially 'The Todd' for responding.

The problem was with server.xml and the keystorepass value. Even though we use the self-signed cert in development, it would appear that this value needs to be filled out, and needs to be the LDAP admin password.

Somehow in the hotfix patch it got changed. The value it took on was the value for the following configman attributes:
pds.admin.password
portal.relate.service_password
No idea how this happened or why.

Editing server.xml by hand, changing the keystorepass value back to LDAP admin password and restarting worked.

Bob.

Syndicate content