THREESCALE-11884 - Fix unable to set ApplicationKey by ApplicationAuth CR when using OIDC auth #1110
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.
What
Close #1078
Fix:
Verification steps:
NOTE:
user_keyis set to custom field calledtoken{ "lastTransitionTime": "2025-09-01T07:00:46Z", "message": "Secret \"auth-secret-unknown\" not found", "status": "True", "type": "Failed" },Under
API Key (user_key) Basicsyou shall seeAuth user keyis set totokenyou should see
User Keyis set totestkeyauth-secretand setUserKeytotestkey2testkey2