apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-757) Web authentication DISABLE option not working
Date Fri, 14 Jul 2017 16:40:00 GMT

    [ https://issues.apache.org/jira/browse/APEXCORE-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087561#comment-16087561

ASF GitHub Bot commented on APEXCORE-757:

vrozov commented on a change in pull request #556: APEXCORE-757 Web authentication DISABLE
option not working.
URL: https://github.com/apache/apex-core/pull/556#discussion_r127497763

 File path: engine/src/main/java/com/datatorrent/stram/StreamingAppMasterService.java
 @@ -644,6 +644,15 @@ protected void serviceStart() throws Exception
       if (SecurityUtils.isStramWebSecurityEnabled()) {
 Review comment:
   It should not matter whether the function can be reused or not. It is an encapsulation
of the logic and the functionality. StreamingAppMasterService.java is already over 13 hundred
lines of code, so any logic that can be offloaded to another class should be moved there.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Web authentication DISABLE option not working
> ---------------------------------------------
>                 Key: APEXCORE-757
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-757
>             Project: Apache Apex Core
>          Issue Type: Bug
>            Reporter: Thomas Weise
>            Assignee: Thomas Weise
> On a secure cluster that has authentication enabled for the YARN web services, Apex is
configured with:
>   <property>
>     <name>apex.attr.STRAM_HTTP_AUTHENTICATION</name>
>     <value>DISABLE</value>
>   </property>
> "DISABLE - Disable authentication for web services."
> Instead it follows the Hadoop setting and fails because in this case Kerberos is enabled
and the keytab not configured.

This message was sent by Atlassian JIRA

View raw message