-
Notifications
You must be signed in to change notification settings - Fork 23
[Fix] IAM: Fix cross-tenant agency AK/SK auth #955
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
Merged
anton-sidelnikov
merged 3 commits into
opentelekomcloud:devel
from
TobiWo:hotfix/fix-cross-tenant-agency-ak-sk-auth
Jul 6, 2026
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This introduces a data race:
ReauthFuncrewritesclient.AKSKAuthOptionswhile every request reads it unlocked when signing (provider_client.go:291-305).The old code never hit this path because it cleared
AccessKey.go test -raceshows it right away.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The race is real. Signing reads
client.AKSKAuthOptions.*unlocked (provider_client.go:291-303), andReauthFuncwrites those same fields.reauthenticateAndRetryholdsclient.mutaroundReauthFunc, but a first-time request signs indoRequestwithout taking that lock, so a concurrent sign and reauth can hit it together. The old token path avoided this by clearingAccessKeyand skipping the signing block; we can't, because retries needAccessKeyto re-sign.One caveat for the thread: the suggested replacement doesn't fully close it. It swaps a whole-struct assignment for field-by-field writes, which shrinks the window, but those writes are still unlocked and still race the unlocked reads.
There is no locked setter for AK/SK options; only
SetToken/Tokenguard anything.go test -racepasses here only because the tests never sign a request while a reauth is running.Decision: take the snippet now for the smaller window, and track the real fix separately: a locked accessor around the AK/SK signing reads and reauth writes in
provider_client.go. That touches the signing path for every service, so it's out of scope for a hotfix. Pre-existing gap, not something this PR introduced. I will create a follow-up issue if you agree.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed it's real but it's not pre-existing. This PR makes it reachable (old code cleared
AccessKeyand signing was skipped).I'm fine to merge it and fix in the next issue.