[
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)
