New Release – GoldMine Premium Edition 2018.2

What’s changed in GoldMine 2018.2

GoldMine Premium Edition/ GoldMine Connect

Password validation

• Due to the added password complexity rules (explained in What’s New below) the password validation at login is now case sensitive.
• In previous versions of GoldMine all user passwords were converted to UPPER case when saved in the database. Existing users must enter their password using all UPPER case letters at login, otherwise the user will not be able to login.

What’s New in GoldMine 2018.2

Includes all functionalities added after GoldMine 2018.1.0

GoldMine Connect (GoldMine Web)

Use of https by default

• For new installations GoldMine Connect will be installed to use port 443 by default
• The https implementation requires a certificate installed on the web server
• If you don’t have a certificate from an external trusted authority, then you must create a self-signed certificate. Please see https://community.ivanti.com/docs/DOC-55003 for more information.
• For existing installations there will be a redirect from http to https
• Please note that in the case of existing installations, we use URL Rewriter to perform the redirect. If URL Rewriter is not installed previously, then the GoldMine Connect installer will download it from the internet, which will require an internet connection, and do the installation.
• In the case of an upgrade if there is no certificate installed on the web server, the admin must configure a certificate prior to the upgrade. If you don’t have a certificate from an external trusted authority, then you must create a self-signed certificate. Please see https://community.ivanti.com/docs/DOC-55003 for more information.

Email Merge Code for primary and additional contact

• Added E-mail Merge Code in Contact Record > Details section > Email address
• Added E-mail Merge Code in Contact Record > Additional Contacts section
GoldMine Link for Microsoft Outlook

Upgrade of Redemption library

• The Redemption library was updated to version 5.16

Support for TLS 1.2

• In 2018.2 version we added support for TLS 1.2, the most used cryptographic protocol
• TLS1.2 requires SQL Server 2008 SP4 / SQL Server 2008 R2 SP3 or newer

GoldMine Premium Edition

Chilkat upgrade

• The Chilkat library was updated to version 9.5.0.71. The following known issues in GoldMine were fixed by this library upgrade:
▪ The boundary string appended to the end of Gmail emails will no longer be added
▪ Emails with the charset charset iso-2022-jp will be properly parsed
▪ Some spaces that were being added to the subject of emails will be fixed/removed (at least for HTML emails)

E-mail center encoding

• If the “Encode E-mails using character set” value is empty in a user’s E-mail Options, GoldMine will use “utf-8” as the default character set.
• The following charsets are fully supported in the current version:
▪ UTF-8
▪ ISO-8859-1
▪ ISO-8859-15
• Full support of UTF-8 in the body of the emails. Although in previous versions we could set the utf-8 as a charset we could not compose emails is some foreign languages (e.g. Arabic), but we could receive them. This issue was fixed in the current version.
• Enabling the Dynamic Update Exchange protocol (DDE)

Open SSL upgrade

• Open SSL library was upgraded to version 1.0.2n which is their latest LTS version
• This version uses TLS 1.2 by default

TLS 1.2 support for database communication

• Support for TLS 1.2, the most used cryptographic protocol, was added
• TLS1.2 requires SQL Server 2008 SP4 / SQL Server 2008 R2 SP3 or newer

Encrypted database connection

• GoldMine uses protocol encryption and validate database server certificate by default to adhere to the “Secure by default” security principle and “Privacy by default” principle
• A new step “Database Encryption” was added to the installer, where the user is asked if he wants to validate that the database server certificate is a trusted one. The default option is Yes.
▪ If a certificate was configured on the database server prior to beginning installation or upgrade and that certificate is trusted, then the user should leave the default selection and press Next button
▪ If on the database server there is no trusted certificate configured, then the user must choose No in this step, otherwise GoldMine will not be able to connect to the database after the installation/upgrade is complete.

User password complexity

• As a part of security enhancements, a password complexity is in place. All defined passwords must respect the following rules:
▪ Have a length of 8 characters or the length setup by the administrator in Tools > Configure > System Settings > Password Policy
▪ Contain 1 uppercase character
▪ Contain 1 lowercase character
▪ Contain 1 digit
▪ Contain 1 special character like! #@$%&/ ()? etc.
• The password complexity is enforced by default for newly created users
• For existing users, password complexity will not be enforced by default, but the user must enter existing password in all UPPER case. Once the user changes the current password, the newly set password must to respect the password complexity.

Administrative user changes

• For all fresh installations of GoldMine, the user named “MASTER” will not be created by default. A new step was added at the end of the installation process requiring the creation of a user with master rights which will have full administrative access to the application.
• For existing installations there will be no changes to the user named Master, however we advise that the default password be changed or to create a new user with full administrative rights and disable the default one, to strengthen the security of your application.

Addition of a read-only account for SQL Query and Filters

• The SQL Query Editor functionality is required to be enabled from Edit Alias window and a read-only user
to be set
▪ A section “SQL Query” was added to Edit Alias (Tools->Databases->Alias Manager->Edit Alias) to enable the SQL Queries functionality and create the read-only user
▪ Once the functionality is enabled, define a username and password and press the OK button to automatically create the MS SQL user with the appropriate access in the database
• To be able to create/update Filters or Groups based on SQL Query, the SQL Query Editor functionality must be enabled and the read-only database user defined.

Versioning of installation files

• All .exe and .dll files created by the GoldMine application during installation are versioned
• The version on the files are the same version you will find in Help > About GoldMine screen

File signing

• All .exe and .dll files created by the GoldMine are signed, using SHA256 digest signature.
SQL Native Client usage as Database connector
• SQL Native Client 11 is used as a Database Connecter starting with GoldMine 2018.2
• If SQL Native Client 11 is not previously installed on the machine, then it will be downloaded from the internet and installed by the installer. This requires an internet connection during installation.

Read the complete GoldMine 2018.2 Release Notes