fix(proxy): honor access token cache ttl

[stonith404]

Description

Pass the configured fallback access token TTL into the OIDC authenticator.

When the proxy cannot derive an expiration from the access token, for example with opaque tokens and PROXY_OIDC_ACCESS_TOKEN_VERIFY_METHOD=none, it should use PROXY_OIDC_USERINFO_CACHE_TTL for userinfo cache entries. The option was parsed and passed into the middleware setup, but not copied onto the authenticator, causing cache entries to expire immediately.

This change makes the implementation match the documented fallback behavior.

Related Issue

• Fixes Token refresh during upload process ["Host requires authentication"] #3050

Motivation and Context

I maintain Pocket ID and ran into this while setting up OpenCloud on my own server. Desktop sync stalled because OpenCloud repeatedly called Pocket ID’s userinfo endpoint until Pocket ID started rate limiting those requests.

The setup uses opaque access tokens with PROXY_OIDC_ACCESS_TOKEN_VERIFY_METHOD=none, so OpenCloud cannot derive an expiration from the access token and should fall back to PROXY_OIDC_USERINFO_CACHE_TTL. That fallback TTL was configured, but it was not applied by the OIDC authenticator, causing userinfo cache entries to expire immediately.

How Has This Been Tested?

I have created a custom image with this change, deployed it on my server and I can confirm that the TTL is now correctly respected and Pocket ID doesn't get spammed anymore with userinfo requests.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation added

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics -6 duplication

Metric	Results
Duplication	-6

View in Codacy

🟢 Coverage 100.00% diff coverage · +0.02% coverage variation

Metric	Results
Coverage variation	✅ +0.02% coverage variation (-1.00%)
Diff coverage	✅ 100.00% diff coverage

View coverage diff in Codacy

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (93fb9cb)	Report Missing	Report Missing	Report Missing
Head commit (5457ef8)	82290 (+1)	18974 (+19)	23.06% (+0.02%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#3056)	1	1	100.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

¹ Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[rhafer]

@stonith404 Thanks a lot for the fix! Good catch.