[jira] [Updated] (ATLAS-3583) Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and DELETE
[ https://issues.apache.org/jira/browse/ATLAS-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3583: --- Fix Version/s: 2.2.0 > Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and > DELETE > > > Key: ATLAS-3583 > URL: https://issues.apache.org/jira/browse/ATLAS-3583 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3583-V3.patch, ATLAS-3583-V8.patch > > > By using Audit Framework, capture audit entries when Type defs are created/ > updated/ deleted. > These audit entries can be seen under the "Audits" tab of Admin section. > If there are mutiple Typedefs created/ updated/ deleted in a single request, > Then only one audit entry will be recorded. > This audit entry will consist of entire information about all the included > Typedefs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3822) UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE
[ https://issues.apache.org/jira/browse/ATLAS-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3822: --- Fix Version/s: 2.2.0 > UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE > > > Key: ATLAS-3822 > URL: https://issues.apache.org/jira/browse/ATLAS-3822 > Project: Atlas > Issue Type: Bug >Reporter: Mandar Ambawane >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3822-1.patch, ATLAS-3822-2.patch, > ATLAS-3822.patch, image-2020-06-16-17-01-29-797.png, > image-2020-06-16-17-01-58-179.png > > > !image-2020-06-16-17-01-29-797.png|width=650,height=361! > > !image-2020-06-16-17-01-58-179.png|width=641,height=472! > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3822) UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE
[ https://issues.apache.org/jira/browse/ATLAS-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184965#comment-17184965 ] ASF subversion and git services commented on ATLAS-3822: Commit 74cb93041c4aecec676f42aabdee598a51b64d59 in atlas's branch refs/heads/branch-2.0 from Keval Bhatt [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=74cb930 ] ATLAS-3822:- UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE (cherry picked from commit 813bab6439d5e6be135cb178ac846056c446fd9b) > UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE > > > Key: ATLAS-3822 > URL: https://issues.apache.org/jira/browse/ATLAS-3822 > Project: Atlas > Issue Type: Bug >Reporter: Mandar Ambawane >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0 > > Attachments: ATLAS-3822-1.patch, ATLAS-3822-2.patch, > ATLAS-3822.patch, image-2020-06-16-17-01-29-797.png, > image-2020-06-16-17-01-58-179.png > > > !image-2020-06-16-17-01-29-797.png|width=650,height=361! > > !image-2020-06-16-17-01-58-179.png|width=641,height=472! > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3583) Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and DELETE
[ https://issues.apache.org/jira/browse/ATLAS-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184966#comment-17184966 ] ASF subversion and git services commented on ATLAS-3583: Commit 52bc5d7cf1bab8c6937e7c5d51e5c5bd1545cba8 in atlas's branch refs/heads/branch-2.0 from Mandar Ambawane [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=52bc5d7 ] ATLAS-3583 Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and DELETE Signed-off-by: nixonrodrigues (cherry picked from commit 892df24289d583028e74e78f7b86f6fde785e909) > Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and > DELETE > > > Key: ATLAS-3583 > URL: https://issues.apache.org/jira/browse/ATLAS-3583 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > Fix For: 3.0.0 > > Attachments: ATLAS-3583-V3.patch, ATLAS-3583-V8.patch > > > By using Audit Framework, capture audit entries when Type defs are created/ > updated/ deleted. > These audit entries can be seen under the "Audits" tab of Admin section. > If there are mutiple Typedefs created/ updated/ deleted in a single request, > Then only one audit entry will be recorded. > This audit entry will consist of entire information about all the included > Typedefs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3822) UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE
[ https://issues.apache.org/jira/browse/ATLAS-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184962#comment-17184962 ] ASF subversion and git services commented on ATLAS-3822: Commit 813bab6439d5e6be135cb178ac846056c446fd9b in atlas's branch refs/heads/master from Keval Bhatt [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=813bab6 ] ATLAS-3822:- UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE > UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE > > > Key: ATLAS-3822 > URL: https://issues.apache.org/jira/browse/ATLAS-3822 > Project: Atlas > Issue Type: Bug >Reporter: Mandar Ambawane >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0 > > Attachments: ATLAS-3822-1.patch, ATLAS-3822-2.patch, > ATLAS-3822.patch, image-2020-06-16-17-01-29-797.png, > image-2020-06-16-17-01-58-179.png > > > !image-2020-06-16-17-01-29-797.png|width=650,height=361! > > !image-2020-06-16-17-01-58-179.png|width=641,height=472! > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
Need help with upgrading dependency versions for apache atlas release-2.1.0-rc3
Hello there. We are working on the apache atlas code and started developing over https://github.com/apache/atlas/tree/release-2.1.0-rc3. Upon scanning using twistlock, we found 180+ vulnerabilities. PFA, the twistlock-image scanning results. Out of these, Jackson-databind and netty_netty-all were the most occurring ones. So, we tried upgrading the versions, but integration tests in atlas-webapp module start failing saying "org.eclipse.jetty.utils: Multi exception". We have upgraded the version of jetty-server to 9.4.x but atlas server fails to start and throws 503: service unavailable error. The same thing is happening while upgrading versions of any other dependencies in atlas module. The application breaks for any other dependency which we are trying to upgrade. For example, Hadoop-hdfs uses Jackson-databind as transitive dependency, hence I am unable to update version. I do not see any open issue on the github channel too. Have you experienced any such scenario while upgrading earlier too? Is there a way for me to move ahead to remove vulnerabilities in the current versions. Regards, Gaurav Saini The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. Humana Inc. and its subsidiaries comply with applicable Federal civil rights laws and do not discriminate on the basis of race, color, national origin, ancestry, age, disability, sex, marital status, gender, sexual orientation, gender identity, or religion. Humana Inc. and its subsidiaries do not exclude people or treat them differently because of race, color, national origin, ancestry, age, disability, sex, marital status, gender, sexual orientation, gender identity, or religion. English: ATTENTION: If you do not speak English, language assistance services, free of charge, are available to you. Call 1‐877‐320‐1235 (TTY: 711). Español (Spanish): ATENCIÓN: Si habla español, tiene a su disposición servicios gratuitos de asistencia lingüística. Llame al 1‐877‐320‐1235 (TTY: 711). 繁體中文(Chinese):注意:如果您使用繁體中文,您可以免費獲得語言援助 服務。請致電 1‐877‐320‐1235 (TTY: 711)。 Kreyòl Ayisyen (Haitian Creole): ATANSION: Si w pale Kreyòl Ayisyen, gen sèvis èd pou lang ki disponib gratis pou ou. Rele 1‐877‐320‐1235 (TTY: 711). Polski (Polish): UWAGA: Jeżeli mówisz po polsku, możesz skorzystać z bezpłatnej pomocy językowej. Zadzwoń pod numer 1‐877‐320‐1235 (TTY: 711). 한국어 (Korean): 주의: 한국어를 사용하시는 경우, 언어 지원 서비스를 무료로 이용하실 수 있습니다. 1‐877‐320‐1235 (TTY: 711)번으로 전화해 주십시오.
Re: Review Request 72729: ATLAS-3910: Use KafkaZkClient instead of ZkUtils
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72729/#review221707 --- Ship it! Ship It! - Ramesh Mani On Aug. 11, 2020, 7:42 a.m., Viktor Somogyi-Vass wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/72729/ > --- > > (Updated Aug. 11, 2020, 7:42 a.m.) > > > Review request for atlas and Madhan Neethiraj. > > > Repository: atlas > > > Description > --- > > ATLAS-3910: Use KafkaZkClient instead of ZkUtils > > > Diffs > - > > > addons/kafka-bridge/src/main/java/org/apache/atlas/kafka/bridge/KafkaBridge.java > 40b1fee71e57175cd7ddf8a3696ef147282295c2 > > addons/kafka-bridge/src/test/java/org/apache/atlas/kafka/bridge/KafkaBridgeTest.java > c8cc85cda1f62b2d1a0a49c61abf06d9beb6fdb7 > notification/src/main/java/org/apache/atlas/hook/AtlasTopicCreator.java > c69574103e360fcfb7dfb525bb06043a1fd647c3 > notification/src/test/java/org/apache/atlas/hook/AtlasTopicCreatorTest.java > 293784770502299875177bd4a4a9c4b32c6b5a9a > > > Diff: https://reviews.apache.org/r/72729/diff/2/ > > > Testing > --- > > > Thanks, > > Viktor Somogyi-Vass > >
[jira] [Commented] (ATLAS-3926) Atlas1.2 with Kerberos problem
[ https://issues.apache.org/jira/browse/ATLAS-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184061#comment-17184061 ] yuyu commented on ATLAS-3926: - First of all, thank you for your suggestions, but it seems that it will not solve my problem.Please pay attention to the part of the configuration file I gave above. I have configured the above attributes you mentioned, but Import Hive MetaData still has Kerberos problems.[~nixon] > Atlas1.2 with Kerberos problem > -- > > Key: ATLAS-3926 > URL: https://issues.apache.org/jira/browse/ATLAS-3926 > Project: Atlas > Issue Type: Bug > Components: falcon-integration, hive-integration >Affects Versions: 1.2.0 >Reporter: yuyu >Priority: Major > Fix For: 1.2.0 > > Attachments: image-2020-08-25-16-29-12-906.png, > image-2020-08-25-16-29-29-667.png, image-2020-08-25-16-30-34-221.png, > image-2020-08-25-16-31-23-439.png, image-2020-08-25-16-31-28-330.png, > image-2020-08-25-16-34-41-642.png, image-2020-08-25-16-35-09-836.png, > image-2020-08-25-16-38-45-645.png > > > Hello, everyone. Recently, I encountered a problem with Kerberos when > deploying atlas.I tried to deploy atlas service on my CDH cluster with CDH > version 5.16 and Kerberos service deployed.My installation method is Atlas > 1.2 integrated CDH HBase and external 5.5.1 Solr > When I start the atlas service, I can successfully access the atlas web page > through my computer： > !image-2020-08-25-16-29-29-667.png! > But when I tried to import hive metadata information, something went wrong，as > shown in the figure below: > !image-2020-08-25-16-30-34-221.png! > !image-2020-08-25-16-38-45-645.png! > !image-2020-08-25-16-31-28-330.png! > It seems to indicate that I don't have a valid Kerberos principal? > Here is part of my atlas configuration file atlas-application.properties： > !image-2020-08-25-16-34-41-642.png! > !image-2020-08-25-16-35-09-836.png! > Can anyone tell me what the problem is,thanks. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3583) Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and DELETE
[ https://issues.apache.org/jira/browse/ATLAS-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184063#comment-17184063 ] ASF subversion and git services commented on ATLAS-3583: Commit 892df24289d583028e74e78f7b86f6fde785e909 in atlas's branch refs/heads/master from Mandar Ambawane [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=892df24 ] ATLAS-3583 Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and DELETE Signed-off-by: nixonrodrigues > Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and > DELETE > > > Key: ATLAS-3583 > URL: https://issues.apache.org/jira/browse/ATLAS-3583 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > Fix For: 3.0.0 > > Attachments: ATLAS-3583-V3.patch, ATLAS-3583-V8.patch > > > By using Audit Framework, capture audit entries when Type defs are created/ > updated/ deleted. > These audit entries can be seen under the "Audits" tab of Admin section. > If there are mutiple Typedefs created/ updated/ deleted in a single request, > Then only one audit entry will be recorded. > This audit entry will consist of entire information about all the included > Typedefs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3920) Harmonize joda-time to version 2.10.latest
[ https://issues.apache.org/jira/browse/ATLAS-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184062#comment-17184062 ] ASF subversion and git services commented on ATLAS-3920: Commit 41e1039bd66829683e9b24f10186bde53a83d7ad in atlas's branch refs/heads/master from mayanknj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=41e1039 ] ATLAS-3920 : Update joda-time to version 2.10.latest. Signed-off-by: nixonrodrigues > Harmonize joda-time to version 2.10.latest > -- > > Key: ATLAS-3920 > URL: https://issues.apache.org/jira/browse/ATLAS-3920 > Project: Atlas > Issue Type: Bug >Reporter: Mayank Jain >Priority: Major > > Atlas currently uses outdated joda-time versions, which can cause issues. To > avoid issue we need to update it to the latest version of joda-time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (ATLAS-3926) Atlas1.2 with Kerberos problem
[ https://issues.apache.org/jira/browse/ATLAS-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184028#comment-17184028 ] Nixon Rodrigues edited comment on ATLAS-3926 at 8/25/20, 1:31 PM: -- For kerberos authentication properties with prefix "atlas.authentication.method.kerberos" are used for configuring the kerberos filter. I see them as some commented. please ensure following properties are set and kinit is done before running import-hive.sh atlas.authentication.method.kerberos=true atlas.authentication.method.kerberos.keytab=/keytab/atlas.keytab atlas.authentication.method.kerberos.principal=atlas/_h...@example.com atlas.authentication.method.kerberos.name.rules= atlas.authentication.keytab=/keytab/atlas.keytab atlas.authentication.principal=atlas/_h...@example.com was (Author: nixonrodrigues): For kerberos authentication properties with prefix "atlas.authentication.method.kerberos" are used for configuring the kerberos filter. I see them as some commented. please ensure following properties are set and kinit is done before running import-hive.sh atlas.authentication.method.kerberos=true atlas.authentication.method.kerberos.keytab=/keytab/atlas.keytab atlas.authentication.method.kerberos.principal=atlas/_h...@example.com atlas.authentication.method.kerberos.name.rules= atlas.authentication.keytab=/keytab/atlas.keytab atlas.authentication.principal=atlas/_h...@root.hwx.site > Atlas1.2 with Kerberos problem > -- > > Key: ATLAS-3926 > URL: https://issues.apache.org/jira/browse/ATLAS-3926 > Project: Atlas > Issue Type: Bug > Components: falcon-integration, hive-integration >Affects Versions: 1.2.0 >Reporter: yuyu >Priority: Major > Fix For: 1.2.0 > > Attachments: image-2020-08-25-16-29-12-906.png, > image-2020-08-25-16-29-29-667.png, image-2020-08-25-16-30-34-221.png, > image-2020-08-25-16-31-23-439.png, image-2020-08-25-16-31-28-330.png, > image-2020-08-25-16-34-41-642.png, image-2020-08-25-16-35-09-836.png, > image-2020-08-25-16-38-45-645.png > > > Hello, everyone. Recently, I encountered a problem with Kerberos when > deploying atlas.I tried to deploy atlas service on my CDH cluster with CDH > version 5.16 and Kerberos service deployed.My installation method is Atlas > 1.2 integrated CDH HBase and external 5.5.1 Solr > When I start the atlas service, I can successfully access the atlas web page > through my computer： > !image-2020-08-25-16-29-29-667.png! > But when I tried to import hive metadata information, something went wrong，as > shown in the figure below: > !image-2020-08-25-16-30-34-221.png! > !image-2020-08-25-16-38-45-645.png! > !image-2020-08-25-16-31-28-330.png! > It seems to indicate that I don't have a valid Kerberos principal? > Here is part of my atlas configuration file atlas-application.properties： > !image-2020-08-25-16-34-41-642.png! > !image-2020-08-25-16-35-09-836.png! > Can anyone tell me what the problem is,thanks. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3926) Atlas1.2 with Kerberos problem
[ https://issues.apache.org/jira/browse/ATLAS-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184028#comment-17184028 ] Nixon Rodrigues commented on ATLAS-3926: For kerberos authentication properties with prefix "atlas.authentication.method.kerberos" are used for configuring the kerberos filter. I see them as some commented. please ensure following properties are set and kinit is done before running import-hive.sh atlas.authentication.method.kerberos=true atlas.authentication.method.kerberos.keytab=/keytab/atlas.keytab atlas.authentication.method.kerberos.principal=atlas/_h...@example.com atlas.authentication.method.kerberos.name.rules= atlas.authentication.keytab=/keytab/atlas.keytab atlas.authentication.principal=atlas/_h...@root.hwx.site > Atlas1.2 with Kerberos problem > -- > > Key: ATLAS-3926 > URL: https://issues.apache.org/jira/browse/ATLAS-3926 > Project: Atlas > Issue Type: Bug > Components: falcon-integration, hive-integration >Affects Versions: 1.2.0 >Reporter: yuyu >Priority: Major > Fix For: 1.2.0 > > Attachments: image-2020-08-25-16-29-12-906.png, > image-2020-08-25-16-29-29-667.png, image-2020-08-25-16-30-34-221.png, > image-2020-08-25-16-31-23-439.png, image-2020-08-25-16-31-28-330.png, > image-2020-08-25-16-34-41-642.png, image-2020-08-25-16-35-09-836.png, > image-2020-08-25-16-38-45-645.png > > > Hello, everyone. Recently, I encountered a problem with Kerberos when > deploying atlas.I tried to deploy atlas service on my CDH cluster with CDH > version 5.16 and Kerberos service deployed.My installation method is Atlas > 1.2 integrated CDH HBase and external 5.5.1 Solr > When I start the atlas service, I can successfully access the atlas web page > through my computer： > !image-2020-08-25-16-29-29-667.png! > But when I tried to import hive metadata information, something went wrong，as > shown in the figure below: > !image-2020-08-25-16-30-34-221.png! > !image-2020-08-25-16-38-45-645.png! > !image-2020-08-25-16-31-28-330.png! > It seems to indicate that I don't have a valid Kerberos principal? > Here is part of my atlas configuration file atlas-application.properties： > !image-2020-08-25-16-34-41-642.png! > !image-2020-08-25-16-35-09-836.png! > Can anyone tell me what the problem is,thanks. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3929) Kafka hook for Atlas to capture production/consumption
[ https://issues.apache.org/jira/browse/ATLAS-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Jaheruddin updated ATLAS-3929: - Summary: Kafka hook for Atlas to capture production/consumption (was: Kafka hook for Atlas) > Kafka hook for Atlas to capture production/consumption > -- > > Key: ATLAS-3929 > URL: https://issues.apache.org/jira/browse/ATLAS-3929 > Project: Atlas > Issue Type: Improvement > Components: kafka-integration >Reporter: Dennis Jaheruddin >Priority: Major > > Currently we already have hooks for many engines (such as Spark, Nifi, > Flink). We also have a hook into the classical storage (HDFS). However, with > streaming becoming more and more dominant, we should also get a hook into the > streaming storage: Kafka. > Currently producers and consumers need to explicitly take atlas into account, > but for stronger governance and auditability, it should be possible to > capture every interaction with Kafka, regardless of how consumption or > production is done. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3929) Kafka hook for Atlas
Dennis Jaheruddin created ATLAS-3929: Summary: Kafka hook for Atlas Key: ATLAS-3929 URL: https://issues.apache.org/jira/browse/ATLAS-3929 Project: Atlas Issue Type: Improvement Components: kafka-integration Reporter: Dennis Jaheruddin Currently we already have hooks for many engines (such as Spark, Nifi, Flink). We also have a hook into the classical storage (HDFS). However, with streaming becoming more and more dominant, we should also get a hook into the streaming storage: Kafka. Currently producers and consumers need to explicitly take atlas into account, but for stronger governance and auditability, it should be possible to capture every interaction with Kafka, regardless of how consumption or production is done. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3927) 403 unauthorized to access atlas webui using keycloak authentication method
[ https://issues.apache.org/jira/browse/ATLAS-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hisham Ismail resolved ATLAS-3927. -- Fix Version/s: 2.1.0 Resolution: Duplicate > 403 unauthorized to access atlas webui using keycloak authentication method > --- > > Key: ATLAS-3927 > URL: https://issues.apache.org/jira/browse/ATLAS-3927 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 > Environment: kubernetes >Reporter: Hisham Ismail >Priority: Major > Fix For: 2.1.0 > > > After installing keycloak, following the instructions on the readme to > include a realm, users and a client with /* redirect uri. Once i access the > webui, i get the redirect to keycloak, do the login which was successful. > However, i get error 403 from atlas side. > > also, i get an error from within the application.logs of atlas: > 2020-08-25 09:44:21,479 ERROR - [pool-2-thread-9:] ~ failed to turn code into > token (OAuthRequestAuthenticator:345)2020-08-25 09:44:21,479 ERROR - > [pool-2-thread-9:] ~ failed to turn code into token > (OAuthRequestAuthenticator:345)javax.net.ssl.SSLHandshakeException: PKIX path > building failed: sun.security.provider.certpath.SunCertPathBuilderException: > unable to find valid certification path to requested target at > java.base/sun.security.ssl.Alert.createSSLException(Alert.java:131) at > java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:326) > at > java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:269) > at > java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:264) > at > java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.checkServerCerts(CertificateMessage.java:645) > at > java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.onCertificate(CertificateMessage.java:464) > at > java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.consume(CertificateMessage.java:360) > at java.base/sun.security.ssl.SSLHandshake.consume(SSLHandshake.java:392) at > java.base/sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:444) > at > java.base/sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:422) > at > java.base/sun.security.ssl.TransportContext.dispatch(TransportContext.java:183) > at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:164) at > java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1144) at > java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1055) > at > java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:395) > at > org.apache.http.conn.ssl.SSLSocketFactory.createLayeredSocket(SSLSocketFactory.java:573) > at > org.keycloak.adapters.SniSSLSocketFactory.createLayeredSocket(SniSSLSocketFactory.java:114) > at > org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:557) > at > org.keycloak.adapters.SniSSLSocketFactory.connectSocket(SniSSLSocketFactory.java:109) > at > org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:414) > at > org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180) > at > org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144) > at > org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:134) > at > org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:610) > at > org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:445) > at > org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:835) > at > org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) > at > org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108) > at > org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56) > at > org.keycloak.adapters.ServerRequest.invokeAccessCodeToToken(ServerRequest.java:111) > at > org.keycloak.adapters.OAuthRequestAuthenticator.resolveCode(OAuthRequestAuthenticator.java:335) > at > org.keycloak.adapters.OAuthRequestAuthenticator.authenticate(OAuthRequestAuthenticator.java:280) > at > org.keycloak.adapters.RequestAuthenticator.authenticate(RequestAuthenticator.java:139) > at > org.keycloak.adapters.springsecurity.filter.KeycloakAuthenticationProcessingFilter.attemptAuthentication(KeycloakAuthenticationProcessingFilter.java:150) > at > org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:21
[jira] [Created] (ATLAS-3928) 403 unauthorized to access atlas webui using keycloak authentication method
Hisham Ismail created ATLAS-3928: Summary: 403 unauthorized to access atlas webui using keycloak authentication method Key: ATLAS-3928 URL: https://issues.apache.org/jira/browse/ATLAS-3928 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 2.1.0 Environment: Kubernetes Reporter: Hisham Ismail After installing keycloak, creating a realm, user and a client for atlas application and followed what was advised in the readme of atlas regarding keycloak. I was able to successfully get the redirect to keycloak, was able to also successfully login however, atlas showed 403 unauthorized with errors in the application.log: 2020-08-25 09:44:21,479 ERROR - [pool-2-thread-9:] ~ failed to turn code into token (OAuthRequestAuthenticator:345)2020-08-25 09:44:21,479 ERROR - [pool-2-thread-9:] ~ failed to turn code into token (OAuthRequestAuthenticator:345)javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:131) at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:326) at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:269) at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:264) at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.checkServerCerts(CertificateMessage.java:645) at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.onCertificate(CertificateMessage.java:464) at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.consume(CertificateMessage.java:360) at java.base/sun.security.ssl.SSLHandshake.consume(SSLHandshake.java:392) at java.base/sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:444) at java.base/sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:422) at java.base/sun.security.ssl.TransportContext.dispatch(TransportContext.java:183) at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:164) at java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1144) at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1055) at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:395) at org.apache.http.conn.ssl.SSLSocketFactory.createLayeredSocket(SSLSocketFactory.java:573) at org.keycloak.adapters.SniSSLSocketFactory.createLayeredSocket(SniSSLSocketFactory.java:114) at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:557) at org.keycloak.adapters.SniSSLSocketFactory.connectSocket(SniSSLSocketFactory.java:109) at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:414) at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180) at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144) at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:134) at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:610) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:445) at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:835) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56) at org.keycloak.adapters.ServerRequest.invokeAccessCodeToToken(ServerRequest.java:111) at org.keycloak.adapters.OAuthRequestAuthenticator.resolveCode(OAuthRequestAuthenticator.java:335) at org.keycloak.adapters.OAuthRequestAuthenticator.authenticate(OAuthRequestAuthenticator.java:280) at org.keycloak.adapters.RequestAuthenticator.authenticate(RequestAuthenticator.java:139) at org.keycloak.adapters.springsecurity.filter.KeycloakAuthenticationProcessingFilter.attemptAuthentication(KeycloakAuthenticationProcessingFilter.java:150) at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:212) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331) at org.apache.atlas.web.filters.AtlasKnoxSSOAuthenticationFilter.doFilter(AtlasKnoxSSOAuthenticationFilter.java:142) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331) at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthentica
[jira] [Created] (ATLAS-3927) 403 unauthorized to access atlas webui using keycloak authentication method
Hisham Ismail created ATLAS-3927: Summary: 403 unauthorized to access atlas webui using keycloak authentication method Key: ATLAS-3927 URL: https://issues.apache.org/jira/browse/ATLAS-3927 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 2.1.0 Environment: kubernetes Reporter: Hisham Ismail After installing keycloak, following the instructions on the readme to include a realm, users and a client with /* redirect uri. Once i access the webui, i get the redirect to keycloak, do the login which was successful. However, i get error 403 from atlas side. also, i get an error from within the application.logs of atlas: 2020-08-25 09:44:21,479 ERROR - [pool-2-thread-9:] ~ failed to turn code into token (OAuthRequestAuthenticator:345)2020-08-25 09:44:21,479 ERROR - [pool-2-thread-9:] ~ failed to turn code into token (OAuthRequestAuthenticator:345)javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:131) at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:326) at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:269) at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:264) at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.checkServerCerts(CertificateMessage.java:645) at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.onCertificate(CertificateMessage.java:464) at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.consume(CertificateMessage.java:360) at java.base/sun.security.ssl.SSLHandshake.consume(SSLHandshake.java:392) at java.base/sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:444) at java.base/sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:422) at java.base/sun.security.ssl.TransportContext.dispatch(TransportContext.java:183) at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:164) at java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1144) at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1055) at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:395) at org.apache.http.conn.ssl.SSLSocketFactory.createLayeredSocket(SSLSocketFactory.java:573) at org.keycloak.adapters.SniSSLSocketFactory.createLayeredSocket(SniSSLSocketFactory.java:114) at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:557) at org.keycloak.adapters.SniSSLSocketFactory.connectSocket(SniSSLSocketFactory.java:109) at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:414) at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180) at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144) at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:134) at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:610) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:445) at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:835) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56) at org.keycloak.adapters.ServerRequest.invokeAccessCodeToToken(ServerRequest.java:111) at org.keycloak.adapters.OAuthRequestAuthenticator.resolveCode(OAuthRequestAuthenticator.java:335) at org.keycloak.adapters.OAuthRequestAuthenticator.authenticate(OAuthRequestAuthenticator.java:280) at org.keycloak.adapters.RequestAuthenticator.authenticate(RequestAuthenticator.java:139) at org.keycloak.adapters.springsecurity.filter.KeycloakAuthenticationProcessingFilter.attemptAuthentication(KeycloakAuthenticationProcessingFilter.java:150) at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:212) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331) at org.apache.atlas.web.filters.AtlasKnoxSSOAuthenticationFilter.doFilter(AtlasKnoxSSOAuthenticationFilter.java:142) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331) at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthentic
[jira] [Created] (ATLAS-3926) Atlas1.2 with Kerberos problem
yuyu created ATLAS-3926: --- Summary: Atlas1.2 with Kerberos problem Key: ATLAS-3926 URL: https://issues.apache.org/jira/browse/ATLAS-3926 Project: Atlas Issue Type: Bug Components: falcon-integration, hive-integration Affects Versions: 1.2.0 Reporter: yuyu Fix For: 1.2.0 Attachments: image-2020-08-25-16-29-12-906.png, image-2020-08-25-16-29-29-667.png, image-2020-08-25-16-30-34-221.png, image-2020-08-25-16-31-23-439.png, image-2020-08-25-16-31-28-330.png, image-2020-08-25-16-34-41-642.png, image-2020-08-25-16-35-09-836.png, image-2020-08-25-16-38-45-645.png Hello, everyone. Recently, I encountered a problem with Kerberos when deploying atlas.I tried to deploy atlas service on my CDH cluster with CDH version 5.16 and Kerberos service deployed.My installation method is Atlas 1.2 integrated CDH HBase and external 5.5.1 Solr When I start the atlas service, I can successfully access the atlas web page through my computer： !image-2020-08-25-16-29-29-667.png! But when I tried to import hive metadata information, something went wrong，as shown in the figure below: !image-2020-08-25-16-30-34-221.png! !image-2020-08-25-16-38-45-645.png! !image-2020-08-25-16-31-28-330.png! It seems to indicate that I don't have a valid Kerberos principal? Here is part of my atlas configuration file atlas-application.properties： !image-2020-08-25-16-34-41-642.png! !image-2020-08-25-16-35-09-836.png! Can anyone tell me what the problem is,thanks. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3925) UI: Properties with value 0 or false are displayed as N/A for
[ https://issues.apache.org/jira/browse/ATLAS-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3925: --- Fix Version/s: 2.2.0 3.0.0 > UI: Properties with value 0 or false are displayed as N/A for > -- > > Key: ATLAS-3925 > URL: https://issues.apache.org/jira/browse/ATLAS-3925 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: image-2020-08-25-12-53-09-294.png, > image-2020-08-25-12-53-45-935.png > > > Check the screenshot: > *partitionCount* is displayed as N/A instead of *0* > > +API response:+ > > *!image-2020-08-25-12-53-09-294.png|width=440,height=151!* > +UI:+ > > *!image-2020-08-25-12-53-45-935.png|width=427,height=214!* > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3925) UI: Properties with value 0 or false are displayed as N/A for
Keval Bhatt created ATLAS-3925: -- Summary: UI: Properties with value 0 or false are displayed as N/A for Key: ATLAS-3925 URL: https://issues.apache.org/jira/browse/ATLAS-3925 Project: Atlas Issue Type: Bug Reporter: Keval Bhatt Assignee: Keval Bhatt Attachments: image-2020-08-25-12-53-09-294.png, image-2020-08-25-12-53-45-935.png Check the screenshot: *partitionCount* is displayed as N/A instead of *0* +API response:+ *!image-2020-08-25-12-53-09-294.png|width=440,height=151!* +UI:+ *!image-2020-08-25-12-53-45-935.png|width=427,height=214!* -- This message was sent by Atlassian Jira (v8.3.4#803005)
