Home
Administering Domino Leap
The following topics contain information for HCL Domino Leap admins.
Securing your Domino Leap deployment

Administering Domino Leap
The following topics contain information for HCL Domino Leap admins.
- Controlling who creates HCL Domino Leap applications
  To configure who can create and delete applications, you need to modify the Access Control List (ACL) for VoltBuilder.nsf.
- Domino Leap configuration settings
  Domino Leap configuration settings are in VoltConfig.nsf in the volt folder of your Domino data directory (volt/VoltConfig.nsf). Use the Notes client or the Domino Administrator client to modify a configuration setting.
- Core Domino server configuration
  HCL Domino Leap is an add-on to the core HCL Domino server. Domino Leap runs in the context of the Domino web server (HTTP process). Therefore, Domino Leap is affected by the underlying Domino server configuration. This topic covers some of the core configuration settings that may affect Domino Leap.
- Upgrading from prior releases
  All Domino Leap NSF files set the database property Don't Maintain Unread Marks as default, which should improve performance. NSF files created in prior versions of Domino Leap are not changed.
- Adding a custom theme
- Domino Leap Cleanup process
  Domino Leap Cleanup primarily purges orphaned Builder attachments, orphaned application attachments, and old Preview databases. Prior to release 1.0.3, this process was done by the Domino Leap Cleanup Agent.
- Enabling basic authentication for HCL Domino Leap API requests
  If form-based authentication is enabled, you will see an HTML form for authentication instead of a pop-up window. This topic provides instructions on how to disable HTML form-based authentication for the HCL Domino Leap server API URL paths and enable basic authentication.
- Securing your Domino Leap deployment
- HCL Link integration
  HCL Link provides a platform for data and application integration.
- Strict CSP
  HCL Domino Leap has a limited capability to restrict the rendering of Domino Leap Forms using a “Strict CSP” policy.
- Admin Application Dashboard
  The Admin Application Dashboard is a page that is available to members of the Admin or SuperAdmin groups.
- Integrating with HCL Volt MX Foundry
  HCL Domino Leap can now use the integration services defined in HCL Volt MX Foundry.

Securing your Domino Leap deployment

The data for each Domino Leap application is stored in a separate Domino database. The ACLs of the database, the permissions, and the access to documents within it are matched as closely as possible to the Domino Leap permissions model - which is enforced by Domino Leap code. One difference is that Domino Leap offers a further refinement and enforcement beyond simply "Author" in a Domino Database ACL. With enough privilege and access through a non-Domino Leap channel, users can create documents in the Domino database that they wouldn't be able to create through Domino Leap UIs or REST endpoints. If this is a concern, below are some of the options that can be leveraged:

NRPC Access - The Domino Leap server can be configured to disallow communication through non-Domino Leap channels. For example, the Domino administrator may wish to limit communication via NRPC port on the Domino Leap server.
Hide Form - Another option is to hide Forms from the Create menu in a Domino Database by unchecking the box to "Appear in Create Menu".
Separate Database - Another option is to advise application authors to use a separate Domino Leap application if the creation of documents related to a specific form needs to be more tightly controlled.
Extending via Domino Application Modifications - Domino applications can have various form or database events added to monitor and control any unintended activity. For example, an agent that alerts when a form is created by someone without the right role. This option is similar to how protections are enforced in a traditional Domino application.