KCM: Display in the log the limit as set by the user

max_uid_ccaches is unconditionally incremented by 2 in ccdb_secdb_init() to create space for some internal entries. We cannot just show this value as it is not what the user configured. Reviewed-by: Sumit Bose <[email protected]> Reviewed-by: Tomáš Halman <[email protected]> (cherry picked from commit 96d8b77)
SSSD · Oct 11, 2023 · 834b536 · 834b536
1 parent 1fa7210
commit 834b536
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/src/responder/kcm/secrets/secrets.c b/src/responder/kcm/secrets/secrets.c
@@ -381,11 +381,12 @@ static int local_db_check_peruid_number_of_secrets(TALLOC_CTX *mem_ctx,
         ret = local_db_remove_oldest_expired_secret(res, req);
         if (ret != EOK) {
             if (ret == ERR_NO_MATCHING_CREDS) {
+                /* max_uid_secrets is incremented by 2 for internal entries. */
                 DEBUG(SSSDBG_OP_FAILURE,
                       "Cannot store any more secrets for this client (basedn %s) "
                       "as the maximum allowed limit (%d) has been reached\n",
                       ldb_dn_get_linearized(cli_basedn),
-                      req->quota->max_uid_secrets);
+                      req->quota->max_uid_secrets - 2);
                 ret = ERR_SEC_INVALID_TOO_MANY_SECRETS;
             }
             goto done;