Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Welcome to the LawMaster Knowledge Base

Your one stop resource for everything LawMaster - from the initial setup, to usage of all the functionality LawMaster has to offer. You can also use this space to search and view the various help topics, create best practices and common problem articles.




Livesearch
spaceKeyLF
sizelarge
additionalpage excerpt
placeholderHow can we help you today?
typepage

Old Request System

If you would like to view your requests created before 04/06/2018 please click here.

Click here to view the latest Release Notes for LawMaster.



Recently Updated Articles      


Recently Updated
showLabelsfalse
max5
themesidebar
showSpacefalse
sorttitle
excerptTypesimple
cqllabel = "accounting"
labelsrecent

Popular Articles (By Label)


Popular Labels
count10


Alerts:

Elasticsearch - Log4j2 Security Update 

On December 9, 2021 a high severity vulnerability was announced in the Apache Log4j 2 module, commonly referred to as Log4Shell or CVE-2021-44228 ESA-2021-31.

The Elasticsearch Advanced Search feature in use by LawMaster, from the Portugal release onwards, makes use of this module. In accordance with the latest information available from Elastic here, all customers on a Portugal version or above (10.14.361 or higher) of LawMaster require a minor change to a configuration setting on the Elasticsearch server in order to fully protect it. This change has already been made for all hosted services and as such, hosted customers do not need to take any action. If your Document Management server is not hosted by LawMaster, then please refer the below instructions to your IT/Managed Service Provider for action.

For Portugal releases or above using Elasticsearch 7.7.1:

1. Connect to your Elasticsearch server (typically the LawMaster Application server) using a user with Administration rights.
2. Navigate to the Elasticsearch JVM configuration directory. By default this should be: C:\ProgramData\Elastic\Elasticsearch\config\jvm.options.d
3. Create a text file in this directory called “jvm.options”. Note that Administration rights will be required to save changes in this location. If this file already exists, go to the next step.
4. Edit the “jvm.options” file created and add the two lines below:
o # Elasticsearch remediation for Log4J/Log4Shell exploit
o -Dlog4j2.formatMsgNoLookups=true
5. Save the “jvm.options” file.
6. Open the “Services” application
7. Location the Elasticsearch service, right click and select Restart. Note that this will cause a brief outage on all Elasticsearch searching and indexing.

Please contact the Helpdesk if you need any further support with implementing this fix.


Downloads


Release Notes


Release Webinars


Awesome Icon
color#0077B5
size20pt
iconfa-linkedin
  
Awesome Icon
color#0084b4
size20pt
iconfa-twitter
  
Awesome Icon
color#3B5998
size20pt
iconfa-facebook-square