Set ouath user token expiration time to 365 days

[karelyatin]

With [1] it was attempted to set token expiration to infinite but as described in [2] with the config set to 0, token expiration is set to default i.e 24 hours. With this patch setting it to a larger value i.e 365 days.

[1] #332
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1959776
Related-Issue: #331

[openshift-ci]

Hi @karelyatin. Thanks for your PR.

I'm waiting for a crc-org member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[gbraad]

Is there a way to test this is actually set to a full year, after the deployment?

[karelyatin]

Is there a way to test this is actually set to a full year, after the deployment?

I did checked locally by manually patch oauth cluster config

$ oc get oauth cluster -o jsonpath="{.spec.tokenConfig}"
{"accessTokenMaxAgeSeconds":31536000}
$ oc get useroauthaccesstokens sha256~veewdhtbEbMsLFJa0D-eYbbKnswcpisjeGmBx4cfnFU
NAME                                                 CLIENT NAME                    CREATED   EXPIRES                         REDIRECT URI                                                    SCOPES
sha256~veewdhtbEbMsLFJa0D-eYbbKnswcpisjeGmBx4cfnFU   openshift-challenging-client   56m       2025-12-13 11:48:42 +0000 UTC   https://oauth-openshift.apps-crc.testing/oauth/token/implicit   user:full

[gbraad]

Ideally, an automated test would need to be added. @wdyt, @praveenkumar @lilyLuLiu ?

[praveenkumar]

/ok-to-test

[praveenkumar]

Ideally, an automated test would need to be added. @wdyt, @praveenkumar @lilyLuLiu ?

We don't need any specific test for this because if it expire user can login again and regenerate but I think @karelyatin is right about current state of this one (only having 24 hour expire time).

[praveenkumar]

/lgtm

[praveenkumar]

/cherry-pick release-4.17

[openshift-cherrypick-robot]

@praveenkumar: once the present PR merges, I will cherry-pick it on top of release-4.17 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[praveenkumar]

/cherry-pick release-4.18

[openshift-cherrypick-robot]

@praveenkumar: once the present PR merges, I will cherry-pick it on top of release-4.18 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.18

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[praveenkumar]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: praveenkumar

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [praveenkumar]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@karelyatin: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-microshift	03e5c6b	link	true	/test e2e-microshift

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.