Infrared360 Release 6.5
release date: 10/01/2021
Questions and Issues should be sent to: support@avadasoftware.com
CONFIDENTIALITY NOTICE:
You are hereby notified that any use or disclosure of this information is strictly prohibited.
If you have received this transmission in error, please send document to support@avadasoftware.com
---------------
6.5.0.1
---------------
1. Repository performance enhancement
2. 2067 reason code on some IBM MQ ZOS connections
3. Saving new Subset issue
4. Updated logo image when clicked to go to avadasoftware.com
5. Properties not displayed on User list screen
----------------------
6.5.1.4 Enhancements:
----------------------
1. Security additions OWASP and HTTP Header defense
----------------------
6.5.1.6 Fixes:
----------------------
1. Fixed issue with Broker Statistics service not collecting for IIB version 9
2. Service Logger and Service Logger Alert will fail to save if the Master repository host field is greater than 36 characters long
3. Alert Copy sets Alert to inactive was not reseting the state of the Alert if Alert being copied was firing
4. Fixed IBM MQ Subscription table 'destination' not showing actual destination when clicked on.
5. Login content was not showing on login page when set in client custom
6. Grid disappears when you specify double qoutes in the grid filter area
----------------------
6.5.1.6 Enhancements:
----------------------
1. Add RFH2 insertion capability to IBM MQ message modify screen
----------------------
6.5.1.7 Fixes:
----------------------
1. IBM MQ MQTT Channel processing and viewing
----------------------
6.5.2.0 Fixes:
----------------------
1. IBM MQ Message Flags not showing correctly on message list screen
2. Infrared360 SSO login processing fixes
3. IBM MQ Usage Page sets was not showing on Usage screen
----------------------
6.5.2.0 Enhancements:
----------------------
1. LDAP Reconcile Service adjusted to support User Collection disassociation, proper User locking based on multiple LDAP Reconcile Services.
2. Added last login date to SSO entry page
3. IBM MQ retrieving handles performance adjustments
----------------------
6.5.2.2 Fixes:
----------------------
1. Collection View was showing duplicate Objects on navigation screen when the Collection has more than one connection associated to it.
2. Channel Instance status determination adjustments for Alerting
----------------------
6.5.2.2 Enhancements:
----------------------
1. Updated online documentation
2. Added audit for closing a QM Connection Object that is part of the Queue Manager server
----------------------
6.5.3.0 Fixes:
----------------------
1. MQSC commander was not auditing modify MQSC commands
2. Adjusted CsrfGuard setting and processing, removed referrer from HTTP Header to deal with potential security issues involving referrer.
----------------------
6.5.3.0 Enhancements:
----------------------
1. Kafka Topic find performance increased
2. Kafka Topic Message list and modification added functionality (summary, clear, delete)
3. Kafka Topic view message screen added
4. Kafka Protobuf implementation
5. Subset scrollable list capability
6. Adjust scheduler calendar to 'auto', it would be hidden in some cases.
7. Audit Server service adjusted to use ; (semicolon) as opposed to , (comma) for a regular expression delimiter. The ',' is a valid regular expression character and the system can get confused.
8. Report paging adjusted to prevent multiple titles in CSV file formats
9. Infrared360 will now export multiple IBM MQ messages into a zip file with extension (ir3zip) as opposed to zip. This will allow the system to tell the difference between a zip file not intended to have Infrared360 messages and zip files that do have Infrared360 messages.
----------------------
6.5.3.2 Fixes:
----------------------
1. Fixed issue with labor-day-obs (observed) not being valid in XRDL expressions
2. Cache-Object Service not processing IBM MQ subscription information
3. Adjusted SNMP service, changing OIDs for information, MIB adjusted
4. Adjusted Channel Report Qmgr Name column in repository to 72 as opposed to 48
5. Kafka fetching of Consumer Groups was not working when multiple connections selected
6. If connected using Azure SSO the primary host was not being monitored correctly
----------------------
6.5.3.2 Enhancements:
----------------------
1. Made adjustments to Infrared360 to support SSO Azure
----------------------
6.5.3.6 Fixes:
----------------------
1. Update of bouncy castle Jars for security reasons
2. Increase JMS property input textbox from 255 to 65536, fixed issue using ^ as a value in the JMS data. The ^ is used as a delimiter internally.
3. Added mechanism to hide password information from debug information
4. IBM MQ stopping channels on navigation screen would only process one channel at a time
5. REST GET IBM MQ connection not working
6. Processing IBM MQ messages setting "Message Processing By Depth" had performance issues when viewing messages on the message list screen
7. Fixed Invalid Console message when saving a Role.
8. Queue History Charts do not display data when not monitored.
----------------------
6.5.3.6 Enhancements:
----------------------
1. Added new IBM MQ v9.2.3 attributes in IBM MQ (STREAMQ, STRMQOS) streaming queues
2. Check for existence of IBM MQ queue 'SYSTEM.MQXR.COMMAND.QUEUE' to determine if Telemetry is enabled on Queue Manager
3. Increased the size of the password field for the SMTP email Service
4. Updated Tomcat to 9.0.73
5. Update Struts Jars for security updates
6. Update HSQL jar for security updates
7. Update IBM MQ Jar to 9.3.2.0
8. Update Bouncy Castle Crypto Jars (for requirement of IBM MQ updated Jar)
----------------------
6.5.3.6 Fixes:
----------------------
----------------------
6.5.3.8 Enhancements:
----------------------
1. Increased password entry size to 128 from 64
----------------------
6.5.4.0 Enhancements:
----------------------
1. If an IBM MQ message has more than 1 DLH header we should remove all DLH headers if more than 1 DLH header exists
2. Cluster Table filtering for IBM MQ Navigator
----------------------
6.5.4.2 Fixes:
----------------------
1. Kafka SSL adjustments
2. Adjustments to allow root collection to be used as a single point of access with no rights for full visibility to connections
3. Fixed internal user caching issues
