FIXICC-Agent 2.8.1 Release Notes (24-10-2015)
Critical bugs and fixes
- Fixicc-agent on windows don't start with default configuration in security.properties file
- Passwords being written to logs in plain text
Improvements and New Features
- Fixicc-agent log contains SCM Revision
Changes in configuration files
conf/log4j.properties:
[+] log4j.appender.file.layout.MaskPattern3=com.epam.fixicc.log4Wrapper.MaskPatternRegex
[+] log4j.appender.file.layout.MaskPattern3.Pattern=assword = (.*?)\n
[+] log4j.appender.file.layout.MaskPattern3.Mask=assword = *****\n
[+] log4j.logger.org.apache.shiro.config=INFO, file
[+] log4j.logger.org.apache.commons.beanutils=INFO, file
FIXICC-Agent 2.8.0 Release Notes
Critical bugs and fixes
- On Windows FIXICC Agent is not started using startService.bat.
- On Windows FIXEdge + FIXICC components intalled into Program Files generate errors.
Improvements and New Features
FIX Admin Protocol was updated to version 3.0
- Username and Password are optional for admin session FIXICC Agent. If those properties are absent agent is trying to find Username and/or Password properties in engine.properties. If engine.properties also doesn't contain credentials, FIXICC Agent tries to connect without them.
- YAJWS was updated from version 11.09 to version 11.11 to fix bug with FIXEdge + FIXICC components intalled into path that contains whitespace.
- Remove all security sensitive data from agent configuration files.
- SSLConfigFile property added to agent.properties for specifying SSL arguments in separate file.
- contextFactory.systemPasswordFile property support added to security.properties for specifying LDAP password in separate file.