Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1jHmHQ-00036q-3C for pgadmin-hackers@arkaria.postgresql.org; Fri, 27 Mar 2020 10:32:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jHmHO-0001QW-Sx for pgadmin-hackers@arkaria.postgresql.org; Fri, 27 Mar 2020 10:31:58 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1jHmHN-0001QP-OE for pgadmin-hackers@lists.postgresql.org; Fri, 27 Mar 2020 10:31:58 +0000 Received: from mail-vs1-xe42.google.com ([2607:f8b0:4864:20::e42]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jHmHJ-0004b8-UH for pgadmin-hackers@lists.postgresql.org; Fri, 27 Mar 2020 10:31:56 +0000 Received: by mail-vs1-xe42.google.com with SMTP id e138so5821358vsc.11 for ; Fri, 27 Mar 2020 03:31:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Yo4g6wbH/QP1QVGIgxsK2i9bLyprh0MJHo2WxmpuqCU=; b=ni5h9R0yE7ufmqpGZ9vqwbBLPrH9Ttnb58AFW5dvVBghmchA308n8HMTi3j+CEmd3A 0uJRtQCb5qbO+BchD8bysgCZsSx0yvXnKw4gZgj6PB5BZjqWwDmr49N9FA326keHYUuT ZofYs9GQdceUnVACuTjRfm3EYjsl5gnC3pjjTBlVMZJp4IRbttRSgSADCrzIxF0A+Qdc Jtb2eTIZlJIi+EltlGZIEkeJzeLshqtlyuwECp6Tlwdi0tskwftuFXusOcrsPcioQTC4 7exuiI4BSYwKSjBkQTLKohDLEmNAOixTtZ1elp1Pyaor2sn6kdje5SsJskHiLzU+SawR oNbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Yo4g6wbH/QP1QVGIgxsK2i9bLyprh0MJHo2WxmpuqCU=; b=jr5ld/GCSKTen2ySUfFgYur3PGR48nwvUzVXreWow2UyivB8T9psHZVhUNolnL8HVh PjJ/auU68ir+yn35vFK/xUYdwnb+VtXj1wqZ7PqQaLHG1jlzF5ERLZ6ohLRJYy4RUhLH iag4z+Py2M/osEVEFsbJPz8EeBdrsYwcmVe0NiAcqCO/mwk7rQkGmTrECXvLKpA7il1J X6qDlRgtfNcT6TSkfQVADwTFRWg0+6Qxs55Z/H42uvD54Lze0fVknzl6daqhofKJPFyH sHJYu+1HjueSQl+hlLbH5r0e3B3XsKegnQt3k6gBmqZw1+Ufm75kO3BQWRsN+hAbrUkb 8lRQ== X-Gm-Message-State: ANhLgQ3Jxys4UrvySPCn0lxRFhiB6Efy4ePSb5MA+YQLS1irkaU0REM9 Y1taAxfwhtMkAWxsrMerouHVgCyfAETPHo8gJR2y8A== X-Google-Smtp-Source: ADFU+vuSyRnnxhpCN2dDCSFKbnkBTim+27IhoOreEEsajuWHtF4jefKBmdM8uqr6/Lixlh2vDspBG92GbiTgCuhDDkQ= X-Received: by 2002:a67:d60d:: with SMTP id n13mr11495740vsj.230.1585305113072; Fri, 27 Mar 2020 03:31:53 -0700 (PDT) MIME-Version: 1.0 References: <376C920F3015BC43A3485A86670B336C2E1884A3@TW-MBX-P03.cnesnet.ad.cnes.fr> In-Reply-To: From: Dave Page Date: Fri, 27 Mar 2020 10:31:37 +0000 Message-ID: Subject: Re: disable create server To: Khushboo Vashi Cc: Pavy Manuel , "pgadmin-hackers@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000202c3705a1d39cce" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000202c3705a1d39cce Content-Type: text/plain; charset="UTF-8" On Fri, Mar 27, 2020 at 4:24 AM Khushboo Vashi < khushboo.vashi@enterprisedb.com> wrote: > Hi, > > On Fri, Mar 27, 2020 at 3:56 AM Pavy Manuel wrote: > >> Hello, >> >> I'm new in the pgadmin list. >> I try to deploy pgadmin4 on my company but I want to manage the >> connections (server in pgadmin) the users can create. >> So, I've found the line 84 of >> pgadmin/dashboard/templates/dashboard/welcome_dashboard.html to disable the >> link : >> >> >> , but I don't find how to disable the context menu in the right of the >> dashboard (each try has no impact on the application, perhaps caused by >> some cache or something like that). >> >> Can someone help me please ? Is there any other way to do what I want ? >> >> I didn't get the idea of stopping users to create servers. If any user > has database access (may be limited) then he should be able to create it > and manage it as pgAdmin *just connects* the database with the given > details in the server dialog. > It seems like a reasonable request to me - for example, to stop students adding random servers to a shared instance of pgAdmin that they're only supposed to be using for coursework. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company --000000000000202c3705a1d39cce Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Fri, Mar 27, 2020 at 4:24 AM Khush= boo Vashi <khushboo.v= ashi@enterprisedb.com> wrote:
Hi,

On Fri, Mar 27, 2020 at 3:56 = AM Pavy Manuel <Manuel.Pavy@cnes.fr> wrote:
Hello,

I'm new in the pgadmin list.
I try to deploy pgadmin4 on my company but I want to manage the connections= (server in pgadmin) the users can create.
So, I've found the line 84 of pgadmin/dashboard/templates/dashboard/wel= come_dashboard.html to disable the link :
<a href=3D"#" onclick=3D"pgAdmin.Dashboard.add_new_server= ()">

, but I don't find how to disable the context menu in the right of the = dashboard (each try has no impact on the application, perhaps caused by som= e cache or something like that).

Can someone help me please ? Is there any other way to do what I want ?

I didn't get the idea of stopping users to create= servers. If any user has database access (may be limited) then he should b= e able to create it and manage it as=C2=A0pgAdmin just connects the = database with the given details in the server dialog.

It seems like a reasonable request to me - for= example, to stop students adding random servers to a shared instance of pg= Admin that they're only supposed to be using for coursework.
= =C2=A0
--
Dave Pa= ge
Blog: http:= //pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterpris= edb.com
The Enterprise PostgreSQL Company
--000000000000202c3705a1d39cce--