Change Log
All notable changes to this project will be documented in this file.
Table of contents
- UPDATES INCLUDED IN V1.2.6
- UPDATES INCLUDED IN V1.2.5
- UPDATES INCLUDED IN V1.2.4
- UPDATES INCLUDED IN V1.2.3
- UPDATES INCLUDED IN V1.2.2
- UPDATES INCLUDED IN V1.2.1
- UPDATES INCLUDED IN V1.2.0
- UPDATES INCLUDED IN V1.1.6
- UPDATES INCLUDED IN V1.1.5
- UPDATES INCLUDED IN V1.1.4
- UPDATES INCLUDED IN V1.1.3
- UPDATES INCLUDED IN V1.1.2
- UPDATES INCLUDED IN V1.1.1
- UPDATES INCLUDED IN V1.1.0
- UPDATES INCLUDED IN V1.0.12
- UPDATES INCLUDED IN V1.0.11
- UPDATES INCLUDED IN V1.0.10
- UPDATES INCLUDED IN V1.0.9
- UPDATES INCLUDED IN V1.0.0h
- UPDATES INCLUDED IN V1.0.0g
- UPDATES INCLUDED IN V1.0.0f
- UPDATES INCLUDED IN V1.0.0e
- UPDATES INCLUDED IN V1.0.0d
- UPDATES INCLUDED IN V1.0.0c
UPDATES INCLUDED IN V1.2.6
GitHub Issue #79 - “External Org” users getting improperly categorized as Known Guests
GitHub Issue #78 - External users by organization name is case sensitive
GitHub Issue #72 - Directory Assistance processed differently based on sequence of loading server docs
UI/UX Issues in Scan Wizard
- “Environment Scan Results” is not displaying the list of additional Domino Directories found
- “User Report Tool” Scan tab should no longer allow the user to change the location of the User Report Tool.
User Report Tool Selection Change
The User Report Tool should only be enforced if the user indicates that they are calculating External Users. If they are only calculating CCB users, the User Report Tool should be optional
UPDATES INCLUDED IN V1.2.5
With DLAU V1.2.5, the new “Highest Access Level” change for External Users (CCX Licenses) now allows these users to have “Editor” ACL Access. In order to properly calculate this new level, the “User Report Tool” has now become a reuiqrement for calculating External users (CCX Licenses). Please refer to the following webpage for more details: User Report Tool Instructions
Change to CCX “Highest Access Level” logic to match new CCX Licensing requirements (now allowing “Editor” ACL Level for CCX licensed users)
GitHub Issue #74 Regression Issue: Directory Assistance “Disabled” Flag only honored when “Domain Type” is set to “LDAP”
GitHub Issue #71 External (CCX) Users Who Are Not Listed in Entitlement Tracking Are Being Recognized as CCB Users when selecting External Organization
GitHub Issue #70 Wrong categorization in “User Information” view due to spelling mistake
GitHub Issue #66 Known guests specified by org calculating as CCB due to missing logic
GitHub Issue #64 Selected Org/OrgUnit in the Known Guest Identification dialog are not marked as Known Guests. (a part of #66)
GitHub Issue #53 CCX not properly detected by OU/OrgSelected
UPDATES INCLUDED IN V1.2.4
DNEXT-23869 Report to include Domino server versions
DNEXT-24782 Make DLAU work with a readonly user with the appropriate rights
Idea DOMINO-I-2537 - DNEXT-23865 Support MacOS
DNEXT-26713 Save the server versions as a reference for each scan
DNEXT-23868 Note when server access is setup to allow wildcarded usernames
Issue #19 - DNEXT-23870 Add new export category and create directory if it does not exist
DNEXT-26644 New version available string is missing the new version title
DNEXT-26672 Error when dividing by zero when creating the digital signature
DNEXT-26677 User information from primary directory is lost when they also exist in another scanned directory
DNEXT-26710 Attempt to fix situations where user receives ERROR: Object variable not set #: 91, line: 3
DNEXT-26795 Correct the spelling of “signing” on “signing” page
DNEXT-26878 utility is duplicated on the Nomad page
UPDATES INCLUDED IN V1.2.3
DNEXT-26195 - Include DLAU version in the emailed report
DNEXT-26190 - Global variable was being updated incorrectly causing incorrect error message
DNEXT-25836, DNEXT-25837 - addressed typo and string updates
DNEXT-26194 - Recompiled LotusScript with 32-bit compiler
DNEXT-25997 - added additional logging output behind Notes.ini DLAU_VERBOSE_MODE=1
UPDATES INCLUDED IN V1.2.2
DNEXT-23866 - Check for new version
DNEXT-24943 - Include user names from entitlement tracking in user counting
DNEXT-24797 - Fix string in dialog that warns the user they don’t have appropriate rights to the names.nsf
DNEXT-24798 - Fix string in dialog that warns the user they don’t have the appropriate role in the Domino Directory
Issue #50 - DNEXT-25113 Observation information is not accurate when non-Domino LDAP is used as authentication
DNEXT-25221, DNEXT-25419 - Admin server is changing when additional directories are identified
DNEXT-25782, DNEXT-25635 - Incorrect error message due to improper casing on file naming comparison
DNEXT-25742 Corrected misspelled word
DLAU_VERBOSE_MODE=1 with the Notes.INI set before beginning the scan, the logging has been enhanced to capture the output in the scan log as well as logging additional information. ___
UPDATES INCLUDED IN V1.2.1
DNEXT-23861 - Added support for scanning Directory Assistance on all servers in the environment.
Idea Domino-I-2499 - DNEXT-23784 - The Customer Name, HCL Customer, etc. can now be stored in a configuration document.
DNEXT-24589 - Added the ability to output logging to the status bar to give the scanner an improved experience to understand progress. Set DLAU_VERBOSE_MODE=1 in the Notes.INI before beginning the scan.
DNEXT-23852 - Version of DLAU is now included in the printable report as well as it is stored on the results of each scan to see how scans change over releases.
DNEXT-23855 - Addressing an issue when Domino is used as LDAP server
Issue #54 - DNEXT-24094 - Logging improvements have additional spaces around each functional area of scanning for visual improvements.
Issue #34 - DNEXT-23853 - Export CCB Users does not provide content
Issue #39 - DNEXT-23780 - Clicking on “Deny Access Users” opens the view “dagroups” instead of “UserInfo”
Issue #41 - DNEXT-23856 - Issues with Directory Catalog not in root directory
Issue #46 - DNEXT-23854 - Bug when DA is not trusted for credentials
Issue #47 - DNEXT-23857 - External (CCX) Users Who are not listed in Entitlement Tracking are being recognized as CCB Users
DNEXT-23771 - Clicking on the pop-up help does not work and is missing in certain situations.
DNEXT-24588 - UI shifts when selecting an entry in the “Observations” field on the results page if there is a value that is too long
Issue #29 - DNEXT-24491 Server names are reported incorrectly in an Observation
UPDATES INCLUDED IN V1.2.0
DLAU is now shipped as a template
DLAU is now signed by Open Source Template/Domino Development
Modified non-warranted license included
UPDATES INCLUDED IN V1.1.6
Due to a failing LotusScript Method, the time difference calculation of when the user’s Notes Certificate is expiring was not functioning correctly if the Notes Certificate expiry date is more than 69 years into the future.
UPDATES INCLUDED IN V1.1.5
The methods for indicating the version of DLAU has changed. In DLAU, there is now a Shared Field that is used for displaying the DLAU version.
The User Interface for the list of Observations and their decrpitions/instructions has been adjusted to provide more room for the descriptions/instructions.
An adjustment has been made to the User Information scan to accommodate for Person documents that were created in a background process that do not contain all Field values that are expected.
The Field Description popup has been adjusted to provide proper messages for CCB and CCX user counts.
UPDATES INCLUDED IN V1.1.4
Each of the DLAU Scans will now log any errors that are encountered during the scan process. If a critical error is encountered, the user will be provided the opportunity to view the Scan Log.
For the message asking the user if they has External Users / Known Guests, the buttons on the message have been changed to “Yes” and “No” to reduce user confusion.
During the User Count Calculations, there has been identified a LotusScript Regression Issue in newer versions of the Notes Client (V12.0.2) where a call to obtain a collection of documents can fail to return the proper results if more than one Search Key is used.
UPDATES INCLUDED IN V1.1.3
In the Scan Wizard, if the “Cancel’ button is pressed prior to the completion of all scans, the user is presented with an error message “Division by zero”.
If there are no CCX or Known User counts, the Report page may cause a calculation error.
UPDATES INCLUDED IN V1.1.2
If all different User License types are not captured in a Domino environment, the Report page may cause a calculation error.
UPDATES INCLUDED IN V1.1.1
There is now a new set of user calculations included on the “Scan Results” page to display the various User Counts for active users over a 1-year (365 days) time period.
When prompted for “External User Calculations” during the HCL Domino Environment Scan, the list of Orgs/OrgUnits was not being populated properly due to an incorrect listing in the completed Domino environment scan.
If a user’s name in their Person document contains a quote ( “ ), the Deny Access Groups scan would fail with a LotusScript error.
UPDATES INCLUDED IN V1.1.0
On the “Printable Report” screen, add the ability for the user to send the results to HCL using a specially formatted email.
Calculate “Known Guests” in a similar fashion to how “CCX Users” are calculated, with the “Highest ACL Level” check to ensure that the user has ACL Level “Reader” or lower
Adjust “User Information” View to show the User Categories (“CCB Users”, CCX Active Users”, “CCX Inactive Users”, “Known Guest Users”)
Update the “Printable Report” screen to include the “CCX Inactive Count” and “Known Guests Count”
On the “Printable Report” screen, update the instructions for use and message for US Federal Government customers
Sort the Members List on the Deny Access Group documents
For the “External Users” dialog, ensure that values are selected if the user clicks the “OK” button
UPDATES INCLUDED IN V1.0.12
Remove any reliance on JavaScript code. This is to allow organizations that have user Policies that block usage of JavaScript in Notes applications
The DLAU is now backwards compatible to Lotus Notes V7.0.2
Modify the “Required Fields” for the “Printable Report” to make user information optional (GDPR Compliance)
Adjust the layout of the “Printable Report” so that it shows the correct User Counts dependent on how the DLAU was run (with or without CCB/CCX counts)
Modify the method for generating the final User Counts to occur at the end of the scanning process so that the User Counts are based on the final results, not partial results
UPDATES INCLUDED IN V1.0.11
Remove “# Members” column from “Deny Access Groups” View to lessen the confusiojn between the # of user names listed in the Deny Access Group versus how many Deny Access Users were discovered in the Domino environment
Add a disclaimer to the “Printable Report” screen for US Federal Government clients indicating who to limit sharing the results of the DLAU with
Add a message to the “Scan Results” screen when 1 or more Security Observations are discovered
Update the “Printable Report” screen to include the “CCX License Count”
Modify method for displaying the number of Deny Access Groups that are captured in the DLAU
The labels for CCB Users, CCX Active Users, and CCX Inactive Users were being displayed when those calculations are not being performed
When calculating “Mail Users” the DLAU was not checking if the Domino Mail server that the user was configured for is an Active Domiuno server
The DLAU was reporting that a LDAP Directory was in use when the configured LDAP Directory was disabled
For Pre-V12 Domino environments, the “User Report Tool” area on the “Scan Results” screen was displayed with blank values when the “user Report Tool” was not selected
Users were receiving a sporadic “Object Variable Not Set” error when attempting to set a value onto the Scan Results controlling document
If a Domino server document had a carriage return in the “Server Name” field, the DLAU would display an empty Domino server name in the “Observations” list
UPDATES INCLUDED IN V1.0.10
The DLAU can now differentiate between Complete Collaboration for Business (CCB) and Complete Collaboration for External Users (CCX). New values are now displayed on the “Scan Results” page with a breakdown of each license type
the “Previous Results” page has been updated to reflect the new CCB & CCX calculations
A sporadic hang and eventual shut down of the HCL Notes client was occurring during the question dialog about External Users. The display of the dialog has been moved to later in the logic to stop the Notes Client issues
An incorrect message was being displayed on the Printable Report page which indicated that an LDAP directory was in use when no LDAP Directories are configured
The “User Information Export” was not working when a subset of the User data was selected for export
On the “Observations” details page, there were labels showing for a programmatic tabbed table in the UI when they should be non-visible
When viewing the Printable Report, when the user is asked for their “Client Information” the functionality would allow the user to progress without entering their information. This has changed to enforce the entry of the information prior to seeing the printable report
There was a sporadic failure in completing the Scan Wizard in very specific situations if the User Report Tool Output was not indicated for older Domino environments
UPDATES INCLUDED IN V1.0.9
Numerous minor UI/UX changes, including better UI spacing to fit smaller resolution screens and a new application icon which uses the resources available in teh “HCL Domino Design Guide”
The version numbering system that is now being used adheres to the Versioning infomration found on the main page of this site
If the HCL Domino servers each have different Directory Assistance Catalogs and/or there are multiple Directory Assistance Configurations which point to the same Domino Directory, but are on separate Domino servers, the DLAU was scanning those Domino Directories miultiple times. A correction to the scan has beendesinged to ensure that only one instance of a Domino Directory is added to the scanning list
UPDATES INCLUDED IN V1.0.0h
This version now indicates the number of Domino Mail Users that are configured in the Domino directories if they are also an Authorized User
If there are LDAP Directories configured in the Directory Assistance Catalog, a new Observation is captured, and an On-Screen message is displayed to the user stating that the utility currently does not support scanning of LDAP Directories
The original Base64 Script Library has been removed. This is in preparation for the utility to be placed into an Open-Source Repository and to follow our rules for the Apache 2.0 License
When scanning the HTTP and LDAP Port Settings on the Domino server documents, we now also check to see if the HTTP / LDAP port is enabled. If it is not enabled, then we ignore the additional check to see if those ports have the option “Enforce server access settings” enabled
In HCL Notes Client (64Bit version only) the NotesTimer event would crash the HCL Notes Client if it was triggered while a Dialogbox was being displayed on the user’s screen
UPDATES INCLUDED IN V1.0.0g
An issue was introduced in the new Re-signing functionality that would present an error after the design was resigned
UPDATES INCLUDED IN V1.0.0f
On the initial page that is presented with instructions for re-signing the design, there is now functionality to re-sign the design even if the user does not have access to a Domino Designer or Domino Administrator client
UI/UX - some of the wording for the Information Popup Messages to better clarify what each set of information is presenting to the user
A regression issue was introduced that ignored an open environment if an HCL Domino server did not have secured HTTP and / or LDAP ports
UPDATES INCLUDED IN V1.0.0e
UI/UX - the categorization of the “User Information” view has been changed to better display users who have access to all Domino servers and users who can only see a subset of the Domino servers
if an organization utilizes the “Alternative Name” field on the Person documents, those Person documents would be captured in DLAU multiple times
UPDATES INCLUDED IN V1.0.0d
If an organization has a large number of Groups in their Domino Directory (more than 65,536 Groups), the Deny Access Scan would fail. the logic for listing all Group Names has been adjusted to now accommodate up to 1,000,000 Groups in a single Domino Directory
UPDATES INCLUDED IN V1.0.0c
the User Information documents now capture if the User is a Notes Mail user. This data is not displayed at this time, but will be used in a near future release that will assist in calculating Notes Mail versus Notes Application users for proper Domino Server licensing purposes (e.g., Utility Server versus Mail Server versus Enterprise Server)
If there is a User that is identified as having access to some, but not all, Domino servers, they are now identified as an “Authorized User - Partial Deny Access”. They will now be in a different category in the “User Information” View and still count towards the “Authorized User” count
On the User Information documents, when the document is opened there is now a new area titled “Server Accessibility” that lists all available Domino servers, the Domino servers that the user can access, and the Domino servers that they CANNOT access based on the Deny Access Group scans that are performed
changed how the License Tracking System is identified as “running” - previously it looked for License Tracking results per available server. Now, the scan will look at the settings in the Domino Directory to see if License Tracking is enabled for each available server. this was changed for environments that have License Tracking enabled for a Domino server but there are no results for the Domino server available
In some environments that have a large number of Observations, the Log document within DLAU that lists all Observations was encountering a data limit (32kb) of values. This has been corrected to allow much more data to be stored on the Log document
If the client’s Domino servers had a mix of different Deny Access names listed on the Security tab of the Server documents (e.g., Sever A has 2 Groups listed, Server B has 1 Group listed, Server C has 3 Groups listed) the Deny Access User calculation was not occurring correctly
The list of Domino Servers that are using a specific Deny Access Group was not fully listed on the Deny Access Group document within the utility