[jira] [Updated] (ATLAS-1906) Atlas client should support setting hadoop-jwt token in header
[ https://issues.apache.org/jira/browse/ATLAS-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1906: --- Fix Version/s: 0.8.1-incubating 0.9-incubating > Atlas client should support setting hadoop-jwt token in header > -- > > Key: ATLAS-1906 > URL: https://issues.apache.org/jira/browse/ATLAS-1906 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Hemanth Yamijala >Assignee: Nixon Rodrigues > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: > 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch, > ATLAS-1906.1.patch, ATLAS-1906.2.patch, ATLAS-1906.3.patch, ATLAS-1906.patch > > > In ATLAS-1767, support was added to make the Atlas REST API calls take a > hadoop-jwt token coming from Knox SSO and authenticate the user. > This works perfectly when using a vanilla HTTP client. We have found it > convenient to use the Atlas client Java binding for our work. However, it > does not seem to support setting the hadoop-jwt token. Hence, we don't seem > to be able to use it with a Knox SSO enabled Atlas server for API calls. > Could this support be added please? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1906) Atlas client should support setting hadoop-jwt token in header
[ https://issues.apache.org/jira/browse/ATLAS-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1906: --- Attachment: ATLAS-1906.3.patch > Atlas client should support setting hadoop-jwt token in header > -- > > Key: ATLAS-1906 > URL: https://issues.apache.org/jira/browse/ATLAS-1906 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Hemanth Yamijala >Assignee: Apoorv Naik > Attachments: > 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch, > ATLAS-1906.1.patch, ATLAS-1906.2.patch, ATLAS-1906.3.patch, ATLAS-1906.patch > > > In ATLAS-1767, support was added to make the Atlas REST API calls take a > hadoop-jwt token coming from Knox SSO and authenticate the user. > This works perfectly when using a vanilla HTTP client. We have found it > convenient to use the Atlas client Java binding for our work. However, it > does not seem to support setting the hadoop-jwt token. Hence, we don't seem > to be able to use it with a Knox SSO enabled Atlas server for API calls. > Could this support be added please? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1906) Atlas client should support setting hadoop-jwt token in header
[ https://issues.apache.org/jira/browse/ATLAS-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1906: --- Attachment: ATLAS-1906.2.patch > Atlas client should support setting hadoop-jwt token in header > -- > > Key: ATLAS-1906 > URL: https://issues.apache.org/jira/browse/ATLAS-1906 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Hemanth Yamijala >Assignee: Apoorv Naik > Attachments: > 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch, > ATLAS-1906.1.patch, ATLAS-1906.2.patch, ATLAS-1906.patch > > > In ATLAS-1767, support was added to make the Atlas REST API calls take a > hadoop-jwt token coming from Knox SSO and authenticate the user. > This works perfectly when using a vanilla HTTP client. We have found it > convenient to use the Atlas client Java binding for our work. However, it > does not seem to support setting the hadoop-jwt token. Hence, we don't seem > to be able to use it with a Knox SSO enabled Atlas server for API calls. > Could this support be added please? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1906) Atlas client should support setting hadoop-jwt token in header
[ https://issues.apache.org/jira/browse/ATLAS-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1906: --- Attachment: ATLAS-1906.1.patch This patch ATLAS-1906.1.patch includes setHadoopJWTCookie method in AtlasBaseClient, this method can be used to update the fresh hadoopJWT cookie when old cookie is expired instead creating the new object of AtlasClient. > Atlas client should support setting hadoop-jwt token in header > -- > > Key: ATLAS-1906 > URL: https://issues.apache.org/jira/browse/ATLAS-1906 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Hemanth Yamijala >Assignee: Apoorv Naik > Attachments: > 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch, > ATLAS-1906.1.patch, ATLAS-1906.patch > > > In ATLAS-1767, support was added to make the Atlas REST API calls take a > hadoop-jwt token coming from Knox SSO and authenticate the user. > This works perfectly when using a vanilla HTTP client. We have found it > convenient to use the Atlas client Java binding for our work. However, it > does not seem to support setting the hadoop-jwt token. Hence, we don't seem > to be able to use it with a Knox SSO enabled Atlas server for API calls. > Could this support be added please? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1906) Atlas client should support setting hadoop-jwt token in header
[ https://issues.apache.org/jira/browse/ATLAS-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1906: --- Attachment: ATLAS-1906.patch > Atlas client should support setting hadoop-jwt token in header > -- > > Key: ATLAS-1906 > URL: https://issues.apache.org/jira/browse/ATLAS-1906 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Hemanth Yamijala >Assignee: Apoorv Naik > Attachments: > 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch, > ATLAS-1906.patch > > > In ATLAS-1767, support was added to make the Atlas REST API calls take a > hadoop-jwt token coming from Knox SSO and authenticate the user. > This works perfectly when using a vanilla HTTP client. We have found it > convenient to use the Atlas client Java binding for our work. However, it > does not seem to support setting the hadoop-jwt token. Hence, we don't seem > to be able to use it with a Knox SSO enabled Atlas server for API calls. > Could this support be added please? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1906) Atlas client should support setting hadoop-jwt token in header
[ https://issues.apache.org/jira/browse/ATLAS-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-1906: --- Attachment: 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch AtlasClient can now set custom header(s) > Atlas client should support setting hadoop-jwt token in header > -- > > Key: ATLAS-1906 > URL: https://issues.apache.org/jira/browse/ATLAS-1906 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Hemanth Yamijala >Assignee: Apoorv Naik > Attachments: > 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch > > > In ATLAS-1767, support was added to make the Atlas REST API calls take a > hadoop-jwt token coming from Knox SSO and authenticate the user. > This works perfectly when using a vanilla HTTP client. We have found it > convenient to use the Atlas client Java binding for our work. However, it > does not seem to support setting the hadoop-jwt token. Hence, we don't seem > to be able to use it with a Knox SSO enabled Atlas server for API calls. > Could this support be added please? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
