Richard Pajerski

Happy Easter

Richard Pajerski — Sun, 5 Apr 2026 00:00:00 -0400

And while they were on their way, all at once Jesus met them and said, All hail. With that, they came near to him, and clung to his feet, and worshipped him. Then Jesus said to them, Do not be afraid; go and give word to my brethren to remove into Galilee; they shall see me there. (St. Matthew 28: 9-10; Knox Version).

Apparition de Jésus aux saintes femmes (Jesus appears to the Holy Women), James Tissot (Public domain)

Notes/Domino 14.5.1 General Availability

Richard Pajerski — Thu, 19 Mar 2026 14:29:03 -0400

Download:

Notes and Domino 14.5.1 are now available on the My HCLSoftware portal.

Release Notes:

https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0129261

Developer Documentation:

https://help.hcl-software.com/dom_designer/14.5.1/index.html

Administrator Documentation:

https://help.hcl-software.com/domino/14.5.1/admin/index.html

Merry Christmas

Richard Pajerski — Thu, 25 Dec 2025 00:00:00 -0500

Ecce virgo in utero habebit, et pariet filium: et vocabunt nomen ejus Emmanuel, quod est interpretatum Nobiscum Deus.
(Matthew 1:23; Latin Vulgate).

Image (public domain): Birth of Christ by Ernst Deger

Happy Easter

Richard Pajerski — Sun, 20 Apr 2025 00:00:00 -0400

Then Jesus said, Do not cling to me thus; I have not yet gone up to my Father's side. Return to my brethren, and tell them this; I am going up to him who is my Father and your Father, who is my God and your God. (St. John 20: 17; Knox Version).

Noli me tangere (Touch me not), James Tissot (Public domain)

Merry Christmas

Richard Pajerski — Wed, 25 Dec 2024 00:00:00 -0500

Et Verbum caro factum est, et habitavit in nobis: et vidimus gloriam ejus, gloriam quasi unigeniti a Patre, plenum gratiæ et veritatis. (St. John 1: 14).

Image (public domain): La nativité de Notre-Seigneur Jésus-Christ, James Tissot

LS2J as an applet replacement

Richard Pajerski — Thu, 30 May 2024 22:50:45 -0400

I'm currently reviewing LS2J as an alternative for replacing a number of custom Notes applets I've deployed over the years. The applets have been very reliable and effective in areas where Notes is typically not that strong such as displaying and editing tabular data. But with applets' deprecation in Java and their "broken" status in Notes 64-bit versions, I need a viable transition to something that can preserve the existing functionality/investment as much as possible.

Although I don't see any obvious way to embed top-level Java windows (JFrame, JDialog) in the same manner as applets (which can be placed on a form like most other widgets), with LS2J I've found I can call them from behind a simple button and in the case of JDialog, even block the Notes client without breaking things too badly. I can also call a JFrame from LS2J but the window can quickly lose focus -- in the same way it does when called from a Java agent. I believe this is due to it being launched on a separate thread.

Below is a contrived example with JDialog but so far so good; I'm able to replace a form-based applet with a simple button that calls a JDialog, blocks for user input and then transfers the text back to Notes:

This is actually simpler than applets which require Javascript when transferring to/from Notes UI documents (not pleasant).

Our button code (Options):

Click function:

And our associated Script Library:

The JDialog class is a bit more involved but not important in the context of this post. The important part consists of returning the contents of a JTextArea when "OK" is clicked:

public String getFieldData() { return jTextArea1.getText(); }

And that's it!

Notes/Domino 14 FP1

Richard Pajerski — Tue, 16 Apr 2024 17:17:37 -0400

Fixpack 1 for both Notes 14 client and Domino 14 server are now available: https://my.hcltechsw.com/downloads

Release notes: https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0112431

Happy Easter

Richard Pajerski — Sun, 31 Mar 2024 00:00:00 -0400

And they went into the tomb, and saw there, on the right, a young man seated, wearing a white robe; and they were dismayed. But he said to them, No need to be dismayed; you have come to look for Jesus of Nazareth, who was crucified; he has risen again, he is not here. Here is the place where they laid him. (St. Mark 16: 5-6; Knox Version).

Resurrection of Christ, Fra Angelico (Public domain)

Merry Christmas

Richard Pajerski — Mon, 25 Dec 2023 00:00:00 -0500

