[ZEPPELIN-3227] Authenticating and authorizing Zeppelin with Github Oauth

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.8.0
• Component/s: documentation, zeppelin-server
• Labels: documentation security zeppelin-server
• Assignee: Unassigned
• Reporter: Mitchell Yuwono
• Created: 13/Feb/18 02:34
• Updated: 13/Feb/18 08:03

Description

I've managed to successfully hook up Github oauth with zeppelin-0.8.0-SNAPSHOT using buji-pac4j for the company where I work currently. I had implemented a custom authorizer using github organization and teams which maps to shiro realms.

There's a related work on this I believe. There's one closed ticket https://issues.apache.org/jira/browse/ZEPPELIN-2598 and volumeint's contribution in https://github.com/bujiio/buji-pac4j/issues/61. Both really helped me in figuring out the inner workings as well as what and how I should approach the solution when I was implementing it. However I was struggling to find a related post and/or documentation on zeppelin side on this.

I reckon it would benefit everyone if we can have a documentation and possibly a default authorizer implementation for some major oauth providers, e.g. Github or Google oauth in the zeppelin server itself. I have an implementation for Github oauth, but not Google oauth.

What do you think?