Welcome to the #dominoforever Product Ideas Lab! 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 jointly by the IBM & 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.


Review Java Security Policy

This may be a moot point if the preferred approach for Java development is e.g. OpenLiberty / Liberty Profile + gRPC to Notes / Domino.

But if Java development on the Domino stack is still a recommended approach, the Java security policy needs review. There are limitations that prevent Java reflection using JAXB or Jackson. There are environmental restrictions that are used in e.g. Watson libraries. See https://openntf.org/main.nsf/project.xsp?r=project/Watson%20Developer%20Cloud%20Java%20SDK%20XPages%20Library.

There may be other recommended changes, it's worth canvassing Domino Java experts.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 21 2018
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    October 16, 2018 10:36

    In fact here is no real Java security on Domino. Every Java agent (and Java code called via LS2J) can easily do anything on the machine. One can just turn off Java security by granting AllPermission to every one.