# Feature OP-17419 - OpenID Connect Session management and synchronization

Project: OpenProject
Status: specified
URL: https://community.openproject.org/work_packages/OP-17419

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Product Backlog |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Authentication / OpenID Connect (OIDC), Integrations / openDesk |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As an** administrator integrating our application with an OIDC-compliant Identity Provider (e.g., Keycloak, Auth0)  
**I want to** verify the validity of the user’s session at the IdP from within our application  
**so that** we can synchronize logout behavior and avoid the user remaining logged into our app after their IdP session has expired

**Acceptance criteria**

  - When the session at the IDP has ended (either due to expiry or logout), the user's session at OpenProject should end as well

  - Interacting with OpenProject should keep the IDP session "alive"

  - TBD: Allow users to disable new behaviour?

**Technical notes**

  - A session validation mechanism is necessary, for example:
    
      - OIDC check\_session\_iframe (per [OIDC Session Management spec](https://openid.net/specs/openid-connect-session-1_0.html)), or
    
      - A silent frontend re-authentication flow (prompt=none) returning the current session state, or
    
      - a silent backend re-authentication flow using the refresh token **(preferred)**

  - Which providers would we expect this to be supported?
    
      - Keycloak (openDesk)

**Permissions and visibility considerations**

  - Users of the application are indirectly affected (e.g. by automatic logout behavior)
    
    <br>

**Translation considerations**

  - *Key terms and phrases in the key languages* 

**Out of scope**

  - 
    <br>
