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

Add a new idea Subscribe
Status Needs Clarification
Workspace Domino
Categories Security
Created by Guest
Created on Feb 6, 2023

RELATED IDEAS

Create authentication exclusion certains users / groups

Domino 11.0 introduced web authentication via IDVault (and / or Directory)

Customers noticed large growing DDM databases and also flooding of console messages with error messages:

[0594:0013-1CE8] 10.08.2022 07:00:01 Event: Error adding event document to Domino Domain Monitoring: Event correlation cache is full. You can increase its size via the NOTES.INI setting EVENT_CORRELATION_POOL_SIZE.

[0594:0013-1CE8] Event correlation cache is full, too many Event documents in DDM.NSF for this server. You can increase the cache size by setting the EVENT_CORRELATION_POOL_SIZE setting in NOTES.INI. Default size is 73.400.320 bytes. Maximum size is 104.857.600 bytes.


After creating a case (CS0346074) with HCL-Support no suitable solution was found.

Creating a DDM filter or changing the authentication is not a suitable option. Excluding users from the Security-Policy with IDVault did not solve the issue.

=> It should be possible to exclude users (direct and via group) from the IDVault authentication mechanism, or create a logic that will only authenticate vaulted users with the IDVault. All others should use "directory" authentication.


  • Attach files
  • Guest
    Reply
    |     Feb 8, 2023

    If you check the history above mentioned case# the support found the root cause of the above DDM errors are caused by the failed IDVault authentication attempts, which are logged to DDM.


    Server01 -->IDvault server Failed to authenticate with server Server01/Org/C: User not found in the ID vault. [1888:0022-069C] 13.01.2023 10:45:00 Server Server01/Org/Creported the following problem causing authentication to fail: Entry not found in index

    Server02-->non vault server [08D0:0022-11E4] 17.01.2023 07:19:43 Server Server02/Org/C reported the following problem causing authentication to fail: Entry not found in index [08D0:0022-11E4] 17.01.2023 07:19:55 Server Server02/Org/C reported the following problem causing authentication to fail: Entry not found in index [09A0:0021-16CC] 17.01.2023 07:20:01 Failed to authenticate with server Server02/Org/C: User not found in the ID vault. [09A0:0021-16CC] 17.01.2023 07:20:01 Failed to authenticate with server Server02/Org/C: User not found in the ID vault

  • Admin
    Thomas Hampel
    Reply
    |     Feb 8, 2023

    How come you are assuming that this console message has anything to do with the IDVault?

Copyright © 2023 HCL Technologies Limited