You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to create an API key for a specific user, as indicated by the unique_user_name parameter, the key is successfully created, but the key belongs to the user account that obtained the token in a previous step.
Given a username of ansible100 with id ee8e595c-6632-4411-9035-06de5f63c1c0 for example, I expect the s3 key to be created for the unique_user_name account id:
The access key is created under the account that obtained the token in the first task. Note the difference in the output of the UUID and userURN in the actual results.
I can independently confirm using the REST API and the UI that the access keys are created for the user obtaining the token, not the unique-user_name we are trying to create the access keys for.
Thanks for this module! It's extremely helpful.
SUMMARY
When trying to create an API key for a specific user, as indicated by the
unique_user_name
parameter, the key is successfully created, but the key belongs to the user account that obtained the token in a previous step.ISSUE TYPE
COMPONENT NAME
na_sg_org_user_s3_key
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
MacOS Sonoma 14.6.1 (23G93)
STEPS TO REPRODUCE
EXPECTED RESULTS
Given a username of
ansible100
with idee8e595c-6632-4411-9035-06de5f63c1c0
for example, I expect the s3 key to be created for theunique_user_name
account id:ACTUAL RESULTS
The access key is created under the account that obtained the token in the first task. Note the difference in the output of the UUID and userURN in the actual results.
I can independently confirm using the REST API and the UI that the access keys are created for the user obtaining the token, not the
unique-user_name
we are trying to create the access keys for.The text was updated successfully, but these errors were encountered: