7/10/2017 7:30:10 PM
3.31.0
(#1235)" (#1269)
The PR #1235 (commit 68e507208941659026ac15a1b242364b25f5fa31) introduces a bug which breaks Azkaban's capability to handle multiple HCAT servers. More specifically #1235 introduces a factory class for the Hive Client and caches the `HiveConf` during construction. When fetching delegation tokens from other HCAT servers, it accidentally uses the cached configuration instead of creating a new HiveConf specific to the target HCAT server. Hence it ends up fetching tokens from `HIVE_HOME` configured HCAT server instead of the target HCAT server leading to SASL errors.
Reverting the change. Confirmed that `HadoopSecurityManager_H_2_0` is identical to the version prior to #1235
|
7/10/2017 6:55:23 PM
on java compiler including info on -Werror flag:
http://docs.oracle.com/javase/7/docs/technotes/tools/windows/javac.html
|
7/10/2017 6:49:11 PM
been scraped and wasn't implemented in totality. Removing dead code.
|
|
|
6/29/2017 10:42:44 PM
from running Azkaban flows (#1257)
* Issue #1256 - enabling config setting to prevent service users from running Azkaban flows
|
|
|
6/28/2017 8:28:12 PM
(#1253)
|
6/28/2017 7:16:38 PM
(#1255)
The current code uses the `SERVICE_PROVIDER` interface to fetch dependencies for the Web Server. Refactored the code to enable parameterized dependency injection from the construction which is the standard way of declaring dependencies. In the process, removed legacy constructor from `AzkabanWebServer` and removed legacy class `AzkabanServletContextListener` which is no longer being used.
Injection sanity tests already exist in the code. Tested solo server and it works as well.
|
|
|
6/27/2017 7:04:20 PM
to #990
Users currently can login by passing their credentials through the query string in the URI in this method:
curl -X POST http://localhost:8081/?action=login\&username=azkaban\&password=azkaban
This leads to sensitive information being logged in access logs and overall isn't a secure method of logging in.
This PR fails these attempts and returns an appropriate warning to users. It also stops the query string from being logged when these requests are made.
This PR includes testing to replicate this user behavior for future regression testing.
|
