element-hq / element-hq/matrix-authentication-service

Follow upstream Idp access + refresh token validity

Open
#3,234 1 comment 2 reactions 0 assignees View on GitHub
A-Upstream-OAuth
Dominant language
Rust
Stars
280
Forks
111
Avg merge
3d 1h
Merged PRs (30d)
25

Description

**Is your feature request related to a problem? Please describe.**

Currently, it looks like sessions I'm running with MAS and related to my upstream IdP are infinite lifetimes despited my upstream Idp has relatively short access token and refresh token validity values. They're not following Idp refresh token validity and access token validity.

**Describe the solution you'd like**

I would expect MAS to follow Idp refresh token validity + access token validity as a end date of session with MAS.
I also expect devices related to MAS to all have a finite lifetime correlated to IdP information.
What would be great, is to have an option to force user to login each time you add a new device or you need to login again to refresh an existing session on a device, so all devices (eg: a desktop and a mobile) are not logout at the same time, ie each device should have its own session lifetime. Otherwise, it would be less user-friendly for user to validate device using another existing session.

**Describe alternatives you've considered**

None. Maybe a configuration is missing on my side.

**Additional context**

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.