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
While this is being investigated, you can update your configuraiton to use SAML instead of SPNEGO.
These are the support ticket numbers opened to HCL about this problem:
CS0328339
CS0296352
Here HCL can found all logs and documentation.
I hope that HCL solves asap this vulnerability problem that at the moment makes Domino an obsolete and unsafe product.
It has been already done. Please check the TrackingID#2202140050002105.
After a case opened in february and closed in august we will not spend any more time and resources. We know only that Domino fails to handle any encryption different from RC4. HCL technical support closed the ticket confirming that Domino needs RC4 to work correctly. Discover how exactly Domino fails in handling any other encryption type is a job of technical support, not the customer.
Please open a support ticket for this matter. Please provide steps to reproduce + how does one configure these other algorithms, and how exactly would Domino fail to handle them
Microsoft declared end of support for RC4_HMAC_MD5 in february 2015 after IETF prohibited RC4 Cipher suites in TLS with RFC 7465
https://www.rfc-editor.org/rfc/rfc7465.html
The use of RC4 encryption is reported as a vulnerability from security tools.
This makes Domino an obsolete and unsafe product unless it will be updated.