I hope this is not claimed anywhere as it is currently not supported.

(In reply to vareti from comment #3)
> I hope this is not claimed anywhere as it is currently not supported.

[arghosh@arghosh ~]$ oc get crd oauths.config.openshift.io -oyaml|grep -A 20 'tokenConfig'
            tokenConfig:
              description: tokenConfig contains options for authorization and access
                tokens
              properties:
                accessTokenInactivityTimeoutSeconds:
                  description: 'accessTokenInactivityTimeoutSeconds defines the default
                    token inactivity timeout for tokens granted by any client. The
                    value represents the maximum amount of time that can occur between
                    consecutive uses of the token. Tokens become invalid if they are
                    not used within this temporal window. The user will need to acquire
                    a new token to regain access once a token times out. Valid values
                    are integer values:   x < 0  Tokens time out is enabled but tokens
                    never timeout unless configured per client (e.g. `-1`)   x = 0  Tokens
                    time out is disabled (default)   x > 0  Tokens time out if there
                    is no activity for x seconds The current minimum allowed value
                    for X is 300 (5 minutes)'
                  format: int32
                  type: integer
                accessTokenMaxAgeSeconds:
                  description: accessTokenMaxAgeSeconds defines the maximum age of
                    access tokens
                  format: int32

That's a wrong component, oauth-apiserver hasn't shipped yet, but I understand the confusion.

This feature hasn't worked in 4.x clusters, but there is an RFE - https://issues.redhat.com/browse/RFE-88.

I'll mark the field as deprecated as it should've always been, not sure if the description change makes it to earlier openshift versions though.

If failed QA, move to Assigned instead. "Post" is incorrect, it means the fix PR exists, but just yet still not merged.
If wanting to verify, pls check the latest payload as of wanting to verify, instead of yesterday old payload, because every hours there is newer "latest" payload with newer updates.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.5 image release advisory), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2409