# Feature SI-68 - Store token expiration information for OIDC user tokens

Project: Stream Integration Basics
Status: closed
URL: https://community.openproject.org/work_packages/SI-68

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 15.4.0 |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Use cases

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Jan Sandbrink |
| 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  
**I want to** have expiration times of access tokens stored and honored,  
**so that** OpenProject does not cause HTTP 401 responses that could've been avoided and cause noise in monitoring and similar services.

**Acceptance criteria**

  - When obtaining an `OpenIDConnect::UserToken`, store the expiration date as provided by the OAuth 2.0 token endpoint

  - The `UserTokens::FetchService` should take that expiration date into account to judge whether a token is expired

  - If the token endpoint does not indicate an expiration time, we assume that the token does not expire
