[INCOMPATIBLE CHANGE] Atlas API Authentication

[Hemanth Yamijala <hy...@hortonworks.com>]

Hi,

As you may have been following, in ATLAS-661 (https://issues.apache.org/jira/browse/ATLAS-661), work was done to introduce authentication to Atlas API. This change is now committed and it is likely to cause a few incompatibilities to those integrating via API. While in future there should be documentation that explains everything, this mail is a quick heads up to highlight some of the changes:

  *   Atlas API will now fail if not provided with a username / password. The username / password can be specified from a few sources: a file (for simplicity) or from LDAP. To quickly bootstrap, you could set a username and password in the file user-credentials.properties in the Atlas conf directory on the server. The password is a hash and there is some instruction on how to generate this here: (https://issues.apache.org/jira/browse/ATLAS-661?focusedCommentId=15258397&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15258397).
     *   Once, the password is set as above, curl –u <username:password> can be used to test the APIs.
  *   Utilities of Atlas like quick start, hive-import and atlas-admin all expect a user name and password now. (This may break any scripts that were written to create data).

In future, tests will be done to integrate Atlas with Kerberized environments and authentication would use Kerberos principal details in such case. Further information will be published via JIRA (or this mailing list) for such changes.

Please provide any feedback you see here via opening additional JIRAs or on this mailing list.

I hope original contributors would participate in the discussion as well.

Another heads-up is ATLAS-497 (https://issues.apache.org/jira/browse/ATLAS-497) which will introduce basic Authorization in Atlas. This is likely to get committed very soon as well.

Thanks
hemanth