From user-return-6761-apmail-drill-user-archive=drill.apache.org@drill.apache.org Fri Aug 26 15:09:43 2016 Return-Path: X-Original-To: apmail-drill-user-archive@www.apache.org Delivered-To: apmail-drill-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C113E19952 for ; Fri, 26 Aug 2016 15:09:43 +0000 (UTC) Received: (qmail 89676 invoked by uid 500); 26 Aug 2016 15:09:43 -0000 Delivered-To: apmail-drill-user-archive@drill.apache.org Received: (qmail 89606 invoked by uid 500); 26 Aug 2016 15:09:43 -0000 Mailing-List: contact user-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@drill.apache.org Delivered-To: mailing list user@drill.apache.org Received: (qmail 89595 invoked by uid 99); 26 Aug 2016 15:09:43 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Aug 2016 15:09:43 +0000 Received: from mail-oi0-f45.google.com (mail-oi0-f45.google.com [209.85.218.45]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 3AC971A0118 for ; Fri, 26 Aug 2016 15:09:43 +0000 (UTC) Received: by mail-oi0-f45.google.com with SMTP id f189so113906608oig.3 for ; Fri, 26 Aug 2016 08:09:43 -0700 (PDT) X-Gm-Message-State: AE9vXwMJyl1bG7dS8aVeNz8vUGSt+yEicYAzZc2oBhQKpYUH0a7jjejbrQy4qbQvyiUFp+itwZDL7MqFZSZH/w== X-Received: by 10.202.104.69 with SMTP id d66mr3027761oic.83.1472224182223; Fri, 26 Aug 2016 08:09:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.9.7 with HTTP; Fri, 26 Aug 2016 08:09:41 -0700 (PDT) In-Reply-To: References: From: Jinfeng Ni Date: Fri, 26 Aug 2016 08:09:41 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Facing issue with drill web UI. To: user Content-Type: text/plain; charset=UTF-8 That's probably because your login is not an admin user, or does not belong to a group having the admin authorization. Take a look at [1] [1] https://drill.apache.org/docs/configuring-web-console-and-rest-api-security/ On Fri, Aug 26, 2016 at 12:10 AM, Sonali Ghorpade wrote: > Hi, > > I have configured custom authentication in dill and modified the > drill-override.conf file according to the documentation mentioned in below > link. > > https://drill.apache.org/docs/configuring-user-authentication/ > my authentication jar is working fine. but after modifying the > drill-override.conf the Storage, Threads, Logs tab in drill web UI is not > seen. can anyone please help me with this issue. my content of > rill-override.conf are > drill.exec { > > cluster-id: "XXXXXXX", > > zk.connect: "XXXX", > security.user.auth { > > enabled: true, > > packages += "org.ebi.drill.security", > > impl: "CustomAuthenticatorType" > > } > > } > if i comment the security.user.auth the Storage, Threads, Logs tab in drill > web UI is shown.please refer the attachment