The time is accomplished, and the kingdom of God is at hand: repent, and believe the gospel. (St. Mark 1:15; Douay-Rheims version).

Image (public domain): The Nativity with the Prophets Isaiah and Ezekiel, Duccio di Buoninsegna. Courtesy National Gallery of Art, Washington.

Three easy-to-use Java 17 features in Notes/Domino 14

Richard Pajerski — Tue, 19 Dec 2023 15:14:01 -0500

As I mentioned previously, having Java 17 available with the latest release of Notes/Domino has brought welcome changes for Java developers. Just to scratch the surface a bit, here are three language-level niceties that we can immediately benefit from:

1. Simplified access to file contents
2. Local-variable type inference (var identifier)
3. Text blocks

1. Simplified access to file contents
Java has been (in)famous for offering a number of ways to open/read and write/close files. As of Java 11, perhaps the simplest way to get text out of a file is:

Files.readString(Path p);

A two-liner in a local Java agent on a Windows 11 client:

import java.nio.file.Files;
import java.nio.file.Path;
import java.nio.file.Paths;

import lotus.domino.*;

public class JavaAgent extends AgentBase {

    public void NotesMain() {

      try {
          Path p = Paths.get("C:\\Windows\\System32\\drivers\\etc\\hosts");
          System.out.println(Files.readString(p));
      } catch(Exception e) {
          e.printStackTrace();
      }
   }
}

Javadoc: https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/nio/file/Files.html#readString(java.nio.file.Path)

2. Local-variable type inference (var identifier)

The var type identifier has been available since Java 10 and is intended to help reduce "boilerplate" code:

import lotus.domino.*;

public class JavaAgent extends AgentBase {

    public void NotesMain() {

      try {
         var s = getSession();
     var db = s.getCurrentDatabase();
         System.out.println("Db title: " + db.getTitle());

            /* Contrast:
               Session s = getSession();
           Database db = s.getCurrentDatabase();
             */
      } catch(Exception e) {
          e.printStackTrace();
      }
   }
}

More: Using the Var Type Identifier

3. Text blocks
In Java 15, Text Blocks were introduced. In a more developed application, it's probably a better idea to store strings and text outside of source code, especially if they need to be regularly modified. But using text blocks can be a time saver for quick testing, demos, etc. and provide improved source readability.

import lotus.domino.*;

public class JavaAgent extends AgentBase {

    public void NotesMain() {

      try {
         var textBlock = """

Using text blocks in Java source

code simplifies text formatting

and improves readability!

""";

System.out.println(textBlock);

      } catch(Exception e) {
          e.printStackTrace();
      }
   }
}

Note: To use these features, remember to adjust your compiler levels appropriately:

New context-specific Notes 14 client preferences options -- nice touch!

Richard Pajerski — Thu, 7 Dec 2023 13:13:08 -0500

Notes 14 is now GA and an improved listing of the Notes "Additional options" (File > Preferences > Basic Notes Client Configuration) is an unexpected but very welcome feature!

Previously, all options were in one long list and so the context where each one applied was not always clear. Now a categorical description precedes each option entry:

Nice touch, HCL and thank you!

Domino/Notes 14 and Java in the client

Richard Pajerski — Wed, 26 Jul 2023 13:25:52 -0400

Those who have been programming with Java in Notes/Domino over the years will be pleased to learn of the move from Java 8.x to Java 17 which is planned for the next release of ND 14 at the end of the year. The version gap is rather stark and indeed a lot has changed. One nice summary of the changes between the two version can be found at The Java Almanac here: https://javaalmanac.io/jdk/17/apidiff/8/.

I've yet to explore the impact to the ND world in any detail but will try to cover that in some future posts. A particular area of interest for me that's still "unresolved" is how HCL intends to treat Java applets. Here I mean applets embedded in Notes client applications, not for use in web browsers. Applets were deprecated for removal in Java 17 and of course have long been out of use in web browsers. But will HCL continue to support their use in the Notes client and if so, for how long?

Happy Easter

Richard Pajerski — Sun, 9 Apr 2023 00:00:00 -0400

And suddenly there was a great trembling of the earth, because an angel of the Lord came to the place, descending from heaven, and rolled away the stone and sat over it; his face shone like lightning, and his garments were white as snow; so that the guards trembled for fear of him, and were like dead men. (Saint Luke 28:2-4 Knox Version).

