[jira] [Updated] (ATLAS-2824) Atlas authentication to support proxy-user

[Madhan Neethiraj (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Madhan Neethiraj updated ATLAS-2824:

Fix Version/s: (was: 1.1.0)
   1.2.0
   2.0.0
  Description: Atlas authentication module should support the notion of 
proxy-user, who would be allowed to perform operations on behalf of other users 
i.e. impersonate other users - similar to Hadoop as documented 
[here|https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/Superusers.html].
  Component/s: (was: atlas-webui)
atlas-core
  Summary: Atlas authentication to support proxy-user  (was: Atlas to 
configure & support Trusted Knox Proxy )

> Atlas authentication to support proxy-user
> --
>
> Key: ATLAS-2824
> URL: https://issues.apache.org/jira/browse/ATLAS-2824
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 2.0.0, 1.2.0
>
> Attachments: ATLAS-2824.patch
>
>
> Atlas authentication module should support the notion of proxy-user, who 
> would be allowed to perform operations on behalf of other users i.e. 
> impersonate other users - similar to Hadoop as documented 
> [here|https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/Superusers.html].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2940) Documentation and atlas_start.py script for Atlas Setup are not aligned with new versions

[Fabio Badali (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fabio Badali updated ATLAS-2940:

Description: 
Following the steps described in 
[https://atlas.apache.org/InstallationSteps.html], particularly:
{quote}
h5. Setting up Apache Atlas

There are a few steps that setup dependencies of Apache Atlas. One such example 
is setting up the [JanusGraph|https://atlas.apache.org/JanusGraph.html] schema 
in the storage backend of choice. In a simple single server setup, these are 
automatically setup with default configuration when the server first accesses 
these dependencies.

However, there are scenarios when we may want to run setup steps explicitly as 
one time operations. For example, in a multiple server scenario using [High 
Availability|https://atlas.apache.org/HighAvailability.html], it is preferable 
to run setup steps from one of the server instances the first time, and then 
start the services.

To run these steps one time, execute the command {{bin/atlas_start.py -setup}} 
from a single Apache Atlas server instance.

However, Apache Atlas server does take care of parallel executions of the setup 
steps. Also, running the setup steps multiple times is idempotent. Therefore, 
if one chooses to run the setup steps as part of server startup, for 
convenience, then they should enable the configuration option 
{{atlas.server.run.setup.on.start}} by defining it with the value {{true}} in 
the {{atlas-application.properties}} file.
{quote}
I got the following error:
{code:java}
Error: Could not find or load main class 
org.apache.atlas.web.setup.AtlasSetup{code}
It seems the class was removed after refactoring in commit 
[96fb0e|https://github.com/apache/atlas/commit/96fb0e77a4fd979d1ff49ac6b3dd290d5bf721a9].
 Documentation and/or script should be modified accordingly to new version.

 

  was:
Following the steps described in 
[https://atlas.apache.org/InstallationSteps.html], particularly:
{quote}
h5. Setting up Apache Atlas

There are a few steps that setup dependencies of Apache Atlas. One such example 
is setting up the [JanusGraph|https://atlas.apache.org/JanusGraph.html] schema 
in the storage backend of choice. In a simple single server setup, these are 
automatically setup with default configuration when the server first accesses 
these dependencies.

However, there are scenarios when we may want to run setup steps explicitly as 
one time operations. For example, in a multiple server scenario using [High 
Availability|https://atlas.apache.org/HighAvailability.html], it is preferable 
to run setup steps from one of the server instances the first time, and then 
start the services.

To run these steps one time, execute the command {{bin/atlas_start.py -setup}} 
from a single Apache Atlas server instance.

However, Apache Atlas server does take care of parallel executions of the setup 
steps. Also, running the setup steps multiple times is idempotent. Therefore, 
if one chooses to run the setup steps as part of server startup, for 
convenience, then they should enable the configuration option 
{{atlas.server.run.setup.on.start}} by defining it with the value {{true}} in 
the {{atlas-application.properties}} file.
{quote}
I got the following error:

 
{code:java}
Error: Could not find or load main class 
org.apache.atlas.web.setup.AtlasSetup{code}
It seems the class was removed after refactoring in commit 
[96fb0e|https://github.com/apache/atlas/commit/96fb0e77a4fd979d1ff49ac6b3dd290d5bf721a9].
 Documentation and/or script should be modified accordingly to new version.

 


> Documentation and atlas_start.py script for Atlas Setup are not aligned with 
> new versions
> -
>
> Key: ATLAS-2940
> URL: https://issues.apache.org/jira/browse/ATLAS-2940
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.1, 1.0.0-alpha, 0.8.2, 1.0.0, 0.8.3, 1.1.0
>Reporter: Fabio Badali
>Priority: Minor
>
> Following the steps described in 
> [https://atlas.apache.org/InstallationSteps.html], particularly:
> {quote}
> h5. Setting up Apache Atlas
> There are a few steps that setup dependencies of Apache Atlas. One such 
> example is setting up the 
> [JanusGraph|https://atlas.apache.org/JanusGraph.html] schema in the storage 
> backend of choice. In a simple single server setup, these are automatically 
> setup with default configuration when the server first accesses these 
> dependencies.
> However, there are scenarios when we may want to run setup steps explicitly 
> as one time operations. For example, in a multiple server scenario using 
> [High Availability|https://atlas.apache.org/HighAvailability.html], it is 
> preferable to run setup steps from one of the server instances the first 
> time, and then start the services.
> To run these 

Re: Review Request 68363: ATLAS-2824 :- Atlas to support Trusted Knox Proxy

[Ashutosh Mestry]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/68363/#review210140
---




webapp/src/main/java/org/apache/atlas/web/filters/AtlasTrustedProxyFilter.java
Lines 84 (patched)


Consider inverted if.



webapp/src/main/java/org/apache/atlas/web/filters/AtlasTrustedProxyFilter.java
Lines 119 (patched)


Consider separate method.



webapp/src/main/java/org/apache/atlas/web/filters/AtlasTrustedProxyFilter.java
Lines 125 (patched)


Consider inverted if.



webapp/src/main/java/org/apache/atlas/web/security/AtlasProxyAuthenticator.java
Lines 52 (patched)


Properties.getProperty can potentially return NULL. In which case, this 
will case NPE.



webapp/src/main/java/org/apache/atlas/web/security/AtlasProxyAuthenticator.java
Lines 69 (patched)


Consider inverted if.



webapp/src/main/java/org/apache/atlas/web/security/AtlasProxyAuthenticator.java
Lines 109 (patched)


Since if is returning, else is not needed.


- Ashutosh Mestry


On Oct. 29, 2018, 1:07 p.m., Nixon Rodrigues wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68363/
> ---
> 
> (Updated Oct. 29, 2018, 1:07 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, Larry McCay, Madhan 
> Neethiraj, and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-2824
> https://issues.apache.org/jira/browse/ATLAS-2824
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch includes code to support request from knox proxy, where the proxy 
> is already known and trusted to Atlas via configuration. Atlas intercepts the 
> incoming requests and if it from knox proxy. Atlas allow the knox's doAs user 
> to create session in Atlas. 
> 
> Configs required:-
> 
> atlas.authentication.allow.trustedproxy :- property allow trusted proxy 
> support
> atlas.proxyuser.knox.hosts :- property to add trusted hosts
> atlas.proxyuser.knox.users :- property to add trusted users
> atlas.proxyuser.knox.groups :- property to add trusted groups
> 
> 
> Diffs
> -
> 
>   
> webapp/src/main/java/org/apache/atlas/web/filters/AtlasTrustedProxyFilter.java
>  PRE-CREATION 
>   
> webapp/src/main/java/org/apache/atlas/web/filters/TrustedProxyAuthenticator.java
>  PRE-CREATION 
>   
> webapp/src/main/java/org/apache/atlas/web/security/AtlasProxyAuthenticator.java
>  PRE-CREATION 
>   webapp/src/main/java/org/apache/atlas/web/security/AtlasSecurityConfig.java 
> 24be5de20 
> 
> 
> Diff: https://reviews.apache.org/r/68363/diff/3/
> 
> 
> Testing
> ---
> 
> Tested 
> 
> * Atlas UI from  Trusted Knox Proxy with Knox SSO loginpage.
> * Atlas UI from  Knox Proxy with Atlas Login.
> * Atlas UI from  Knox Proxy with SSO Filter enabled at Atlas.
> * Atlas UI with Atlas Login.
> * Atlas api from curl with BASIS & Kerberos headers
> 
> 
> https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/573/console
> 
> Topology Used:-
> 
> 
> 
>   
> 
> federation
> SSOCookieProvider
> true
> 
> sso.authentication.provider.url
> {KNOXHOST}/gateway/knoxsso/knoxauth/login.html
> 
> 
> 
> identity-assertion
> Default
> true
> 
>   
>   
>   ATLAS
>   {ATLAS_HOST}:21000/
>   
>   
>   ATLAS-API
>   {ATLAS_HOST}:21000
>   
> 
> 
> 
> Thanks,
> 
> Nixon Rodrigues
> 
>

[jira] [Updated] (ATLAS-2940) Documentation and atlas_start.py script for Atlas Setup are not aligned with new versions

[Fabio Badali (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fabio Badali updated ATLAS-2940:

Description: 
Following the steps described in 
[https://atlas.apache.org/InstallationSteps.html], particularly:
{quote}
h5. Setting up Apache Atlas

There are a few steps that setup dependencies of Apache Atlas. One such example 
is setting up the [JanusGraph|https://atlas.apache.org/JanusGraph.html] schema 
in the storage backend of choice. In a simple single server setup, these are 
automatically setup with default configuration when the server first accesses 
these dependencies.

However, there are scenarios when we may want to run setup steps explicitly as 
one time operations. For example, in a multiple server scenario using [High 
Availability|https://atlas.apache.org/HighAvailability.html], it is preferable 
to run setup steps from one of the server instances the first time, and then 
start the services.

To run these steps one time, execute the command {{bin/atlas_start.py -setup}} 
from a single Apache Atlas server instance.

However, Apache Atlas server does take care of parallel executions of the setup 
steps. Also, running the setup steps multiple times is idempotent. Therefore, 
if one chooses to run the setup steps as part of server startup, for 
convenience, then they should enable the configuration option 
{{atlas.server.run.setup.on.start}} by defining it with the value {{true}} in 
the {{atlas-application.properties}} file.
{quote}
I got the following error:

 
{code:java}
Error: Could not find or load main class 
org.apache.atlas.web.setup.AtlasSetup{code}
It seems the class was removed after refactoring in commit 
[[96fb0e|https://github.com/apache/atlas/commit/96fb0e77a4fd979d1ff49ac6b3dd290d5bf721a9]|https://github.com/apache/atlas/commit/96fb0e77a4fd979d1ff49ac6b3dd290d5bf721a9].
 Documentation and/or script should be modified accordingly to new version.

 

  was:
Following the steps described in 
[https://atlas.apache.org/InstallationSteps.html], particularly:
{quote}
h5. Setting up Apache Atlas

There are a few steps that setup dependencies of Apache Atlas. One such example 
is setting up the [JanusGraph|https://atlas.apache.org/JanusGraph.html] schema 
in the storage backend of choice. In a simple single server setup, these are 
automatically setup with default configuration when the server first accesses 
these dependencies.

However, there are scenarios when we may want to run setup steps explicitly as 
one time operations. For example, in a multiple server scenario using [High 
Availability|https://atlas.apache.org/HighAvailability.html], it is preferable 
to run setup steps from one of the server instances the first time, and then 
start the services.

To run these steps one time, execute the command {{bin/atlas_start.py -setup}} 
from a single Apache Atlas server instance.

However, Apache Atlas server does take care of parallel executions of the setup 
steps. Also, running the setup steps multiple times is idempotent. Therefore, 
if one chooses to run the setup steps as part of server startup, for 
convenience, then they should enable the configuration option 
{{atlas.server.run.setup.on.start}} by defining it with the value {{true}} in 
the {{atlas-application.properties}} file.
{quote}
I got the following error:

 
{code:java}
Error: Could not find or load main class 
org.apache.atlas.web.setup.AtlasSetup{code}
It seems the class was removed after refactoring in commit 
[96fb0e|[https://github.com/apache/atlas/commit/96fb0e77a4fd979d1ff49ac6b3dd290d5bf721a9]].
 Documentation and/or script should be modified accordingly to new version.

 


> Documentation and atlas_start.py script for Atlas Setup are not aligned with 
> new versions
> -
>
> Key: ATLAS-2940
> URL: https://issues.apache.org/jira/browse/ATLAS-2940
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.1, 1.0.0-alpha, 0.8.2, 1.0.0, 0.8.3, 1.1.0
>Reporter: Fabio Badali
>Priority: Minor
>
> Following the steps described in 
> [https://atlas.apache.org/InstallationSteps.html], particularly:
> {quote}
> h5. Setting up Apache Atlas
> There are a few steps that setup dependencies of Apache Atlas. One such 
> example is setting up the 
> [JanusGraph|https://atlas.apache.org/JanusGraph.html] schema in the storage 
> backend of choice. In a simple single server setup, these are automatically 
> setup with default configuration when the server first accesses these 
> dependencies.
> However, there are scenarios when we may want to run setup steps explicitly 
> as one time operations. For example, in a multiple server scenario using 
> [High Availability|https://atlas.apache.org/HighAvailability.html], it is 
> preferable to run setup steps from one of 

[jira] [Updated] (ATLAS-2940) Documentation and atlas_start.py script for Atlas Setup are not aligned with new versions

[Fabio Badali (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fabio Badali updated ATLAS-2940:

Description: 
Following the steps described in 
[https://atlas.apache.org/InstallationSteps.html], particularly:
{quote}
h5. Setting up Apache Atlas

There are a few steps that setup dependencies of Apache Atlas. One such example 
is setting up the [JanusGraph|https://atlas.apache.org/JanusGraph.html] schema 
in the storage backend of choice. In a simple single server setup, these are 
automatically setup with default configuration when the server first accesses 
these dependencies.

However, there are scenarios when we may want to run setup steps explicitly as 
one time operations. For example, in a multiple server scenario using [High 
Availability|https://atlas.apache.org/HighAvailability.html], it is preferable 
to run setup steps from one of the server instances the first time, and then 
start the services.

To run these steps one time, execute the command {{bin/atlas_start.py -setup}} 
from a single Apache Atlas server instance.

However, Apache Atlas server does take care of parallel executions of the setup 
steps. Also, running the setup steps multiple times is idempotent. Therefore, 
if one chooses to run the setup steps as part of server startup, for 
convenience, then they should enable the configuration option 
{{atlas.server.run.setup.on.start}} by defining it with the value {{true}} in 
the {{atlas-application.properties}} file.
{quote}
I got the following error:

 
{code:java}
Error: Could not find or load main class 
org.apache.atlas.web.setup.AtlasSetup{code}
It seems the class was removed after refactoring in commit 
[96fb0e|https://github.com/apache/atlas/commit/96fb0e77a4fd979d1ff49ac6b3dd290d5bf721a9].
 Documentation and/or script should be modified accordingly to new version.

 

  was:
Following the steps described in 
[https://atlas.apache.org/InstallationSteps.html], particularly:
{quote}
h5. Setting up Apache Atlas

There are a few steps that setup dependencies of Apache Atlas. One such example 
is setting up the [JanusGraph|https://atlas.apache.org/JanusGraph.html] schema 
in the storage backend of choice. In a simple single server setup, these are 
automatically setup with default configuration when the server first accesses 
these dependencies.

However, there are scenarios when we may want to run setup steps explicitly as 
one time operations. For example, in a multiple server scenario using [High 
Availability|https://atlas.apache.org/HighAvailability.html], it is preferable 
to run setup steps from one of the server instances the first time, and then 
start the services.

To run these steps one time, execute the command {{bin/atlas_start.py -setup}} 
from a single Apache Atlas server instance.

However, Apache Atlas server does take care of parallel executions of the setup 
steps. Also, running the setup steps multiple times is idempotent. Therefore, 
if one chooses to run the setup steps as part of server startup, for 
convenience, then they should enable the configuration option 
{{atlas.server.run.setup.on.start}} by defining it with the value {{true}} in 
the {{atlas-application.properties}} file.
{quote}
I got the following error:

 
{code:java}
Error: Could not find or load main class 
org.apache.atlas.web.setup.AtlasSetup{code}
It seems the class was removed after refactoring in commit 
[[96fb0e|https://github.com/apache/atlas/commit/96fb0e77a4fd979d1ff49ac6b3dd290d5bf721a9]|https://github.com/apache/atlas/commit/96fb0e77a4fd979d1ff49ac6b3dd290d5bf721a9].
 Documentation and/or script should be modified accordingly to new version.

 


> Documentation and atlas_start.py script for Atlas Setup are not aligned with 
> new versions
> -
>
> Key: ATLAS-2940
> URL: https://issues.apache.org/jira/browse/ATLAS-2940
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.1, 1.0.0-alpha, 0.8.2, 1.0.0, 0.8.3, 1.1.0
>Reporter: Fabio Badali
>Priority: Minor
>
> Following the steps described in 
> [https://atlas.apache.org/InstallationSteps.html], particularly:
> {quote}
> h5. Setting up Apache Atlas
> There are a few steps that setup dependencies of Apache Atlas. One such 
> example is setting up the 
> [JanusGraph|https://atlas.apache.org/JanusGraph.html] schema in the storage 
> backend of choice. In a simple single server setup, these are automatically 
> setup with default configuration when the server first accesses these 
> dependencies.
> However, there are scenarios when we may want to run setup steps explicitly 
> as one time operations. For example, in a multiple server scenario using 
> [High Availability|https://atlas.apache.org/HighAvailability.html], it is 
> preferable to run setup steps from one of the 

[jira] [Created] (ATLAS-2940) Documentation and atlas_start.py script for Atlas Setup are not aligned with new versions

[Fabio Badali (JIRA)]

Fabio Badali created ATLAS-2940:
---

 Summary: Documentation and atlas_start.py script for Atlas Setup 
are not aligned with new versions
 Key: ATLAS-2940
 URL: https://issues.apache.org/jira/browse/ATLAS-2940
 Project: Atlas
  Issue Type: Bug
Affects Versions: 1.0.0, 0.8.2, 1.0.0-alpha, 0.8.1, 0.8.3, 1.1.0
Reporter: Fabio Badali


Following the steps described in 
[https://atlas.apache.org/InstallationSteps.html], particularly:
{quote}
h5. Setting up Apache Atlas

There are a few steps that setup dependencies of Apache Atlas. One such example 
is setting up the [JanusGraph|https://atlas.apache.org/JanusGraph.html] schema 
in the storage backend of choice. In a simple single server setup, these are 
automatically setup with default configuration when the server first accesses 
these dependencies.

However, there are scenarios when we may want to run setup steps explicitly as 
one time operations. For example, in a multiple server scenario using [High 
Availability|https://atlas.apache.org/HighAvailability.html], it is preferable 
to run setup steps from one of the server instances the first time, and then 
start the services.

To run these steps one time, execute the command {{bin/atlas_start.py -setup}} 
from a single Apache Atlas server instance.

However, Apache Atlas server does take care of parallel executions of the setup 
steps. Also, running the setup steps multiple times is idempotent. Therefore, 
if one chooses to run the setup steps as part of server startup, for 
convenience, then they should enable the configuration option 
{{atlas.server.run.setup.on.start}} by defining it with the value {{true}} in 
the {{atlas-application.properties}} file.
{quote}
I got the following error:

 
{code:java}
Error: Could not find or load main class 
org.apache.atlas.web.setup.AtlasSetup{code}
It seems the class was removed after refactoring in commit 
[96fb0e[|https://github.com/apache/atlas/commit/96fb0e77a4fd979d1ff49ac6b3dd290d5bf721a9|https://github.com/apache/atlas/commit/96fb0e77a4fd979d1ff49ac6b3dd290d5bf721a9]].
 Documentation and/or script should be modified accordingly to new version.



 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2940) Documentation and atlas_start.py script for Atlas Setup are not aligned with new versions

[Fabio Badali (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fabio Badali updated ATLAS-2940:

Description: 
Following the steps described in 
[https://atlas.apache.org/InstallationSteps.html], particularly:
{quote}
h5. Setting up Apache Atlas

There are a few steps that setup dependencies of Apache Atlas. One such example 
is setting up the [JanusGraph|https://atlas.apache.org/JanusGraph.html] schema 
in the storage backend of choice. In a simple single server setup, these are 
automatically setup with default configuration when the server first accesses 
these dependencies.

However, there are scenarios when we may want to run setup steps explicitly as 
one time operations. For example, in a multiple server scenario using [High 
Availability|https://atlas.apache.org/HighAvailability.html], it is preferable 
to run setup steps from one of the server instances the first time, and then 
start the services.

To run these steps one time, execute the command {{bin/atlas_start.py -setup}} 
from a single Apache Atlas server instance.

However, Apache Atlas server does take care of parallel executions of the setup 
steps. Also, running the setup steps multiple times is idempotent. Therefore, 
if one chooses to run the setup steps as part of server startup, for 
convenience, then they should enable the configuration option 
{{atlas.server.run.setup.on.start}} by defining it with the value {{true}} in 
the {{atlas-application.properties}} file.
{quote}
I got the following error:

 
{code:java}
Error: Could not find or load main class 
org.apache.atlas.web.setup.AtlasSetup{code}
It seems the class was removed after refactoring in commit 
[96fb0e|[https://github.com/apache/atlas/commit/96fb0e77a4fd979d1ff49ac6b3dd290d5bf721a9]].
 Documentation and/or script should be modified accordingly to new version.

 

  was:
Following the steps described in 
[https://atlas.apache.org/InstallationSteps.html], particularly:
{quote}
h5. Setting up Apache Atlas

There are a few steps that setup dependencies of Apache Atlas. One such example 
is setting up the [JanusGraph|https://atlas.apache.org/JanusGraph.html] schema 
in the storage backend of choice. In a simple single server setup, these are 
automatically setup with default configuration when the server first accesses 
these dependencies.

However, there are scenarios when we may want to run setup steps explicitly as 
one time operations. For example, in a multiple server scenario using [High 
Availability|https://atlas.apache.org/HighAvailability.html], it is preferable 
to run setup steps from one of the server instances the first time, and then 
start the services.

To run these steps one time, execute the command {{bin/atlas_start.py -setup}} 
from a single Apache Atlas server instance.

However, Apache Atlas server does take care of parallel executions of the setup 
steps. Also, running the setup steps multiple times is idempotent. Therefore, 
if one chooses to run the setup steps as part of server startup, for 
convenience, then they should enable the configuration option 
{{atlas.server.run.setup.on.start}} by defining it with the value {{true}} in 
the {{atlas-application.properties}} file.
{quote}
I got the following error:

 
{code:java}
Error: Could not find or load main class 
org.apache.atlas.web.setup.AtlasSetup{code}
It seems the class was removed after refactoring in commit 
[96fb0e[|https://github.com/apache/atlas/commit/96fb0e77a4fd979d1ff49ac6b3dd290d5bf721a9|https://github.com/apache/atlas/commit/96fb0e77a4fd979d1ff49ac6b3dd290d5bf721a9]].
 Documentation and/or script should be modified accordingly to new version.



 


> Documentation and atlas_start.py script for Atlas Setup are not aligned with 
> new versions
> -
>
> Key: ATLAS-2940
> URL: https://issues.apache.org/jira/browse/ATLAS-2940
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.1, 1.0.0-alpha, 0.8.2, 1.0.0, 0.8.3, 1.1.0
>Reporter: Fabio Badali
>Priority: Minor
>
> Following the steps described in 
> [https://atlas.apache.org/InstallationSteps.html], particularly:
> {quote}
> h5. Setting up Apache Atlas
> There are a few steps that setup dependencies of Apache Atlas. One such 
> example is setting up the 
> [JanusGraph|https://atlas.apache.org/JanusGraph.html] schema in the storage 
> backend of choice. In a simple single server setup, these are automatically 
> setup with default configuration when the server first accesses these 
> dependencies.
> However, there are scenarios when we may want to run setup steps explicitly 
> as one time operations. For example, in a multiple server scenario using 
> [High Availability|https://atlas.apache.org/HighAvailability.html], it is 
> preferable to run setup steps from one of 

Re: [VOTE] Release Apache Atlas v 0.8.3 - RC1

[Srikanth Venkat]

+1 (non-binding)
Thanks to the Atlas community for the key fixes and stabilization improvements. 
Thanks Ashutosh for putting this release together!

Cheers
Srikanth 

Srikanth Venkat
Hortonworks 


On 10/29/18, 1:34 AM, "Nixon Rodrigues" 
 wrote:

Verified the rc1 bits provided.

+1 for release of 0.8.3 RC #1

Thanks,
Nixon Rodrigues

On Sat, Oct 27, 2018 at 12:47 PM Sarath Subramanian 
wrote:

> Thanks Ashutosh for Apache Atlas 0.8.3 RC #1.
>
> * Verified source checksum and validated signature
> * Build source using embedded-hbase-solr profile (build successful)
> * Ran quickstart and validated entities in atlas UI.
> * Validated basic search, advanced search and saved search feature.
> * Validated lineage filtering to hide process entities.
>
> +1
>
> Thanks,
> Sarath Subramanian
>
>
> On Fri, Oct 26, 2018 at 3:48 PM Ashutosh Mestry 
> wrote:
>
> > Apache Atlas 0.8.3 Release Candidate #1 is now available for a vote
> within
> > dev community.
> >
> > Following commits went into branch-0.8 since the last release candidate:
> > - ATLAS-2900: Exported connected bug fix.
> > - ATLAS-2934: Utility to detect and repair incorrect entity state.
> > - ATLAS-2935: Updated NPM package version and added package-lock.json.
> > - ATLAS-2927: Update lineage query for Process entities.
> > - ATLAS-2930: UI changes to handle softReference attribute elegantly.
> > - ATLAS-2931: Set isSoftReferenced method to JsonIgnore.
> > - ATLAS-2926: ZipSink out of memory error for very large entities.
> > - ATLAS-2917: Filter added for lineage to hide Process entity.
> > - ATLAS-2921: Updated import scripts exist status in case of Java error.
> > - ATLAS-2924: Used encoded property name in getEncodedProperty.
> >
> > Links to the release artifacts are given below. Please review and vote.
> >
> > The vote will be open for at least 72 hours or until necessary votes are
> > reached.
> >   [ ] +1 approve
> >   [ ] +0 no opinion
> >   [ ] -1 disapprove (and reason why)
> >
> > Ashutosh Mestry
> >
> > List of issues addressed in this release:
> >
> 
https://issues.apache.org/jira/browse/ATLAS-2924?jql=project%20%3D%20ATLAS%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%200.8.3%20ORDER%20BY%20key%20DESC
> >
> > Git tag for the release:
> > https://github.com/apache/atlas/tree/release-0.8.3-rc1
> >
> > Sources for the release:
> >
> 
https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc1/apache-atlas-0.8.3-sources.tar.gz
> >
> > Source release verification:
> > PGP Signature:
> >
> 
https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc1/apache-atlas-0.8.3-sources.tar.gz.asc
> > SHA512
> > <
> 
https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc1/apache-atlas-0.8.3-sources.tar.gz.ascSHA512
> >
> > Hash:
> >
> 
https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc1/apache-atlas-0.8.3-sources.tar.gz.sha512
> >
> > Keys to verify the signature of the release artifacts are available at:
> > https://dist.apache.org/repos/dist/dev/atlas/KEYS
> >
> >
> >
>

Re: Review Request 68363: ATLAS-2824 :- Atlas to support Trusted Knox Proxy

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/68363/
---

(Updated Oct. 29, 2018, 1:07 p.m.)


Review request for atlas, Apoorv Naik, Ashutosh Mestry, Larry McCay, Madhan 
Neethiraj, and Sarath Subramanian.


Changes
---

This patch is revised by implementing with TrustedProxyAuthenticator which 
handles the authentication, and also handles review comments.

Property changed to "atlas.authentication.method.trustedproxy" to enable 
trusted support


Bugs: ATLAS-2824
https://issues.apache.org/jira/browse/ATLAS-2824


Repository: atlas


Description
---

This patch includes code to support request from knox proxy, where the proxy is 
already known and trusted to Atlas via configuration. Atlas intercepts the 
incoming requests and if it from knox proxy. Atlas allow the knox's doAs user 
to create session in Atlas. 

Configs required:-

atlas.authentication.allow.trustedproxy :- property allow trusted proxy support
atlas.proxyuser.knox.hosts :- property to add trusted hosts
atlas.proxyuser.knox.users :- property to add trusted users
atlas.proxyuser.knox.groups :- property to add trusted groups


Diffs (updated)
-

  
webapp/src/main/java/org/apache/atlas/web/filters/AtlasTrustedProxyFilter.java 
PRE-CREATION 
  
webapp/src/main/java/org/apache/atlas/web/filters/TrustedProxyAuthenticator.java
 PRE-CREATION 
  
webapp/src/main/java/org/apache/atlas/web/security/AtlasProxyAuthenticator.java 
PRE-CREATION 
  webapp/src/main/java/org/apache/atlas/web/security/AtlasSecurityConfig.java 
24be5de20 


Diff: https://reviews.apache.org/r/68363/diff/3/

Changes: https://reviews.apache.org/r/68363/diff/2-3/


Testing
---

Tested 

* Atlas UI from  Trusted Knox Proxy with Knox SSO loginpage.
* Atlas UI from  Knox Proxy with Atlas Login.
* Atlas UI from  Knox Proxy with SSO Filter enabled at Atlas.
* Atlas UI with Atlas Login.
* Atlas api from curl with BASIS & Kerberos headers


https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/573/console

Topology Used:-



  

federation
SSOCookieProvider
true

sso.authentication.provider.url
{KNOXHOST}/gateway/knoxsso/knoxauth/login.html



identity-assertion
Default
true

  
  
  ATLAS
  {ATLAS_HOST}:21000/
  
  
  ATLAS-API
  {ATLAS_HOST}:21000
  



Thanks,

Nixon Rodrigues

[jira] [Commented] (ATLAS-2937) UI: Lineage filter- support added for depth filter

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1887#comment-1887
 ] 

ASF subversion and git services commented on ATLAS-2937:


Commit 7d27b68537a315e409c5e63d8b35de66a9087a34 in atlas's branch 
refs/heads/master from [~abhib4]
[ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=7d27b68 ]

ATLAS-2937: UI: Lineage filter- support added for depth filter

Signed-off-by: nixonrodrigues 


> UI: Lineage filter- support added for depth filter
> --
>
> Key: ATLAS-2937
> URL: https://issues.apache.org/jira/browse/ATLAS-2937
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.0.0
>Reporter: Abhishek Kadam
>Assignee: Abhishek Kadam
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: ATLAS-2937.patch
>
>
> Depth Filter added for lineage filter.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Release Apache Atlas v 0.8.3 - RC1

[Nixon Rodrigues]

Verified the rc1 bits provided.

+1 for release of 0.8.3 RC #1

Thanks,
Nixon Rodrigues

On Sat, Oct 27, 2018 at 12:47 PM Sarath Subramanian 
wrote:

> Thanks Ashutosh for Apache Atlas 0.8.3 RC #1.
>
> * Verified source checksum and validated signature
> * Build source using embedded-hbase-solr profile (build successful)
> * Ran quickstart and validated entities in atlas UI.
> * Validated basic search, advanced search and saved search feature.
> * Validated lineage filtering to hide process entities.
>
> +1
>
> Thanks,
> Sarath Subramanian
>
>
> On Fri, Oct 26, 2018 at 3:48 PM Ashutosh Mestry 
> wrote:
>
> > Apache Atlas 0.8.3 Release Candidate #1 is now available for a vote
> within
> > dev community.
> >
> > Following commits went into branch-0.8 since the last release candidate:
> > - ATLAS-2900: Exported connected bug fix.
> > - ATLAS-2934: Utility to detect and repair incorrect entity state.
> > - ATLAS-2935: Updated NPM package version and added package-lock.json.
> > - ATLAS-2927: Update lineage query for Process entities.
> > - ATLAS-2930: UI changes to handle softReference attribute elegantly.
> > - ATLAS-2931: Set isSoftReferenced method to JsonIgnore.
> > - ATLAS-2926: ZipSink out of memory error for very large entities.
> > - ATLAS-2917: Filter added for lineage to hide Process entity.
> > - ATLAS-2921: Updated import scripts exist status in case of Java error.
> > - ATLAS-2924: Used encoded property name in getEncodedProperty.
> >
> > Links to the release artifacts are given below. Please review and vote.
> >
> > The vote will be open for at least 72 hours or until necessary votes are
> > reached.
> >   [ ] +1 approve
> >   [ ] +0 no opinion
> >   [ ] -1 disapprove (and reason why)
> >
> > Ashutosh Mestry
> >
> > List of issues addressed in this release:
> >
> https://issues.apache.org/jira/browse/ATLAS-2924?jql=project%20%3D%20ATLAS%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%200.8.3%20ORDER%20BY%20key%20DESC
> >
> > Git tag for the release:
> > https://github.com/apache/atlas/tree/release-0.8.3-rc1
> >
> > Sources for the release:
> >
> https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc1/apache-atlas-0.8.3-sources.tar.gz
> >
> > Source release verification:
> > PGP Signature:
> >
> https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc1/apache-atlas-0.8.3-sources.tar.gz.asc
> > SHA512
> > <
> https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc1/apache-atlas-0.8.3-sources.tar.gz.ascSHA512
> >
> > Hash:
> >
> https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc1/apache-atlas-0.8.3-sources.tar.gz.sha512
> >
> > Keys to verify the signature of the release artifacts are available at:
> > https://dist.apache.org/repos/dist/dev/atlas/KEYS
> >
> >
> >
>

Re: Review Request 69177: Export & Import: New Features Documentation

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/69177/#review210136
---


Ship it!




Ship It!

- Nixon Rodrigues


On Oct. 26, 2018, 6:53 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69177/
> ---
> 
> (Updated Oct. 26, 2018, 6:53 p.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj, Nixon Rodrigues, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-2839
> https://issues.apache.org/jira/browse/ATLAS-2839
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Approach**
> 
> Augmented existing documentation.
> 
> Additional documentation uses markdown.
> 
> 
> Diffs
> -
> 
>   docs/pom.xml 19e916918 
>   docs/src/site/markdown/AtlasServer.md PRE-CREATION 
>   docs/src/site/markdown/ExportImportAudits.md PRE-CREATION 
>   docs/src/site/markdown/ImportEntityTransforms.md PRE-CREATION 
>   docs/src/site/markdown/Incremental-Export.md PRE-CREATION 
>   docs/src/site/markdown/ReplicatedToFromAttributes.md PRE-CREATION 
>   docs/src/site/markdown/SoftReference.md PRE-CREATION 
>   docs/src/site/resources/images/markdown/atlas-server-exp-imp-audits.png 
> PRE-CREATION 
>   docs/src/site/resources/images/markdown/atlas-server-properties.png 
> PRE-CREATION 
>   docs/src/site/twiki/Export-API.twiki 207499985 
>   docs/src/site/twiki/Export-HDFS-API.twiki 6c2006035 
>   docs/src/site/twiki/Import-Export-API.twiki 6b07b64ac 
> 
> 
> Diff: https://reviews.apache.org/r/69177/diff/2/
> 
> 
> Testing
> ---
> 
> **Tests**
> 
> Used mvn site:run to verify rendering.
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>