BoKS Reporting Manager 7.1 Release Notes

Transcription

1 BoKS Reporting Manager 7.1 Release Notes This document contains information about the BoKS Reporting Manager 7.1 product release from Fox Technologies. It includes the following sections: Revision History Supported Platforms What s New Support For Newer BoKS Manager Versions And Features New Report Fields Fixed Issues Fixed Issues on All Platforms Known Issues Getting Support And Service Revision History Revision: 1 Date of this revision: Revision history: Rev No Date Comments First version. Go to top Supported Platforms BoKS Reporting Manager 7.1 is supported on the following platforms: Vendor Platform Comments Oracle Oracle Solaris 10 on SPARC Oracle Oracle Solaris 11 on SPARC Red Hat Red Hat Enterprise Linux 6 64-bit Red Hat Red Hat Enterprise Linux 7 64-bit BoKS Reporting Manager 7.1 Release Notes Page 1

2 The following database versions are supported for the BoKS Reporting Database: Vendor MySQL Oracle Database Version 5.5 or later or later The following BoKS Manager versions are supported for BoKS Reporting Manager 7.1. BoKS Manager Version Support Platforms 7.1 All supported Note: If you are using any of the BoKS Reporting Packs for NERC, PCI or SOX, note that there are updated versions of each pack for use with BoKS Reporting Manager 7.1. Go to top What s New FoxT Reporting Manager 7.1 features the following improvements: Support For Newer BoKS Manager Versions And Features BoKS Reporting Manager 7.1 includes the following updates to support domains running newer versions of BoKS Manager: Supports operation with FoxT BoKS Manager 7.1. Important: If you are doing an upgrade to BoKS 7.1 and to BoKS Reporting Manager 7.1 from a BoKS version earlier than 7.0 and you use audit logging in BRM 7.1, make sure that all the audit logs are synchronized before upgrading to BoKS 7.1. After BoKS has been upgraded you can upgrade to BRM 7.1. The BoKS audit logging changed in BoKS 7.0, and BRM 7.1 is only capable of reading the new format BoKS audit logs. Note: If you are running SELinux on the Master, ensure that the latest BoKS SELinux policy RPM is installed on the Master before you install or upgrade BoKS Reporting Manager. You can download the BoKS SELinux policy RPM from the FoxT Customer Support website. Page 2 BoKS Reporting Manager 7.1 Release Notes

3 Fixed Issues New Report Fields BoKS 7.1 includes new parameters for Access Rules, and these are added to the access control reports in BoKS Reporting Manager. In addition, you can filter access rule report contents based on the valid time of access rules. Access Reports Filter for Expired User Accounts A new filter for Access Control Reports can be used to include or exclude user accounts in BoKS that are expired and therefore do not have access to BoKS-protected systems in report output. Go to top Issues that have been fixed in this release. Fixed Issues on All Platforms #9804, #4603 REPORT "BRM Domain Status" SHOWS WRONG DATE FOR LAST UPDATE The BRM Domain Status report may show the incorrect date for the last update. The correct date can be found by running the "bjdpm domainstatus" command. As this issue only occurs in environments running certain Oracle driver versions, ensure you are running the latest Oracle driver version to avoid this issue. #9716 LOG CONFIG FILE NOT FOUND WHEN RUNNING bdpjm SCRIPTS An issue discovered in the hotfixes HFBRM-0006 and HFBRM-0007 meant that when running the bdpjm scripts a logger could not be created because the current working directory did not match the path in the log configuration file, AppcontrolLogging.xml. #9704, #13046 BoKS SSH CLIENT NOT USED BY DEFAULT BoKS Reporting Manager used the native SSH client instead of the BoKS SSH client by default. This could cause issues when BoKS Reporting Manager had been configured to authenticate with hostbased in which case the wrong hostkey was typically used. #9701, #12494 HANDLING OF UNEXPECTED LOG DATA If BoKS Reporting Manager encountered a log message that it was unable to parse, it set the status to AU OUT_OF_SYNCH and exited rather than logging the issues to the error log. BoKS Reporting Manager 7.1 Release Notes Page 3

4 #9698, #8226, TFS BRM INSTALLER FAILS TO AUTO-SELECT UID FOR brmuser During the installation of BoKS Reporting Manager, the administrator is asked to specify a user to create. If the UID field for the user was left blank, the install stopped responding. #12834 KSLOG ENTRIES ARE NOT SHOWN IN AUDIT REPORTS The audit log entries for KSLOG do not specify the log type (user or system). The audit log report filter for log type did not handle an unspecified log type in log messages. #12149, #8915 DUPLICATE MEMBERS IN BOKS DATABASE CAUSES DELETING HOSTGROUP TO FAIL Member duplicates in the BoKS database get imported into the BRM database when doing ondemand. When deleting the Host Group in a live feed it failed to remove the members because of the duplication. When then deleting the Host Group an error was returned from the database because it still contained the child members. This issue existed for Oracle. #8925 MUST RESTART BRM AFTER CREATE DOMAIN TO ENABLE SEQUENTIAL MODE If the DomainConcurrency property is set to SEQUENTIAL, BRM must be restarted after creating a new domain in order for the live feed jobs to run in sequential mode. This is expected behavior and is now documented in the Administration Guide. #11952 BRM DATABASE CAN BECOME INCONSISTENT FOR MULTIPLE DOMAINS Running parallel ondemand updates for multiple domains at the same time could cause data from one domain to refer to data in other domains. This problem resulted in some data not being visible in the reports. Also, this resulted in an error when deleting the domain. #7234, TFS , TFS LOCK WAIT TIMEOUT ON TABLE DOMAIN If multiple ondemand or live feed jobs were running in parallel, an error "lock wait timeout" and/or "LockAcquisitionException" sometimes occured for table DOMAIN. If this problem should occur, wait until any current AC or AU job has finished before starting another AC ondemand job. Page 4 BoKS Reporting Manager 7.1 Release Notes