Image (public domain): Resurrection of Christ by Noël Coypel

DOTS follow-up, SPR for applet bug

Richard Pajerski — Wed, 15 Feb 2023 10:27:45 -0500

Following up on my NSFDBHOOK post in December, I'm told the official word from HCL Product Management is that "HOOK and Event Management (EM) should be discontinued, as those have not been well used and tested functionality ..." I can appreciate that it's hard to justify development if there isn't much traction, but having an easily accessible Java API for these low-level Domino events (without having to write my own DSAPI plugin) would've been a really handy feature for some of my custom applications. There's always the Domino Ideas Portal for the future!

Regarding Java applets not loading in Notes, HCL is now tracking a fix under SPR #CECNCNPSCQ.

[February 28, 2023 update] Defect article for applets can be found here: https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0102913

Securing access to MongoDB with Sametime 12 Premium

Richard Pajerski — Tue, 14 Feb 2023 22:58:54 -0500

Setting up a new, fully functional stand-alone Sametime 12.0.1 Premium server on Docker instance is a relatively pleasant experience and HCL has made great strides is presenting a more simplified, compelling UX for the product than what was previously offered. For example, the new interface for creating and customizing meetings gets all the important, relevant bits into a single page (a good introduction to the product can be found here).

But the thrust of this post is on securing the server itself, and more specifically the MongoDB portion where chat histories, contact lists and other details are stored. HCL supports MongoDB versions 4.2 and higher on a best effort basis and I'm using version 6.0.4 on CentOS 8 for purposes of this post. Here's what worked for me.

After installing, we configure our Sametime database using the MongoDB Shell; upon first connecting, there's no prompt for a password and we're plainly told:

"Access control is not enabled for the database. Read and write access to data and configuration is unrestricted"

Well, that's not good. It was now possible to connect using mongosh and fully control the server *from anywhere, without a password*...

According to the installation guide, port 27017 should be "permitted bidirectionally". That's understandable since a common strategy is to deploy the MongoDB server on its own host. But even with this installation which has both the MongoDB server and Sametime on the same machine, closing off external access to 27017 caused internal connectivity problems for Sametime (I could no longer create meetings and chat histories were no longer available).

So next I turned to this document on securing MongoDB. That method might work for other versions of MongoDB but it didn't work with 6.0.4 (the MongoDB server refused to start). What I found is that "keyFile" authorization is needed for this version of MongoDB when replica sets are used (which is the default for Sametime).

Create the keyfile:

openssl rand -base64 812 > /opt/st12/mongosec.key

Be sure to also run these two commands on the keyfile or Mongo won't start:

chmod 400 /opt/st12/mongosec.key
chown mongod:mongod /opt/st12/mongosec.key

Edit /etc/mongod.conf to tell MongoDB where the file is and enable authorization:

security:
keyFile: /opt/st12/mongosec.key
authorization: enabled

We also need to launch the MongoDB server with "--auth". I've installed MongoDB as a service so that means editing /etc/systemd/system/multi-user.target.wants/mongod.service:

[Service]
Environment="OPTIONS=-f /etc/mongod.conf --auth"

After restarting the MongoDB service (systemctl restart mongod), I can still connect with mongosh but the warnings are gone; if I attempt to run commands, I'm told authentication is required:

To connect with a username:

mongosh mongodb://127.0.0.1:27017 -u sametimeUser

Finally, don't forget to change the default user/pass combination (sametimeUser/sametime) before going live!

Merry Christmas

Richard Pajerski — Sun, 25 Dec 2022 00:00:00 -0500

And she shall bring forth a son: and thou shalt call his name JESUS. For he shall save his people from their sins. (St. Matthew 1:21; Douay-Rheims version).

Image (public domain): The Nativity by Lorenzo Lotto (1523)

Possible bug with triggered NSFDBHOOK events in DOTS (on Windows 2019)

Richard Pajerski — Fri, 23 Dec 2022 13:13:26 -0500

[February 2023 update: DOTS follow-up, SPR for applet bug]

