[
https://issues.apache.org/jira/browse/KNOX-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203639#comment-16203639
]
Tomasz Ulinski commented on KNOX-710:
-------------------------------------
Thank you [~moresandeep] for pointing this out.
Am I correct in thinking that Zeppelin uses Apache Shiro internally so
authenticating websocket connection to Zeppelin through Knox looks like this:
1. Browser sends a ticket request to Knox
2. Knox doesn't validate user's credentials but just forwards the request to
Zeppelin
3. Zeppelin handles user auth with Apache Shiro
4. Tickets is returned back (through Knox) to the browser
5. [?] Ticket is used to establish a websocket connection (is it a session
cookie or Authorization header?). Or maybe websocket connection is established
without authentication, but the ticket is attached to every websocket message?
> Support Zeppelin UI through Knox
> --------------------------------
>
> Key: KNOX-710
> URL: https://issues.apache.org/jira/browse/KNOX-710
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Affects Versions: 0.9.0
> Environment: All
> Reporter: Jeffrey E Rodriguez
> Assignee: Prabhjyot Singh
> Fix For: 0.12.0
>
> Attachments: KNOX-710.001.patch
>
>
> Zeppelin is a great data analytics product,
> https://zeppelin.incubator.apache.org/
> It would be great if we can support Zeppelin through Knox.
> One of the challenges is websocket support through Knox.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
