Finally you got rid of user management in your application since your organisation has standardized on an IdP. There are plenty to choose from. I usually develop using a Keycloak IdP before I test it with the target IdP (and yes: Azure Entrada tries to be different).

So it's time to adjust your SPA to use the IdP. The admins tell you, you need to use PKCE, part of the OIDC specification

Where is the fun in ready made?

A quick search on npmjs shows, the topic is popular and AWS takes the crown. But for deeper understanding, let's roll our own.

Prerequisites

There are just four items you need. The first three are provided by your IdP admins, the forth one you have to provide to them.

• The URL of your IdP, the full path where .well-known can be found. That's usually the root, but does differ for Entrada or Keycloak
• The issuer. That typically is the URL, except for Entrada
• The clientId. A String, usually opaque
• The callback urls. Pick those wisely. Typically you want three: http://localhost:3000/myApp, https://localhost:8443/myApp and https://final.place.com/myApp The first two enable you to test your application locally with both http and https

It is sitting on my desk, a shiny M4 MacBook. It wants to be configured. I can take the easy route and use the Migration Assistant. But that would carry forward all the cruft the various incarnations of the Migration Assistant have accumulated over the decade. So I went the hard way.

Manual with a dash of AppStore

First Stop: update macOS. In my case Sequoia 15.1 -> 15.6.1

Installation falls into 3 categories

• command line tooling
• settings & data
• GUI applications

Followed by the reconfiguration of license keys

Depending on how deep you authenticate, you might be tasked maintaining a user base in _users (and welcome to "I forgot my password" hell). The standing recommendation is to implement a single source of identity using a directory as Identity Provider (IdP). My favorite NoSQL database can be configured to trust JWT signed by known IdPs, so let's do that.

Some assembly required

CouchDB can be configured in three ways: Edit the respective ini file, use the Fauxton UI or use the REST API. I like the later since I'm comfortable with curl and Bruno (not a fan of Postman anymore). The steps are:

• configure a client on your identity provider
• enable JWT authentication
• specify what claims are mandatory
• specify how to map roles
• add trustedd public keys
• restart your node

I'm a big fan of a strict Content Security Policy (CSP). It can be a pain to setup (but there is help, here, here, here and here) and evaluate.

Let's report it

You won't know if a policy was tried to be violated unless the attempt is reported back to your application. For that purpose we use the CSP directives report-to and the older, deprecated report-uri. Until Firefox catches up, use both. When a browser supports report-to, report-uri gets ignored.

Reporting isn't only useful in production, but already during development and especially during retrofitting. There you can swap the Content-Security-Policy header for Content-Security-Policy-Report-Only. It will allow all content to load, but report back all violations.

