Client Credentials Grants' Access tokens not respecting Access Token Lifespan and being bound to `SSO Session Max` #44282

eduser25 · 2025-11-18T01:02:54Z

eduser25
Nov 18, 2025

This might be very well on purpose, but I'd like to have some feedback as of why this is like this:

When creating a client with service account enabled, I'd expect to be able to allow for longer Access token longevity to the tokens created by such client, but they seem to be anyway bound to SSO Session Max even though they are not related to the SSO process nor are they user sessions in this case?

There are a bunch of use cases that could benefit from this, why enforce SSO Session Max for access tokens for machine connectivity for example?

Is this intended? I've tried multiple options but none seem to be able to escape SSO Session max, and it seems very much by design. What's the intention in this case?

Navigation Menu

Repository navigation

Client Credentials Grants' Access tokens not respecting Access Token Lifespan and being bound to `SSO Session Max` #44282

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 0 comments

Select a reply

Uh oh!

Client Credentials Grants' Access tokens not respecting Access Token Lifespan and being bound to SSO Session Max #44282

Uh oh!

Uh oh!

eduser25 Nov 18, 2025

Replies: 0 comments

Client Credentials Grants' Access tokens not respecting Access Token Lifespan and being bound to `SSO Session Max` #44282

eduser25
Nov 18, 2025