If you are using DOTS in Domino 12.x, you might have seen some NullPointer Exceptions after you have updated a DOTS plugin. Recommendation was to delete the complete workspace-dots folder prior to starting DOTS after the upgrade.
This issue has been addressed in SPR#SJAAC3BNWV: DOTS – Workspace need to be deleted on every change and add of new plugin.
With this fix it is no longer necessary to delete the workspace-dots folder. Not sure, when the fix was provided. There is no information about it in the fixlist database.
But this is only true for Domino on WINDOWS. If you are using DOTS with Domino on LINUX, you will see an error on the Domino server console ( “An error occurred while processing the command”) or even worse, the NullPointer Exceptions.
The problem is that the underlying API in Domino does not delete files starting with a dot. (hidden files on UNIX systems).
There is a HF67 available for Domino 12.0.1 FP1 that fixes this issue. SPR#DNADCHM8VJ: Deleting directory fails on Linux/UNIX when directory contains files starting with dot (UNIX hidden file).
The fix has already found it’s way into Domino 12.0.2 (Danube).
If you need the fix, open a case with HCL support.
Active Directory Password Sync applies the Windows passwords of users registered in an Active Directory domain to their Domino HTTP and/or Notes ID passwords.
Password synchronization is supported for
Registered HCL Notes, HCL Nomad, HCL Verse, and HCL iNotes users accessing Domino servers with HTTP passwords or Notes IDs.
HCL Traveler users accessing their mail through the web browser on their mobile devices.
Web users who are not registered in Domino but who have Person documents in the Domino directory accessing Domino web applications with HTTP passwords.
To setup and configure Active Directory Password Sync, you need at least 2 Domino v12 servers. One server acts as Request Creator and the other one has the role Request Processor.
On the “Active Directory Password Sync” tab of the configuration document for each of the servers you can configure which password changes should be processed. The refresh interval specifes the amount of times in minutes after a request is created to allow the request to be processed.
To sync passwords to Notes IDs, the Request Processor servers require password reset authority to the ID vault. I you miss this configuration step, you’ll see an error message on the console of the Request Processor:
[1DFC:0059-1694] 07.04.2021 10:13:23,00 AD Password Sync> PWSyncProcessStoredRequests: Failed to update password in Notes ID for CN=Herbert Feuerstein/O=singultus: Agent containing ResetUserPassword method must be signed by a designated Password Resetter.
[1DFC:0059-1694] 07.04.2021 10:13:23 Password Sync: Active Directory Password Sync failed for objectGUID 6630b191119c8b45b78b77865a37cc70: Agent containing ResetUserPassword method must be signed by a designated Password Resetter.
Request Creator must be installed on the AD Domain Controller. The install type is “Utility Server”. The server must be configured but will never run as a service.
After you have successfully configured the Request Creator, The installer will remove some of the Domino server executables
[0C14:0002-1284] Deleted Executable File 'C:\Domino\nserver.exe' for security reasons.
[0C14:0002-1284] Deleted Executable File 'C:\Domino\nhttp.exe' for security reasons.
[0C14:0002-1284] Deleted Executable File 'C:\Domino\nldap.exe' for security reasons.
[0C14:0002-1284] Deleted Executable File 'C:\Domino\nsmtp.exe' for security reasons.
[0C14:0002-1284] Deleted Executable File 'C:\Domino\npop3.exe' for security reasons.
[0C14:0002-1284] Deleted Executable File 'C:\Domino\nimap.exe' for security reasons.
The installer finally adds the Domino password library “npwsync.dll” to the Windows registry. The entry can be found here
For security reason, the server id that is used for the Request Creator is encrypted during the installation and configuration process. Make sure that the id does not have a password on it. The secured id cannot be used on any other machine than the Request Creator.
A new application is created on the Request Processor. The application stores the requests that are created by the Request Creator. After a request has been successfully processed, the document is removed from the database.
Most of the items in the document are encrypted.
After you have setup and configured Request Creator and Request Processor, you should restart both machines (OS level).
When a user now updates his / her password, LSA processed the change thru the Domino password library, and a new document is created in the Active Directory Password Sync application. The Request Processor reads new documents from the application and processes them according to its configuration.
Here is an example of what you see on the Request Processor console
Domino V12 Early Access CodeDrop 3 comes with a couple of new Java/LotusScript transaction methods that have been added to the (Notes)Database class. At the moment, there is no Domino Designer V12 available. So how can we test the new methods?
If you are familiar with Java, then this is possible, because Java development not neccessarily needs Domino Designer.
All we need is the Notes.jar file from the V12 Domino Docker container.
Now that you have access to the Domino V12 program directory, copy the Notes.jar file located in /opt/hcl/domino/notes/latest/linux/ndext to your development environment.
In the BuildPath change the location of Notes12.jar to the location of Notes.jar in your environment.
To build the project, change to the bin directory inside the project and issue the command
jar cfe D12Test.jar Domino12Test de
Copy the resulting .Jar file to the ndext folder in the Domino V12 program directory. Make sure to set the correct execution rights ( 755 ). Now you can start the addin with
lo runjava de.eknori.Domino12Test
After the addin has started you will see the following on the Domino console
11/01/2020 05:45:15 Domino12Test: version 2 11/01/2020 05:45:15 Domino12Test: build date 2020-10-22 11:00 CET 11/01/2020 05:45:15 Domino12Test: java 1.8 11/01/2020 05:45:15 Domino12Test: seconds elapsed 30
During the next scheduled addin run, the code will create a new document in the d12test.nsf. You need to create this database on your server before running the addin. The database does not need to contain any design elements.
When the addin ran, you should see new documents in the database created with a form “commit”.
You should NOT see any documents that have a “rollback” form.
The same way, you can also test the new DQL enhancements in V12 Early Access Code Drop 3.
The October code drop of Domino 12 ( Early Access Program) introduces TOTP as a new security feature.
A time-based one-time password (TOTP) is a temporary passcode generated by an algorithm that uses the current time of day as one of its authentication factors. Time-based one-time passwords are commonly used for two-factor authentication. In two-factor authentication scenarios, a user must enter a traditional, static password as well as a time-based one-time password to gain access to the computing system.
To configure TOTP, please follow the instructions in the documentation
TOTP uses the IDVault. It is important that the server running Domino 12 is the primary server for the IDVault by now. Development is still work in progress and you will run into issues with TOTP when you’re Domino 12 running together with Domino 11 like I do.
The IDVault in Domino 12 comes with an updated design to show information about TOTP.
After you have configured your server for TOTP, you will see a new login dialog when you access an application on the Domino 12 server that needs authentication.
If you acces the server for the first time and TOTP is not yet set up for your user, you need to setup a TOTP authentication device.
There are a couple of applications available. I am using TOTP Authenticator on an iPhone . I also tested with Authy
You’re not participating in the program yet? Read more about the HCL Domino 12 Early Access Program here.