I recently took advantage of DOTS being back in the Domino 12 server, to replace a Java agent with a scheduled DOTS tasklet and have been pleased with the results. Using tasklets is generally going to be far more efficient than using Java agents in Domino since a JVM is loaded once with the DOTS server task and remains resident in memory until the DOTS task is stopped whereas with each agent invocation a new instance of the JVM is started. There are other benefits to using tasklets over Java agents which I may take up in a future post but for the moment, I've run across an issue on a Windows 2019 server installation.

Although the deployment above uses a scheduled tasklet, I was originally hoping to use the triggered NSFDBHOOK events in order to capture some document saves in (more/less) real time. But while testing on Windows 2019, I noticed that the HOOK_EVENT_NOTE_UPDATE and HOOK_EVENT_NOTE_OPEN events were not being emitted at all or only very infrequently. I had earlier tested the same tasklet on a Domino installation on a Windows 8.1 client and the events fired more/less as expected. Aside from the OS difference, everything about the Domino installations was identical -- with one exception: the Domino program installation directory on the Windows client had no spaces but the Windows server was installed in the default C:\Program<space>Files\HCL directory. Sure enough, after reinstalling Domino on the Windows 2019 server without the space (specifically in C:\Domino), events began firing again. HCL has also reproduced this and may open an SPR.

