en:release:3.09_release_notes
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
en:release:3.09_release_notes [2018/03/05 20:10] – kjdon | en:release:3.09_release_notes [2018/09/26 08:57] – anupama | ||
---|---|---|---|
Line 56: | Line 56: | ||
===== Further instructions ===== | ===== Further instructions ===== | ||
+ | ==== Setting up your Greenstone to run over https ==== | ||
+ | The more secure https protocol is increasingly required by browsers and gradually superseding http. Given that you meet the following requirements and configure your GS3 as below, Greenstone 3 has now been automated to obtain an https certificate for you from the free Certification Authority " | ||
+ | Requirements: | ||
+ | * on unix (linux and mac) systems you need to have sudo permissions | ||
+ | * on windows, you probably need admin rights | ||
+ | * ensure nothing is running on port 80 when you're ready to set up https certification your GS3 | ||
+ | |||
+ | Steps: | ||
+ | - Edit build.properties as follows: | ||
+ | * set '' | ||
+ | * set a value for '' | ||
+ | * Ensure '' | ||
+ | * By default '' | ||
+ | - Make sure you have read and agree with the [[https:// | ||
+ | - Use a terminal to go into your GS3 installation folder, run '' | ||
+ | source ./gs3-setup | ||
+ | ant setup-https-cert | ||
+ | </ | ||
+ | - Once the setup-https-cert ant target has finished, you can start your web GS3 server by either running the gs3-server application or by running "ant start" from the terminal. | ||
+ | - If you ran the gs3-server application, | ||
+ | - Once your https home page has loaded, confirm that your certificate is properly installed by looking for a green padlock next to the address bar. (Depending on your browser, you can click the padlock to get more information on the certificate issuer.) | ||
+ | |||
+ | There are 2 more https-related automated ant targets you can run from the command line: | ||
+ | * '' | ||
+ | * '' | ||
+ | |||
+ | **Important: | ||
====Changing the admin password==== | ====Changing the admin password==== | ||
Login to the administration page, ' | Login to the administration page, ' | ||
Line 220: | Line 247: | ||
===== Important Changes and Bug Fixes ===== | ===== Important Changes and Bug Fixes ===== | ||
- | + | * HTTPS support: Greenstone will obtain a certificate from the Certification Authority Let's Encrypt to run your GS3 tomcat over https. However, on unix systems (macs and linux), you will need to have sudo permissions. And on Windows you will probably need admin rights. | |
===== IMPORTANT information ===== | ===== IMPORTANT information ===== | ||
Line 226: | Line 253: | ||
==== Troubleshooting ==== | ==== Troubleshooting ==== | ||
+ | |||
+ | === Your browser doesn' | ||
+ | **The issue:** | ||
+ | The following scenario can occur if you set up GS3 with https, and your server.protocols property in build.properties contains both '' | ||
+ | |||
+ | Switching between visiting your Greenstone 3 digital library (DL) using http and https URLs can result in the http version of the pages not remembering your login details despite you logging in. This can happen if you ever started off with the https version of the URL to a Greenstone3 DL page and then moved to using the http version of your GS3 URL, or if you ever logged in to your GS3 over https and then attempt to log in later using http. | ||
+ | |||
+ | **The solution:** | ||
+ | The solution is to either start a private window if you want to access your GS3 DL pages over http, or to first clear your browser cookies related to your GS3 DL before swapping from https to http. | ||
+ | |||
+ | **The cause:** | ||
+ | Using https causes session cookies to have the secure flag set to true. When a session cookie has the secure flag thus set, non http URLs cannot return that cookie in their subsequent requests to the server. Only https URLs can. See https:// | ||
+ | |||
+ | <!-- | ||
+ | If you're on firefox and you just logged in to to a running Greenstone 3 digital library (DL), but visiting subsequent pages in the DL shows you that it has forgotten you're logged in, then you're probably encountering a restriction that your firefox browser has. | ||
+ | |||
+ | **NOTE:** We've encountered this problem on Firefox and only for http URLs that use the domain/ | ||
+ | |||
+ | To confirm that it only happens on firefox, try another browser first. For instance, Chrome. If your being logged in is being remembered on Chrome, then you've confirmed that the phenomenon is firefox-specific. | ||
+ | |||
+ | Things to try: | ||
+ | * Close all tabs in firefox and restart firefox in the usual way. Try logging in and visiting other pages to see if it remembers your login now. | ||
+ | * If that made no difference, try launching a Private Window (Ctrl + Shift + P on firefox), visit your GS3 digital library and login again, then check whether it's being remembered across Greenstone pages now. | ||
+ | * If that also made no difference then the most likely cause is Firefox plugins or extensions or addons, or maybe its hardware acceleration feature needs to be switched off. To find out if any of this is the case, quit firefox once more by first close all tabs in firefox and quit it. Then try re-launching Firefox in Safe Mode as explained at https:// | ||
+ | |||
+ | > [[https:// | ||
+ | > A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there? | ||
+ | |||
+ | (If that doesn' | ||
+ | |||
+ | After relaunching Firefox in Safe Mode, test whether your login details are being remembered this time. If it works now, it could indeed be an addon/ | ||
+ | --> | ||
=== Mac Installer fails === | === Mac Installer fails === |
en/release/3.09_release_notes.txt · Last modified: 2023/03/13 01:46 by 127.0.0.1