Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Proxy-Authorization token expired issue for cached destination #5563

Merged
merged 8 commits into from
Feb 27, 2025

Conversation

ZhongpinWang
Copy link
Contributor

@ZhongpinWang ZhongpinWang commented Feb 25, 2025

We do not cache destination with proxyConfiguration any more. The proxy configuration will be added every time after a destination is fetched from or not from cache.

Client credential token is cached anyway already so no performance issue when keep calling serviceToken() to set proxy authorization token.

Closes SAP/cloud-sdk-backlog#1255.
Fix #5131

  • I know which base branch I chose for this PR, as the default branch is v3-main now, which is not for v4 development.
  • If my change will be merged into the main branch (for v4), I've updated (V4-Upgrade-Guide.md)[./V4-Upgrade-Guide.md] in case my change has any implications for users updating to SDK v4

@ZhongpinWang ZhongpinWang changed the title fix: Stop caching proxy authorization token fix!: Stop caching proxy authorization token Feb 25, 2025
@ZhongpinWang ZhongpinWang changed the title fix!: Stop caching proxy authorization token fix!: Add proxyConfiguration on the fly instead of caching as part of the destination Feb 25, 2025
@ZhongpinWang ZhongpinWang changed the title fix!: Add proxyConfiguration on the fly instead of caching as part of the destination fix!: Add proxyConfiguration on the fly instead of caching it Feb 25, 2025
@ZhongpinWang ZhongpinWang changed the title fix!: Add proxyConfiguration on the fly instead of caching it fix!: Proxy-Authorization token expired issue for cached destination Feb 25, 2025
@ZhongpinWang ZhongpinWang changed the title fix!: Proxy-Authorization token expired issue for cached destination fix: Proxy-Authorization token expired issue for cached destination Feb 25, 2025
Copy link
Contributor

@deekshas8 deekshas8 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍🏽

@ZhongpinWang ZhongpinWang merged commit 438ebd8 into v3-main Feb 27, 2025
17 checks passed
@ZhongpinWang ZhongpinWang deleted the fix-move-add-proxy-configuration-after-caching branch February 27, 2025 10:28
ZhongpinWang added a commit that referenced this pull request Feb 27, 2025
…#5563)

* feat: use existing proxy authorization header if not expired

* fix: lint

* chore: add changeset

* fix: remove expiration check

* fix: lint

* fix: lint

* revert
ZhongpinWang added a commit that referenced this pull request Feb 28, 2025
…#5563) (#5580)

* feat: use existing proxy authorization header if not expired

* fix: lint

* chore: add changeset

* fix: remove expiration check

* fix: lint

* fix: lint

* revert
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Expired destinations through connectivity proxy remain in cache
2 participants