5 TFS AC LIVE FEED ACCESS ROUTES SCALABILITY/PERFORMANCE Lots of access routes with * as target host in combination with many hosts resulted in the AC live feed taking a long time, due to ineffective updates of access route tables in the database. #5642 HOSTGROUP IN LIVE FEED UPDATE INSERTED TWICE The sequence number for Host Group creation in ondemand was not updated correctly. If the succeeding live feed included the same entry, the sequence number could not be compared. This resulted in the Host Group being inserted twice which generated a constraint violation error in the database. TFS UNABLE TO SEE AND SELECT ALL ITEMS IN A DROP DOWN INPUT FIELD When the number of items exceeds 1400 in the database, items above 1400 were not shown in the drop down list when running a report. They were not selectable even when applying a search filter. This made it impossible to run the report for certain objects (for example hosts or users) that exceed 1400 in the list. TFS RETRY TO CONNECT WHEN BOKS IS DOWN The domain went out of sync as soon as the BoKS master/replica could not be contacted. A retry functionality is implemented that keeps retrying to connect until a timeout period is exceeded. TFS OUT-OF-SYNCH WHEN CHANGING HOSTGROUP FOR A USER An exception was triggered in Live Feed when the Host Group of a user was changed. This led to the domain becoming out of sync. #5410 "BOKS TIMESTAMP CHANGED" ERROR AFTER BOKS DB RESTORE For BoKS 6.5 versions, after a restore of the BoKS database and BRM ondemand update the timestamp for the hostgroupmembers table does not get updated correctly. This leads to the domain becoming out of synch in a live feed update for Host Groups. #4903 INSUFFICIENT PRIVILEGES FOR MYSQL USER Ondemand operation required that the database user (brmadmin) had super admin privileges when using the MySQL database. BoKS Reporting Manager 7.1 Release Notes Page 5

6 Known Issues Issues identified in this release, with workarounds where appropriate. #12149, #9700, #8916 DEADLOCK PROBLEM FOR PARALLEL JOBS When parallel live feed jobs are running and competing for the same resources, a deadlock can occur due to the lack of index for the foreign key in the child table. When deleting rows from the parent table it then takes a table lock on the child table. If two jobs are operating on the same table this makes deadlocks in the database likely. A configuration parameter DomainConcurrency can be set in boksbrm.properties to force the live feed jobs to run sequentially. #9699, #8606 LockAcquisitionException ERROR WHEN DELETING DOMAIN When you delete a domain the program returns a LockAcquisitionException error, causing other configured domains to stop responding. WORKAROUND: For methods of mitigating the risk of database locking issues, please see the section Common Issues and Solutions in the Administrator s Guide. #9691, #8593 Optimistic locking failed ERROR DURING AC ONDEMAND UPDATE When performing an ondemand update of AC data to a domain, the update fails and the error log includes the error message Optimistic locking failed. WORKAROUND: For methods of mitigating the risk of database locking issues, please see the section Common Issues and Solutions in the Administrator s Guide. #9694, #8562 EXCEPTION: NOT ENOUGH SPACE The BDPJM returns a Java error similar to the following when trying to create a domain: Error creating domain. Connection problem. Reason : Cannot run program "ssh": error=12, Not enough space #9690, #8548, TFS LOCK WAIT TIMEOUT ON TABLE DOMAIN If a livefeed of AC data does not complete before the next livefeed is due to start, the import fails due to a lock wait timeout on the Domain table. WORKAROUND: For methods of mitigating the risk of database locking issues, please see the section Common Issues and Solutions in the Administrator s Guide. Page 6 BoKS Reporting Manager 7.1 Release Notes

7 #9695, #8461 LONG PARAMETERS OVERFLOW ON REPORTS Reports that feature very long input parameters, for example a very long BoKS username, may present the parameter as overflowing the dedicated field in the report output, leading to an untidy appearance in the report. #9801, #7494 INTERNET EXPLORER 10 & 11 COMPATIBILITY MODE MUST BE ENABLED In order to use the BoKS Reporting Manager web administration interface with Internet Explorer 10 and 11, you must enable Compatibility View in the browser. For details on how to enable this view in your browser, see the description at the Microsoft support website. #9802, #5299 FILES CREATED IN /tmp The ReportEngine may sometimes produce a number of zero length prn* files in the /tmp directory, and these are not automatically removed. These files may be safely removed manually. #9803, #4795 CANNOT CLOSE LOCALE / TZ POPUPS In certain browser versions, when you open the "Set Locale" or "Set Time Zone" popups using the icons in the top bar, you cannot close the popup by clicking OK, but only by clicking the cross button at the top right of the popup. #9806, #946 HIBERNATE EXCEPTION: ROW UPDATED OR DELETED BY ANOTHER TRANSACTION If you change the interval time for live feed updates, then change the interval back again, the following exception may appear in the log: "org.hibernate.staleobjectstateexception: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect)". However, after this exception occurs, BoKS Reporting Manager automatically attempts a new live feed update, which is normally unaffected by this exception. #9807, # 694 DESELECTING ALL LOG TYPE OR SEVERITY CAUSES SQL SYNTAX ERROR When you are running an Audit Log report, and do not select any Log Type or Severity in the Parameters page, the report does not run, instead returning an sql syntax error. BoKS Reporting Manager 7.1 Release Notes Page 7

8 Getting Support And Service If you have a question about a specific item in this document, refer to the case number or title listed at the start of the item when you place your technical support call. For information on our company and products, plus links to sales and support, please see our website: Fox Technologies Inc. All rights reserved Page 8 BoKS Reporting Manager 7.1 Release Notes