You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zeppelin.apache.org by "Mitchell Yuwono (JIRA)" <ji...@apache.org> on 2018/02/13 02:35:02 UTC

[jira] [Created] (ZEPPELIN-3227) PAC4J oauth integration

Mitchell Yuwono created ZEPPELIN-3227:
-----------------------------------------

             Summary: PAC4J oauth integration
                 Key: ZEPPELIN-3227
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3227
             Project: Zeppelin
          Issue Type: Improvement
          Components: documentation, zeppelin-server
    Affects Versions: 0.8.0
            Reporter: Mitchell Yuwono


I've managed to successfully hook up Github oauth with zeppelin-0.8.0-SNAPSHOT using buji-pac4j. I had implemented a custom authorizer using github organization and teams which maps to shiro realms. There's a closed ticket https://issues.apache.org/jira/browse/ZEPPELIN-2598 and [~volumeint]'s contribution in [https://github.com/bujiio/buji-pac4j/issues/61] which really helped me in figuring out the inner workings.

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?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)