At this point, you need to determine what is going on with your namenode/webhdfs.
Try hitting webhdfs directly instead of going through Knox. That should lead you to changes for your topology or something. The bottom line is that LDAPS is working for you now and you just need to triage your HDFS related configuration. On Sat, Aug 22, 2015 at 10:50 AM, Aneela Saleem <[email protected]> wrote: > Any response Kevin? > > Regards, > Aneela Saleem > On Aug 22, 2015 2:14 AM, "Aneela Saleem" <[email protected]> wrote: > >> Following is the response body: >> >> HTTP/1.1 302 Found >> Location: https://localhost/gateway/cluster1/webhdfs/v1/?op=LISTSTATUS >> Content-Length: 0 >> Server: Jetty(8.1.14.v20131031) >> >> >> And no i'm just using single node cluster for testing purpose. My HDFS is >> not in HA mode. >> >> On Sat, Aug 22, 2015 at 1:50 AM, Kevin Minder < >> [email protected]> wrote: >> >>> The last line in the audit log below indicates that the NameNode is >>> returning a 302 to Knox. The implication here is that your authentication >>> at Knox to LDAP via LDAPS was successful. >>> >>> Is your HDFS in HA mode? >>> >>> Can you provide the response body returned by the curl command? >>> >>> From: Aneela Saleem >>> Reply-To: "[email protected]" >>> Date: Friday, August 21, 2015 at 4:35 PM >>> To: "[email protected]" >>> Subject: Re: Working with ldaps ( LDAP over SSL ) >>> >>> gateway-audit.log has following content: >>> >>> 15/08/22 01:18:20 |||audit|||||redeploy|topology|sandbox|unavailable| >>> 15/08/22 01:18:20 |||audit|||||redeploy|topology|admin|unavailable| >>> 15/08/22 01:18:20 |||audit|||||deploy|topology|cluster1|unavailable| >>> 15/08/22 01:18:29 >>> ||1202b16f-be70-4cfe-aded-76e5f52dcc8e|audit|WEBHDFS||||access|uri|/gateway/cluster1/webhdfs/v1/?op=LISTSTATUS|unavailable| >>> 15/08/22 01:18:29 >>> ||1202b16f-be70-4cfe-aded-76e5f52dcc8e|audit|WEBHDFS||||access|uri|/gateway/cluster1/webhdfs/v1/?op=LISTSTATUS|success|Response >>> status: 302 >>> >>> >>> and attache is the gateway.log file. I have not made HDFS work with >>> ldaps yet, im having so much trouble in this. >>> >>> >>> >>> On Sat, Aug 22, 2015 at 1:26 AM, Kevin Minder < >>> [email protected]> wrote: >>> >>>> Can you provide your gateway.log and gateway-audit.log for a request >>>> that returns a 302. From your topology file I’m assuming that this is a >>>> WebHdfs request since the other service definitions seem invalid. Is HDFS >>>> is safe or standby mode? To my knowledge Knox doesn’t return any 302 >>>> status codes so I’m assuming this is coming from the NameNode. >>>> >>>> From: Aneela Saleem >>>> Reply-To: "[email protected]" >>>> Date: Friday, August 21, 2015 at 3:43 PM >>>> To: "[email protected]" >>>> Subject: Working with ldaps ( LDAP over SSL ) >>>> >>>> Hi all, >>>> I have setup ldaps and want to make it work with knox. I have changed >>>> topology file accordingly but when i run cURL command i get http:/1.1 >>>> 302 Found error. Please look at the topology file and do tell me what >>>> i'm missing >>>> >>> >>> >>
