Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Under Consideration
Workspace Domino
Categories Security
Created by Guest
Created on Jul 15, 2021

Evolve management of Java Security Policy on Domino Server

Domino mandates java security controls to avoid code from performing privileged operation.

Control of policies is defined by java.policy files.

This is a burden for customer, partners and admins.

The proposal is to implement a new Java policy provider (implementing java's policy.provider) that:

  1. Loads config from NSF on server / client (names.nsf form or other database)

  2. Stores policies as documents (using java.policy syntax)

  3. Check for a list of trusted signersbefore loading a policy (notes document must be signed by the user)

  4. Allows to quickly enable/disable policy (eg. Enabled field in db document) (eventually with hot-reload of the policy)

  5. Set priority of documents to build the policy

The expected value for everybody is that:

  1. It is good for security (but also for developers)

  2. Is based on NSFs with all advantages ( replication, secturity, no filesystem access needed)

  3. A catalog of policies can be built for sharing, reuse & optimization

  • Attach files