SBUS: increase SBUS_MESSAGE_TIMEOUT to 5 mins

Handling BE_REQ_INITGROUPS for LDAP user with 10k groups takes longer
than 2 mins.

Author: alexey-tikhonov

src/responder/common/responder_common.c

@@ -33,6 +33,7 @@
 #include <popt.h>
 #include <dbus/dbus.h>
 
+#include "sbus/sbus_message.h"
 #include "util/util.h"
 #include "util/strtonum.h"
 #include "db/sysdb.h"
@@ -1073,6 +1074,13 @@ int sss_process_init(TALLOC_CTX *mem_ctx,
         rctx->client_idle_timeout = 10;
     }
 
+    if (rctx->client_idle_timeout > SBUS_MESSAGE_TIMEOUT) {
+        DEBUG(SSSDBG_CONF_SETTINGS, "'"CONFDB_RESPONDER_CLI_IDLE_TIMEOUT
+              "' is configured to a value %d - higher than SBUS_MESSAGE_TIMEOUT %d, "
+              "this usually doesn't make sense.\n",
+              rctx->client_idle_timeout, SBUS_MESSAGE_TIMEOUT);
+    }
+
     if (rctx->socket_activated) {
         ret = responder_setup_idle_timeout_config(rctx);
         if (ret != EOK) {

src/sbus/sbus_message.h

@@ -29,8 +29,10 @@
 
 /* Use longer default timeout than libdbus default due to expensive
  * selinux operation: see https://bugzilla.redhat.com/show_bug.cgi?id=1654537
+ * Another example of a very long running operation - BE_REQ_INITGROUPS where
+ * the user is a member of tens of thousands of groups.
  */
-#define SBUS_MESSAGE_TIMEOUT 120000
+#define SBUS_MESSAGE_TIMEOUT 300000
 
 /**
  * Bound message with a talloc context.