Monetra 8.5.0 was released March 6th. This is a security release so all Monetra users will be expected to upgrade to this release to maintain PCI compliance.
Release notes for the changes are listed below.
--
Monetra 8.5.0 released [security]
March 6, 2017
Effective 03/06/2017
Monetra 8.5.0 has been released to the public and is a security and feature enhancement release.
This release is highly recommended for all users of Monetra and should be considered the most modern and stable release available.
Changelog
Database Schema: v4.4 (compatible with v4.0)
Security:
OpenSSL has been updated to v1.0.2k to correct numerous flaws. For more information please see: https://www.openssl.org/news/secadv...170126.txt
#2225. The Windows Service path is now created as quoted to prevent attacks.
Certifications:
First Data CardNet/North and Nashville/North (EDC) have been recertified with added support for EMV Debit and EMV Contactless.
Features:
#1977. When creating an MADMIN sub-user with AuthAs permissions, it is now possible to assign what permissions that sub-user can authenticate using.
#2089, #2228, #2232, #2237. Logging has been modified to both reduce the number of lines per request as well as enhance tracability and provide additional summary data to assist with monitoring Monetra.
#2164. Add the ability to view the locked status of subusers, and to specifically unlock subusers as a normal user has been added.
#2218. Reduce database commits to every 24hrs on usage of both CardShield device keys, and Product Licensing to reduce database load.
#2200. It is now possible to request the same token be returned when tokenizing the same card. It is also possible to now tokenize non-financial cards or cards that couldn't previously be tokenized strictly for the possibility of checking for duplicates.
#1431. Allow mass purging of expired DSS tokens and automated recurring history as both MADMIN and normal users. This also allows adding of automated tasks for this purging.
#2171. The Monetra loopback emulator can now simulate a duplicate batch failure message. If the batch contains any transaction with a dollar amount of $99999.00, it will trigger the failure.
#1598. If the cardtypes field is left blank when adding a user account, it will default to activating all cardtypes supported by the processor.
Fixes:
#1806. If there is a failure fetching fresh E2E keys from a processor, the last successful cached version will be returned.
#2168. An error is now returned if the industry code sent during an adduser or edituser is not supported by the chosen processing institution.
#2170. When adding subaccounts for routing different cards to different processors, or settling to a different processor than accepts the authorizations, Monetra will now sanity check the account configuration and return errors if the route chosen could be ambiguous.
#2172. When adding US Debit support to a merchant account, it now forces all US Debit types to be active as it was a misconfiguration if not properly configured.
#2196. For cards that do not require the expiration date be validated, the format of the expiration date must still at least be valid.
#2230. For VoiceAuth transactions, the user-entered approval code is now validated to ensure it is exactly 6 characters.
#2240. User deletion has been optimized to delete data in chunks to reduce database load and locks.
#2226, #2227. Product licensing and CardShield device license enforcement has been relaxed to allow "grace" licenses, and to auto-purge unused licenses.
#2001. Email addresses entered for the purpose of settlement email notifications are now sanity checked to ensure they are in a valid format to attempt to eliminate message sending failures.
Integration Changes:
#2089, #2228, #2232, #2237. Monetra's log file format has changed. Those with automated log parsing and monitoring systems may need to enhance those tools to work appropriately with these changes.
#1977. subuseradd and subuseredit for MADMIN users now take additional fields of authas_trantypes and authas_admintypes that can be used to restrict the actions that can be performed on the accounts. If not specified, it defaults to all permissions, the special keyword of all can also be used to explicitly allow unlimited access. subuserlist will also return new columns of the same names.
#1977. New MADMIN action=sysinfo type of sysinfo=trantypes. This new sysinfo request will return 3 response parameters, madmintypes, trantypes, and admintypes as a pipe-delimited list of all known transactions for the respective class.
#1977. The getperms request as an MADMIN user now also returns authas_trantypes and authas_admintypes.
subuseradd and subuseredit's trantypes and admintypes fields can now take a special keyword of all to explicitly indicate all permissions.
#2164. subuserlist adds a new column of locked to indicate if the account is currently locked or not due to password failures.
#2164. New user-level admin function type of unlockacct to unlock an account due to too many password failures. This takes a single argument of user to specify the username to unlock.
#2200. When inserting a recurring card, either explicitly through recurringadd, or when using tokenize=yes with a transaction, a new flag of matching_token=yes can be passed to return the original token for the same card.
#2200. A new token type parameter of nontrans can be used for tokenizing non-financial cards, or cards that otherwise would not be allowed to be used for tokenization.
#1431. Rename of admin=recurringclear to admin=recurringpurgehist, an alias has been added for compatibility.
#1431. Addition of MADMIN action=recurringpurgeexpired and user-level admin=recurringpurgeexpired. This new action purges expired cards within the DSS system and take a a single argument of keep_months=# specifying the number of months after a card is expired that should be kept on file. All older tokens will be purged.
#1431. New Cron Task type of purgeexpired available for both normal users and MADMIN users. This task will purge expired cards within the DSS system. The cron_data value is the number of months after a card is expired that should be kept on file. All older tokens will be purged.
#1431. New Cron Task type of purgerecurhist available for both normal users and MADMIN users. This task will purge history of automatic recurring and installment payment attempts. The cron_data value is the number of days to keep.
ThirdParty Library Updates:
SQLite updated to 3.16.2
C-Ares updated to 1.12.0 + PR#81 (Windows Route Metric patches).
OpenSSL updated to 1.0.2k
--
Monetra Administrator v8.5.0 released
March 6, 2017
Effective 03/06/2017
Monetra Administrator v8.5.0 has been released to the public and is considered a feature and maintenance related release.
This release is strongly recommended for all users of Monetra and should be considered the most stable available.
Changelog
Subuser perms, allow specifying auth as perms.
Add cron task for purging recurring history.
--
Monetra Client v8.5.0 released
March 6, 2017
Effective 03/06/2017
Monetra Client v8.5.0 has been released to the public and is considered a feature and maintenance related release.
This release is strongly recommended for all users of Monetra and should be considered the most stable available.
Changelog
Subuser perms, allow specifying all perms.
Add cron task for purging recurring history.
--
Monetra Installer 1.0.25 released
March 6, 2017
Effective 03/06/2017
Monetra Installer v 1.0.25 has been released to the public and is a maintenance release.
This release is strongly recommended for all users of Monetra and should be considered the most stable available.
Changelog
Update to OpenSSL 1.0.2k
Support for packages including symlinks
OS/400 PASE environment support
Windows Administrative privileges check for LocalSystem user
--
Monetra Manager v8.5.0 released
March 6, 2017
Effective 03/06/2017
Monetra Manager v8.5.0 has been released to the public and is considered a maintenance related release.
This release is strongly recommended for all users of Monetra and should be considered the most stable available.
Changelog
Miscellaneous fixes.
--
