We do use nginx, but nginx auth only (not zeppelin+shiro).
The nginx user will be the only authentication that takes place - it doesn’t
pass anything to zeppelin (zeppelin is unaware of basic auth via nginx as far
as I know).
You are correct, that you can leave zeppelin setup for basic
Hello,
I have configured nginx to front load the authentication (basic) to Zeppelin
UI. With that, I am able to see the login dialog and it allows access to
Zeppelin only after entering valid credentials. However, I believe the
user/principal is not propopaged to AuthenticationInfo component
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/814
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the fea
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/814#issuecomment-214075844
Merge if there're no more discussions
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If y
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/814#issuecomment-210926723
Looks good to me.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
GitHub user astroshim opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/814
Fix nginx config to use single port for websocket and REST.
### What is this PR for?
Zeppelin uses single port number for REST and websocket since 0.5.5 so It
should be fixed
