Nice !
On Fri, Aug 3, 2018 at 1:17 PM Dhruv Goyal <777.dh...@gmail.com> wrote:
> Hi Sandeep,
>
> I figured it was the issue with Zeppelin configuration for authentication,
> it is resolved now, thanks for your inputs.
>
> We had to use :
> /** = authcBasic
> And we were using :
> /** = authc
>
Hi Sandeep,
I figured it was the issue with Zeppelin configuration for authentication, it
is resolved now, thanks for your inputs.
We had to use :
/** = authcBasic
And we were using :
/** = authc
In zeppelin shiro
Thanks & Regards
Dhruv Goyal
> On 03-Aug-2018, at 10:21 PM, Sandeep Moré
Hello Dhruv,
It appears that the error (405) is coming from Zeppelin, do you see any
errors in Zeppelin log ? can you share zeppelin log and gateway-audit.log
for the above request ?
I have never encountered 405, I tried with Knox 1.1.0 and Zeppelin Version
0.6.0.2.5.0.0-1245 and did not
Hello Sandeep,
1. gateway.websocket.feature.enabled this is set to true in gateway site
2. Version of Zeppelin - 0.7.3
Gateway Log - This is just a part of it I cannot find any error or issue, I can
send the complete log if you want:
2018-08-03 14:41:18,554 DEBUG hadoop.gateway
Hello Dhruv,
What version of zeppelin are you testing with ? You will need to enable
websockets or Zeppelin UI to work, make sure you have websocket turned on
in gateway-site.xml.
Can you share gateway.log failure logs as well so we know where exactly
Knox is failing.
Best,
Sandeep
On Fri, Aug
Hi,
I am trying to enable Zeppelin with Knox, I have picked the latest changes done
in 1.1.0, but I am still facing the issue, when I login to the Knox and then
when I provide credentials to login to Zeppelin, it logs out (from zeppelin and
not from knox) and ask for credentials again. It