You then run your E2E Tests (You have those, haven't you?) and get a free overview what loads from where. Adjust the CSP, rinse and repeat.

Where to report to?

There are numerous SaaS providers with fancy dashboards, that offer ready made solutions. When you are pressed for time, that might be your best option. I haven't evaluated them, so I can't recommend or endorse them.

"We need to use [insert-framework-of-the-day]!" is the typical answer when asking for a light web single page application (SPA).

It doesn't need to be that way, Paul and myself shared in a recent webinar.

Serving the long tail

Long Tail Apps tend to be outside of IT control, since they bypass the (usually heavy) standup of an IT development project.

That standup could be way lighter, when your application just consists of one html file, one css file, one js file, one manifest and (optionally) one or more image files as well as a definded point of deployment.

The typical objection goes: "But it is never one HTML file, I need a login, a list and a form in read and edit mode"

template to the rescue

The <template> element is part of the WebComponents specification and it is useful in simple SPA applications.

AI Chatbots are a popular topic. As part of a session at Engage 2025 I was looking for an easy to grasp example to understand the difference of user prompt and system prompt, the later typically invisible to the user. My goal was to make it abundantly clear how important the system prompt is.

I settled sending the same user prompt with vastly different system prompts. Here is what I got.

Romeo at the balcony

Mercutio’s mocking my love and he’s never been in love himself.

Wait. What’s that light coming from the window over there? It’s like the east, with Juliet as the morning sun! Rise, Juliet, beautiful sun, and kill the jealous moon who’s already fading and sad because you are far more beautiful than she is. Don’t swear off men like the virgin moon goddess Diana—the moon envies you anyway. Her virginal appearance is weak and pale and only fools want to emulate it. Get rid of it.

It’s my lady! Oh, it’s my love. Oh, if only she knew I love her. She’s talking but I can’t hear anything. What does it matter?

Her expression means something and I can answer that. No, I’m being too forward. She’s not talking to me. Oh, if two of the most beautiful stars had to leave heaven on important business, they’d ask her eyes to do the twinkling for them while they were gone! What if her eyes took their places in the sky and those stars became her eyes? Her beautiful face would outshine those stars in her head like daylight outshines lamps, while her eyes in the sky would be so bright at nighttime that birds would be convinced it was day. Look at how she leans her cheek on her hand. I wish I were a glove on her hand so I could touch her cheek!

The Domino REST API not only provides secure access to "jsonified" Domino data,
but also comes with capabilities to ease integration. This enables one to quickly cater to the long tail of applications, giving them a home instead of loosing them to the shadow IT.

Once you know the steps, you can deploy new Single Purpose Applications (I modified the meaning of SPA a little) in no time.

No CORS, no headache

DRAPI allows to host static applications in the keepweb.d directory. "Static" might be a little misnomer (it only relates to the source files, not the interaction) since a JS file can make your experience quite interactive. Since you run on the same Domain and port as the API, you don't need to worry about CORS

Preparation

Your SPA will live in a sub directory of keepweb.d, so think about a name, we shall use demo42 here. Add a suitable icon (e.g. 72x72 px png), name it demo42.png and you are ready to roll. Let's assume our Domino API is running on https://api.demo.io

Work faster with vitejs

viteJS is one of the fronteand tools you want to learn. It features "hot module reload" to speed up development and, when done, packages your application nice and tidy.

It is easy to get started. You need a current version (22.x at time of writing) of nodeJS installed as development tooling.

npm create vite@latest demo42 -- --template vanilla
cd demo42
npm install

This will create the demo42 directory and scaffold the project for you. Before we get started with athe development, let's adjust the environment. In the root of the project create a file vite.config.js

import { defineConfig } from 'vite';

export default defineConfig({
  base: '/keepweb/demo42/',
  server: {
    proxy: {
      '/api': {
        target: 'https://api.demo.io',
        changeOrigin: true
      }
    }
  }
});

This allows you to develop in the comfort of your local machine's hot module reload which refreshes your app on svae automagically. It also fixes the path matching to its final destination. Next create in public the file manifest.json. This file defines the tile layout for the landing page.

{
  "short_name": "Demo 42",
  "name": "The final answer to all Demos",
  "start_url": ".",
  "display": "standalone",
  "theme_color": "#000000",
  "background_color": "#aacccc",
  "icon": "vite.svg"
}

You can play with colors and icons as you deem fit. Now we are ready to run the application:

npm run dev

Mainly as a note to self.

My default firewall setup

sudo ufw status
sudo ufw default allow outgoing
sudo ufw default deny incoming
grep IPV6 /etc/default/ufw
sudo ufw allow ssh
sudo ufw limit ssh/tcp comment 'Rate limit for openssh server'
sudo ufw allow 80/tcp comment 'Allow nginx HTTP'
sudo ufw limit 80 comment 'limit nginx HTTP'
sudo ufw allow 443/tcp comment 'Allow nginx HTTPS'
# For Domino mail
sudo ufw allow 1352/tcp comment 'Allow Notes replication'
sudo ufw allow 25/tcp comment 'Allow SMTP'
sudo ufw allow 587/tcp comment 'Allow SMTP'
sudo ufw allow 110/tcp comment 'Allow POP3'
sudo ufw allow 995/tcp comment 'Allow POP3s'
sudo ufw allow 143/tcp comment 'Allow IMAP'
sudo ufw allow 993/tcp comment 'Allow IMAPs'
sudo ufw allow from 1.2.3.4 'Allow the othe Domino'
sudo ufw enable

Java 14 (in a preview feature) introduced Records. In a nutshell: Records are (mostly) immutable objects with a greatly reduced amount of boilerplate code requirements. For a detailed introduction head over to Baeldung.

When records need update

The short answer: create a new record and use the existing as input. Let's look at an example:

public record Billionaire(String name, Long wealth, Temporal assessment) {

  public Billionaire cloneWithNewAssesment(Long newWealth, Temporal currentAssesment) {
    return new Billionaire(this.name, newWealth,currentAssesment);
  }
}

By itself this is a clean solution. You might add another function for unchanged assesment values. It gets messy when your records have a few more fields.

To address this, JEP 468 has neen proposed. Unfortunately it isn't seen anywhere in JDK 23 or JDK 24. Its syntax follows the spirit of boilerplate avoidance.

// Wealth changed
Billonaire theUpdated = oldBillionaire with { newWealth, newAssesment}

// Wealth unchanged
Billonaire anotherUpdated = oldBillionaire with { newAssesment}

Ultimately that's the way to go. Until then I needed a stopgap measure. It contains quite some boilerplate, following the builder pattern to make use easier

public record Billionaire(String name, Long wealth, Temporal assessment) {

  public BillionaireUpdater forCloning() {
    return new BillionaireUpdater(this);
  }
}

public class BillionaireUpdater {

  Long wealth = null;
  Temporal assessment = null;
  final Billionaire old;


  public BillionaireUpdater(Billionaire old) {
    this.old = old;
  }

  public BillionaireUpdater wealth(Long wealth) {
    this.wealth = wealth;
    return this;
  }

  public BillionaireUpdater assessment(Temporal assessment) {
    this.assessment = assessment;
    return this;
  }

  public Billionaire build() {
    return new Billionaire(
      old.name(),
      this.wealth == null ? old.wealth : this.wealth,
      this.assesment == null ? old.assesment : this.assesment
    );
  }
}

This approach keeps the "bulky" code outside the record, so once JEP 468 becomes available, updating should be managable leading to the ultimate removal of the Updater classes. The use is quite straight forward:

Billionaire theUpdated = oldBillionaire.forCloning()
                                    .wealth(insaneAmount)
                                    .assesment(dateOfAssesment)
                                    .build();

As usual YMMV

Getting your CI/CD pipeline right can be a daunting task. Here is one I had to address:

• Create a Quarkus Java application
• Compile it to a native executable
• Build a container for it
• Make the container available to both Linux and MacOS

The little irony, Docker on macOS or Windowsruns Linux under the hood.

The easy part - Quarkus

As I've written before it is easy to get started with Quarkus. It provides 5 ways to build containers, and detailed instructions to build a native image.

Building a native image looked daunting, with quite some prerequisites like GraalVM, CLI and C compiler. Luckily all this is available in a builder image, and a simple property settin in your pom.xml settles it: