You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Andras Piros (JIRA)" <ji...@apache.org> on 2018/05/03 15:46:00 UTC
[jira] [Commented] (OOZIE-3225) [Kerberos] Webconsole disabled
message shown instead of 401 error
[ https://issues.apache.org/jira/browse/OOZIE-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462631#comment-16462631 ]
Andras Piros commented on OOZIE-3225:
-------------------------------------
Thanks for the contribution [~kmarton]! +1
> [Kerberos] Webconsole disabled message shown instead of 401 error
> -----------------------------------------------------------------
>
> Key: OOZIE-3225
> URL: https://issues.apache.org/jira/browse/OOZIE-3225
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 5.0.0
> Reporter: Julia Kinga Marton
> Assignee: Julia Kinga Marton
> Priority: Major
> Attachments: OOZIE-3225-001.patch
>
>
> In Jetty when defining a filter, we should map them to the call types. Right now, the filters are mapped on request calls, but a call to {{/oozie}} is forwarded to {{index.jsp}}. Since this is a forward call, the filter is skipped, but when trying to get the {{extjs}} dependencies, the error 401 is thrown, so it will be processed as missing dependency, and the Oozie console disabled message will be shown instead of 401 error.
> We should extend the scope of the filters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)