Re: zeppelin.server.allowed.origins - does not seem to work with Zeppelin REST API

2018-06-28 Thread Ying Chen
ed.origins" is to do with setting CORS > header, which means this will continue to work over curl, but will get > blocked over any browsers. I've attached a screenshot for reference. > > > [image: Screenshot from 2018-06-26 09-48-23.png] > > > Let me know if this he

zeppelin.server.allowed.origins - does not seem to work with Zeppelin REST API

2018-06-25 Thread Ying Chen
Hello - I am in the process of validating some security settings for Zeppelin (0.7.3 w/ HDP 2.6.3) According to: https://zeppelin.apache.org/docs/0.7.0/install/configuration.html zeppelin.server.allowed.origins can be set to only allow requests that is coming from a specific host. I am not sure

Shiro security - cookie setting - throwing java.lang.NoSuchMethodError

2018-06-25 Thread Ying Chen
Hello - This is on HDP 2.6.3 / Zeppelin version: 0.7.3 I was following the instruction in: https://zeppelin.apache.org/docs/0.7.3/security/shiroauthentication.html and set: cookie = org.apache.shiro.web.servlet.SimpleCookie cookie.name = JSESSIONID cookie.secure = true cookie.httpOnly = true ses

Configuration for increasing header size? (REST) Notebook api complains about header too large

2018-06-06 Thread Ying Chen
When attempting to use notebook API to create a new notebook page, hitting an issue with the web page header. In the logs I see: Header is too large >8192 badMessage: 413 for HttpChannelOverHttp@77c7d025 {r=0,c=false,a=IDLE,uri=/api/notebook} - - [05/Jun/2018:19:23:40 +] "POST /api/notebook