From commits-return-3965-apmail-ace-commits-archive=ace.apache.org@ace.apache.org Mon Nov 11 10:34:25 2013 Return-Path: X-Original-To: apmail-ace-commits-archive@www.apache.org Delivered-To: apmail-ace-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 46A5410EA4 for ; Mon, 11 Nov 2013 10:34:25 +0000 (UTC) Received: (qmail 19341 invoked by uid 500); 11 Nov 2013 10:34:23 -0000 Delivered-To: apmail-ace-commits-archive@ace.apache.org Received: (qmail 18912 invoked by uid 500); 11 Nov 2013 10:34:20 -0000 Mailing-List: contact commits-help@ace.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ace.apache.org Delivered-To: mailing list commits@ace.apache.org Received: (qmail 18661 invoked by uid 99); 11 Nov 2013 10:34:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Nov 2013 10:34:18 +0000 Date: Mon, 11 Nov 2013 10:34:18 +0000 (UTC) From: "J.W. Janssen (JIRA)" To: commits@ace.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACE-427) Disabling authentication in WebUI trigger a NullPointerException MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818842#comment-13818842 ] J.W. Janssen commented on ACE-427: ---------------------------------- I do not think this is directly related to the disabling of authentication rather than probably having two browser windows open with the Vaadin UI? I've seen Vaadin reacting rather strangely to this by throwing the above exception. Could you verify this by simply restarting the Vaadin UI? > Disabling authentication in WebUI trigger a NullPointerException > ---------------------------------------------------------------- > > Key: ACE-427 > URL: https://issues.apache.org/jira/browse/ACE-427 > Project: ACE > Issue Type: Bug > Components: Authentication, UI > Environment: Mac OSX. Sun JDK 1.7.0-25_b15. > Reporter: Damien Martin-Guillerez > Priority: Blocker > > The affected version is actually on SVN in the trunk, revision 1524399 > Disabling the authentication by setting ui.authentication.enabled = false in conf/org.apache.ace.webui.vaadin.cfg generates a nullpointerexception when loading the page. > 2013.11.10 23:54:38 WARNING - Bundle: org.apache.ace.webui.vaadin - Login failed! Destroying session... - java.lang.NullPointerException > at org.apache.ace.webui.vaadin.ShortcutHelper.getPlatformSpecificModifier(ShortcutHelper.java:81) > at org.apache.ace.webui.vaadin.ShortcutHelper.addCrossPlatformShortcut(ShortcutHelper.java:34) > at org.apache.ace.webui.vaadin.VaadinClient.addCrossPlatformAddShortcut(VaadinClient.java:484) > at org.apache.ace.webui.vaadin.VaadinClient.createAddArtifactButton(VaadinClient.java:549) > at org.apache.ace.webui.vaadin.VaadinClient.createArtifactToolbar(VaadinClient.java:723) > at org.apache.ace.webui.vaadin.VaadinClient.initGrid(VaadinClient.java:1115) > at org.apache.ace.webui.vaadin.VaadinClient.doLogin(VaadinClient.java:964) > at org.apache.ace.webui.vaadin.VaadinClient.loginAutomatically(VaadinClient.java:1196) > at org.apache.ace.webui.vaadin.VaadinClient.authenticate(VaadinClient.java:523) > at org.apache.ace.webui.vaadin.VaadinClient.init(VaadinClient.java:339) > at com.vaadin.Application.start(Application.java:551) > at org.apache.ace.webui.vaadin.VaadinClient.start(VaadinClient.java:416) > at com.vaadin.terminal.gwt.server.AbstractApplicationServlet.startApplication(AbstractApplicationServlet.java:1219) > at com.vaadin.terminal.gwt.server.AbstractApplicationServlet.service(AbstractApplicationServlet.java:484) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:96) > at org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:79) > at org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:42) > at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:49) > at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33) > at org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(FilterPipeline.java:48) > at org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:39) > at org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java:67) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:654) > at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:445) > at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:225) > at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1044) > at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:372) > at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:189) > at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:978) > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) > at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) > at org.eclipse.jetty.server.Server.handle(Server.java:369) > at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:486) > at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:933) > at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:995) > at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644) > at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) > at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) > at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) > at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) > at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) > at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) > at java.lang.Thread.run(Thread.java:724) > My use-case (reason for me using this feature): I want to embed the server in our systems using a proxy from another Jetty instance with LDAP authentication. The webui should be accessible to our dev team while the API only accessible from authenticated networks (i.e., no authentication is used from ACE, iptables filtering allows only some interfaces to connect to ACE, only one entry point for all our development and admin tools) -- This message was sent by Atlassian JIRA (v6.1#6144)