I note at https://community.cisco.com/t5/unified-computing-system-ucs/cimc-xml-api-change-in-behavior-for-0-day-provisioning/td-p/4864264, there was a change in behaviour in firmware version 4.2(3b), which enforces a password change before further functions can be used.
It seems imcsdk can't be used to do this initial password change (at least not using from imcsdk.apis.v2.admin.user import local_users_update), and I see in HISTORY.rst the latest version 0.9.13 (2022-07-21) supports only firmware version version 4.2(2a)
My provisioning script is now failing, and I don't want to manually reset passwords on every new machine.
I guess I'll use some XML request outside of imcsdk to do a password change but it seems sub-optimal. Is it intended for this to be covered in future?
I note at https://community.cisco.com/t5/unified-computing-system-ucs/cimc-xml-api-change-in-behavior-for-0-day-provisioning/td-p/4864264, there was a change in behaviour in firmware version 4.2(3b), which enforces a password change before further functions can be used.
It seems imcsdk can't be used to do this initial password change (at least not using
from imcsdk.apis.v2.admin.user import local_users_update), and I see in HISTORY.rst the latest version 0.9.13 (2022-07-21) supports only firmware version version 4.2(2a)My provisioning script is now failing, and I don't want to manually reset passwords on every new machine.
I guess I'll use some XML request outside of imcsdk to do a password change but it seems sub-optimal. Is it intended for this to be covered in future?