#dominoforever | Product 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

Add a blanket grant for the XPages JVM to the default java.policy file

I just lost two days, just to find out that our RuntimePermission exception (getClassLoader) in Java is caused by a missing setting in a java.policy file, somewhere deep in the Domino tree. In the end, after trying several different settings, the only one that solved the issue was

grant { permission java.security.AllPermission; };

Apparently, the java.policy is overwritten during installation, so I'd like to request, on behalf of all XPages users, that this grant be added to the default java.policy file.

  • Guest
  • Jun 26 2021
  • Under Consideration
  • Attach files
  • Guest commented
    30 Jun, 2021 09:05am

    Agree with the comment dated 28 Jun 10:41, i.e. making it easier for admins to extend permissions for distinct applications (rather than granting full permissions to all applications by default).

  • Guest commented
    28 Jun, 2021 10:41am

    Idea for the implementation: change the Domino Java SecurityManager so that an admin can configure which XPages application get full permissions.

  • Guest commented
    26 Jun, 2021 06:31pm

    This is one of XPages developers' eternal banes, where the environment doesn't provide a nuanced SecurityManager, letting everything fall to the default, too-locked-down configuration. This means that XPages apps don't have an option to do even basic things like reflection without deploying code via bundles or altering the policy files.