Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Wed, 12 Aug 2015 16:26:45 +0000 (UTC)
From: "Christian Schneider (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12855537.1439382053000.46648.1439396805891@Atlassian.JIRA>
In-Reply-To: <JIRA.12855537.1439382053000@Atlassian.JIRA>
References: <JIRA.12855537.1439382053000@Atlassian.JIRA>
 <JIRA.12855537.1439382053083@arcas>
Subject: [jira] [Commented] (KARAF-3930) When starting the gogo shell in the
 webconsole the user is not fully authenticated
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/KARAF-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693755#comment-14693755 ] 

Christian Schneider commented on KARAF-3930:
--------------------------------------------

Found the problem. This was a tricky one.

OSGiManager has two methods:
service(final ServletRequest req, final ServletResponse res)
and
void service(HttpServletRequest request, HttpServletResponse response)

The first calls the second with AccessController.doPrivileged which invalidates our jaas login. So we needed to make sure the second is called.
Unfortunately the second is only package visible. As we were in a different package with our KarafOsgiManager it fell back to call the first one transparently.


> When starting the gogo shell in the webconsole the user is not fully authenticated
> ----------------------------------------------------------------------------------
>
>                 Key: KARAF-3930
>                 URL: https://issues.apache.org/jira/browse/KARAF-3930
>             Project: Karaf
>          Issue Type: Bug
>          Components: webconsole
>    Affects Versions: 4.0.0
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>             Fix For: 4.0.1
>
>
> When starting the gogo console in webconsole the prompt shows like this:
> {noformat}${USER}@root(){noformat}
> I think the reason for this is that the user ise not correctly authenticated. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)