In the meantime, after working a bit more with those NSF hook events, my impression is that they are not altogether reliable -- or at least, there doesn't appear to be a one-to-one correlation with each document save/open and a DOTS-generated event. Some document saves/opens never fire an event. The source code for the older versions of DOTS is on openntf.org here: https://stash.openntf.org/projects/DOTS/repos/dots/browse/sources but I'm not sure if this is the same code being shipped with the Domino 12 server (though I assume it's pretty close).

If I'm looking in the right place, lines 79 and 80 of the postMessage method (https://stash.openntf.org/projects/DOTS/repos/dots/browse/sources/dotsNSFHook.cpp), have:

STATUS error = MQOpen(queueName, 0, &dotsmq); if ( error == NOERROR ){

where DOTS presumably intercepts the necessary events from an internal Domino queue. But what if there *are* errors here? Will our DOTS tasklets ever know about them? Maybe errors are unlikely here but perhaps this is the source of some missed events.

Java applets in Notes 64-bit client not loading

Richard Pajerski — Wed, 21 Dec 2022 19:17:53 -0500

[February 2023 update: DOTS follow-up, SPR for applet bug]

For the first time in the history of Notes, HCL last month released a fully supported 64-bit version of the Notes standard, Domino Designer and Domino Administrator clients with release 12.0.2. Overall I've found it to be more stable and certainly faster than its 32-bit counterpart and so I now use it regularly. However, it's not without its issues with reports popping up here and here. And I have another to add: Java applets won't load in the 12.0.2 64-bit client. I submitted a ticket to HCL and they could reproduce this so they're preparing an SPR.

A notable aspect of this bug is that there are no error logs (that I could find) to indicate something's wrong. Nothing in the Java Debug console, the IBM_TECHNICAL_SUPPORT folder, log.nsf, etc. You will see the Java coffee cup but I think most end users will not immediately interpret it as a problem:

This issue is probably not an inconvenience for most deployments since Java applets were never widely implemented in Notes (in my experience). But where applets are used, they can bring quite a bit of power (e.g. custom interfaces for any third-party system with a Java API -- databases, message queues and so on). The good news is that applets do still work in 32-bit Notes 12.0.2 and will likely be supported in Notes as long as Java 8 remains the default runtime.

Traveler 12 expired APNS certificates

Richard Pajerski — Wed, 21 Dec 2022 15:07:09 -0500

It looks like the expiration date for APNS p12 certificates that shipped with Traveler 12.0.1 was on or about December 19, 2022. If you have a Traveler 12.0.1 (November 2021) installation and started seeing Domino console messages similar to:

[1034:0002-1038] 12/21/2022 01:38:08 PM  Traveler: SEVERE <User> Unable to get the PushNotificationResponse for apnsId null Exception Thrown...

on or after that date, the resolution is to apply Traveler 12.0.1 Fix Pack 2 which includes new APNS p12 certificates that expire in September 2023. Until that fixpack gets applied (or you upgrade to Traveler 12.0.2 which also contains updated certificates), iOS users will no longer receive notifications of new email on their devices.

More here: What's new in Traveler 12.0.1 Fix Pack 2?

Happy Easter

Richard Pajerski — Sun, 17 Apr 2022 00:00:00 -0400

And then, when he sat down at table with them, he took bread, and blessed, and broke it, and offered it to them; whereupon their eyes were opened, and they recognized him. (St. Luke 24:30; Knox Version).

Image (public domain): Supper at Emmaus by Matthias Stom

Merry Christmas

Richard Pajerski — Sat, 25 Dec 2021 00:00:00 -0500

This is the sign by which you are to know him; you will find a child still in swaddling-clothes, lying in a manger.
(Luke 2:12; Knox Version).

Image (public domain): L'Adoration des Bergers by Georges de La Tour

Brief overview of modern (2021) server-side development landscape in Domino

Richard Pajerski — Thu, 7 Oct 2021 20:21:02 -0400

Among the technical reasons Domino has enjoyed longevity in the application server market are its stability and reliability. But of course technology changes rapidly and being able to successfully adapt to new trends has also kept Domino relevant over the years. Striking a balance between trendy and relevant is not always obvious but the stewards of Domino have generally taken a conservative approach to introducing and supporting new technology which continues to benefit the product in the immediate and long term.

Very briefly then, beyond the tried-and-true world of Notes client server application development, let's look at three modern technology options developers can choose from in 2021:

1. Domino AppDev Pack (https://doc.cwpcollaboration.com/appdevpack/docs/en/homepage.html)

From the site: "The AppDev Pack primarily adds Node.js support to HCL Domino Server."

So developers already familiar with or wanting to explore the JavaScript-centric Node.js have a custom-designed set of tools for programmatically and securely accessing Domino applications and data.

2. Domino REST API (Project Keep) (https://opensource.hcltechsw.com/domino-keep-docs/)

From the site: "Domino REST API is designed to re-establish Domino as a world class, modern, standards-compliant, cloud native and enterprise-level collaboration platform. It adds contemporary REST APIs to Notes and Domino, enabling a modern programming experience with the tools of your choice."

This is still in beta but will hopefully be out in Domino 12.0.1 later this fall. Domino has for many years had the ability to offer data via a REST API (Domino Access Services) but Keep modernizes that effort by implementing (among other things) OpenAPI and JWT Authorization. In addition, developers will be able to introduce their own server-side modules called "verticles" as Keep runs on top of Vert.x.

3. Tasklets with DOTS - Domino OSGi Tasklet Service (https://help.hcltechsw.com/domino/12.0.0/admin/wn_dotsredux.html)

From the documentation: "DOTS is a generic Domino add-in task that lets users create Domino server tasks by creating a tasklet container using Java OSGi plugins."

Ok, this is not exactly modern -- DOTS was an OpenNTF project that's been available since Domino 8.5.3. Although officially dropped in the Domino 10/11 era it was recently updated and re-introduced in Domino 12.

Strictly-speaking, DOTS is the Domino server task that manages the tasklets which are Java server-side plugins. Tasklets use a standard mechanism for starting/stopping (OSGi-defined) which makes them similar to Java agents but have the additional benefits of (a) not being tied to a specific .nsf file, (b) not requiring a full JVM reload on every execution and (c) better access to the Domino C API.

How are you developing Domino server-side code these days?

Notes client pegs one logical processor at 15%

Richard Pajerski — Fri, 18 Jun 2021 15:38:15 -0400

Having recently installed a Notes/Designer/Admin 12 client on Windows 8.1 Pro on an aging Intel i7 Quad-Core (with eight logical processors), I was surprised to see that after startup, Notes was consistently grabbing one logical processor and pegging it at around 15%. Windows Task Manager showed that nlnotes.exe was the process and it wouldn't let go of that processor until Notes was closed:

Notes, Designer and Admin clients all worked fine and interaction with local- and server-based applications was normal. Without giving it too much thought, I tried a few things like removing cache.ndk, stopping a couple Notes-related services and making sure the preference "Enable scheduled local agents" was disabled.

But none of that worked and strangely, Disk and Network utilization were both at 0%:

The client was set up in the normal way by connecting to a Domino server with an existing mail file on the server. However, this workstation needed to use a Location that sends and receives mail from a POP3 server instead of Domino. For that purpose I used an existing names.nsf that already had Account and Locations documents in place. All of that connectivity worked and the mail flowed normally.

The next step was internet search but nothing obvious jumped out and most references to similar problems ended with Notes client crashes which I was not experiencing.

The Location document for this POP3 configuration kicks off replication and runs it every 10 minutes. I noticed that after starting the client, there was a gap of a few seconds where the nlnotes.exe process was at 0% and didn't go up to 15% until replication started (and then stayed there). Thinking the culprit was the Replicator, I disabled replication and restarted Notes... but nlnotes.exe was back to 15%!

But this time I could clearly see that process spiked when "Notes configuration settings have been refreshed" scrolled across the Status bar:

Based on that message and the fact that a POP3 configuration like this is not commonly used, I kept pursuing the Location document as the source of the problem. And the problem was indeed there.

When you configure the Notes client for POP3 mail retrieval, only the "Mail" tab of the Location document needs to be filled out:

The "Servers" tab can remain empty -- and that was the problem! At a minimum, the "Home/mail server" field MUST have some value in it to calm down the processor:

It doesn't matter if the server is down or the value entered isn't even a Domino server -- nlnotes.exe will report that the server is not responding but it leaves the processor alone after that:

Ok, problem solved, back to work.

Happy Easter

Richard Pajerski — Sun, 4 Apr 2021 00:00:00 -0400

Early in the morning on the first day of the week, while it was still dark, Mary Magdalen went to the tomb, and found the stone moved away from the tomb door. (St. John 20:1; Knox Version).

Image (public domain): The Resurrection by Carl Heinrich Bloch

Congratulations Ray Ozzie - 2021 Computer History Museum Fellow Award

Richard Pajerski — Sat, 20 Mar 2021 23:16:00 -0400

Ray Ozzie is among the 2021 Computer History Awards honorees recognized "For a lifetime of work in collaborative software and software entrepreneurship".

https://computerhistory.org/press-releases/chm-honors-tech-legends-for-lifetime-of-contributions-and-impact-on-humanity/

A virtual event took place to honor Ray on March 18, 2021 and will be generally available in the coming days. Thank you, Mr. Ozzie for your contribution to computer history!

One additional little feature...

Richard Pajerski — Fri, 12 Mar 2021 12:43:20 -0500

In an effort to cover some specific cases, a minor feature was just added to CertMatica (3.6.0) to automate copying LE certificates to additional locations on the server's file system.

The idea is to allow Domino to share the LE certificate with one or more services running on the same machine (such as a reverse proxy like Nginx or an alternate SMTP service) without further manual intervention.

CertMatica 3.6.0

CertMatica 3.6.0 Trial

CertMatica 3.5.1 - important note for Domino 9.x and 10.x servers

Richard Pajerski — Fri, 5 Mar 2021 20:53:21 -0500

First of all, a big "Thank you!" to all CertMatica customers!

Just out this week, CertMatica 3.5.1 is a maintenance release with simplified switching between Let's Encrypt test and production modes and minor improvements to logging and documentation. However, for those running on earlier versions of Domino 9.x and 10.x servers, this release also includes an important update to the CertMatica Cacerts Utility which can be used to address potential connectivity errors caused by missing or expired intermediate certificates in the Domino JVM truststore (cacerts). For information on Let's Encrypt infrastructure changes related to this update see https://letsencrypt.org/2019/04/15/transitioning-to-isrg-root.html.

As always, feedback and commentary is always greatly appreciated!

Notes/Domino 12.0 Beta 1

Richard Pajerski — Thu, 21 Jan 2021 13:37:28 -0500

Start Your Engines! HCL Domino v12 Beta is Here! Are You Ready?

FlexNet download: https://hclsoftware.flexnetoperations.com/flexnet/operationsportal/logon.do

Merry Christmas

Richard Pajerski — Fri, 25 Dec 2020 00:00:00 -0500

Image (public domain): Nativity of Jesus by El Greco.

CertMatica now includes Let's Encrypt certificate automation for HCL Sametime 11 Proxy Server

Richard Pajerski — Mon, 28 Sep 2020 00:05:00 -0400

In addition to Domino, CertMatica now includes the ability to install and renew Let's Encrypt certificates for Sametime 11 Proxy servers. Using the simplicity (and power) of a single .nsf solution, CertMatica can help to centralize administration for LE certificates across both server types and seamlessly manage service restarts. No extra dependencies needed.

For more information, please visit the CertMatica 3.5.0 product page.

As always, comments and suggestions are welcome!