THREESCALE-11884 - Fix unable to set ApplicationKey by ApplicationAuth CR when using OIDC auth#1110
Conversation
…er_key See THREESCALE-11072 for details
|
Skipping CI for Draft Pull Request. |
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) ✅ license/snyk check is complete. No issues have been found. (View Details) |
ac974e4 to
d5e1b22
Compare
d5e1b22 to
76a21f9
Compare
76a21f9 to
27f62bf
Compare
|
PR needs rebase. DetailsInstructions 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. |
|
@tkan145: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
What
Close #1078
Fix:
Verification steps:
Details
NOTE:
user_keyis set to custom field calledtokenDetails
{ "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