Github user SarunasG commented on the issue:

    https://github.com/apache/zeppelin/pull/2373
  
    Hi All,
    
    Have one more question related to OIDC enablement on Zeppelin. I am now 
able successfully authenticate my user and log into Zeppelin app by Shiro, OIDC 
and Keycloak, but unfortunately I am not able to log out. It loops when I click 
on Logout button keeping my user being logged in with the initial token id, and 
does not direct me to Keycloak for another login attempt. 
    The scenario is:
    
    1) I hit default Zeppelin URL and then I am transferred to Keycloak for 
user credentials.
    2) I authenticate by user name and password so am logged into Zeppelin.
    3) I click on "Logout" button within Zeppelin app once I am there, then 
"Logout success" dialog box appears, and I am redirected to main Zeppelin 
screen.
    `baseUrlSrv.getRestApiBase() + '/login/logout'` followed by 
`window.location = baseUrlSrv.getBase()` from **navbar.controller.js**
    4) Once I am redirected to main page, default url is triggered and my user 
is logged in again without any promt for credentials because of stored token.
    
    I also added a few lines into shiro.ini file just to try, which I thought 
might help but looks it has no effect.
    ```
    [main]
    
logout.redirectUrl=http://localhost:8080/auth/realms/demo/protocol/openid-connect/logout
    
    [urls]
    /api/login/logout = logout
    ```
    Currently I am trying to solve this logout issue (to get actually logged 
out & directed to Keycloack for authentication with e.g. another user 
credentials...) and find a solution, but maybe someone already did that ? 
    Any tips on how to log out from Zeppelin with or without code modifications 
would be very welcome !


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to