ContributionsMost RecentMost LikesSolutionsRe: SSO login issues Hi @Asad.Humayun , In my case the file was different between first moment when it ws uploaded and second moment when i’ve updated the metadata for some orgs. There were some additional claims on the metadata. Re: SSO login issues Hi @Asad.Humayun, This looks like an SSO integration error. Check internally with your identity and management team if the “SnapLogic SAML” details for your snaplogic apps were configured ok. Re: KERBEROS issues - HDFS cluster I’ve contacted Snaplogic support. Not even they are not able to fix the issue. 😀 KERBEROS issues - HDFS cluster Hi , We’ve implemented Kerberos in our hadoop cluster, but we are having issues with our pipelines. We are getting this error 🙂 "Reason: org.apache.hadoop.security.AccessControlException: SIMPLE authentication is not enabled. Available:[TOKEN, KERBEROS] " “Caused by: java.util.concurrent.ExecutionException: org.apache.hadoop.security.AccessControlException: SIMPLE authentication is not enabled. Available:[TOKEN, KERBEROS] at java.util.concurrent.FutureTask.report(FutureTask.java:122) at java.util.concurrent.FutureTask.get(FutureTask.java:206) at com.snaplogic.snap.api.binary.SimpleReader.doRead(SimpleReader.java:332) … 30 more Caused by: org.apache.hadoop.security.AccessControlException: SIMPLE authentication is not enabled. Available:[TOKEN, KERBEROS] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62” All was configured correctly , keytabs are ok, i’m able to do a kinit from any groundplex nodes, time on KDC servers and kerberos clients is synced. Pipelines worked ok for some while, but we saw that after we restarted jcc process on the groundplex nodes pipelines started to fail. JCE extension was installed as per https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/2015960/How+to+Configure+a+Groundplex+for+CDH+with+Kerberos+Authentication Any ideas ? Thank you, Petrica Re: Unable to reach Snaplex neighbor - https://hostname:8081 Has anyone any ideas ? Thanks, Unable to reach Snaplex neighbor - https://hostname:8081 Hello, Very often i see this error (“Unable to reach Snaplex neighbor - https://hostname:8081”) on the Snaplogic Control Pane, on Dashboard on the groundplex servers. Port 8081 is open between nodes and there are no fw issues. The problem is that when i’m accessing directly the node URL, https://hostname:8081 , i see that all the Neighbors are green and communicates with all of them. Why is this alert showing on the Snaplogic Dashboard ? Is there any parameter ( heartbeat config or something similar) that i can change on my nodes ? Thank you, Petrica Re: How can i setup logrotate for jcc_output.log? Hi Akidave, Thank you for your help on this. This worked like a charm. 🙂 Best regards, Petrica Re: SSO login issues Issue solved. Was a problem with the metadata Idm file. How can i setup logrotate for jcc_output.log? Hi all, How can i setup logrotate for jcc_output.log ? in this moment this log is very big on all snaplogic servers ( 60 GB ) and i need to know how can i configure logrotate for these logs. Best regards, Petrica SolvedRe: SSO login issues I’m using same metadata on all organizations. What i’ve done is that i’ve just changed metadata on one org, but afterwards i’ve reverted back , but error is still there. Is like something is stuck on the backend of the snaplogic portal and is still seeing that organization with different IdP metadata.