GitHub user andreaTP reopened a pull request:
https://github.com/apache/zeppelin/pull/2373
[ZEPPELIN-2598] Securing Zeppelin with OpenID Connect
### What is this PR for?
Integrating Open ID connect login into Zeppelin leveraging Shiro(already
present) and Pac4J( that needs to be in the classpath).
Modifications done here should not affect any existing mechanisms but
simply integrates and enable new once.
### What type of PR is it?
[Improvement]
### What is the Jira issue?
[ZEPPELIN-2598]
### Questions:
* Does the licenses files need update?
* Is there breaking changes for older versions?
* Does this needs documentation?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nokia/zeppelin keycloak
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2373.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2373
----
commit 4ce91213eedf7c6b9eee1339290fbff1818989bd
Author: andrea <[email protected]>
Date: 2017-05-16T16:33:41Z
Enabling authentication with OpenId connect
commit 03bbe30b5707580580e2ee5c27126e7541220ff9
Author: andrea <[email protected]>
Date: 2017-05-30T06:32:02Z
updates
commit 545686dced6999bda7b8b6c21761874c9453cbd1
Author: andrea <[email protected]>
Date: 2017-05-30T12:23:24Z
fix username after direct login
commit 7ec8cddbe1f8162eb0bde7e2dbf8c76e2a4656bf
Author: andrea <[email protected]>
Date: 2017-06-01T13:07:55Z
reverted to a minimum
commit 80c375d42a3dc3f3de40360a0500c3c657ac2070
Author: andrea <[email protected]>
Date: 2017-06-19T19:48:41Z
fixed style issues on master
commit 31270f2cdce5a001353b6149cee4873ffa6d0fa8
Author: andrea <[email protected]>
Date: 2017-06-19T19:54:30Z
Merge remote-tracking branch 'apache/master' into keycloak
----
---
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 feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
