Closed ehaligow closed 1 year ago
The "/redfish/v1/AccountService/Accounts/admin_1" has included the ID (admin_1) to identify which user name could find the account data. The "/redfish/v1/AccountService/Accounts/4" has included the ID (4) to find the account data as well. This "tests" folder just offers the test cases of examples for some devices and shows those commands how to use it. If you want to change it to match the ID and to get account data, we need to modify it.
Ths tc file is just to test functionality depends on what is kind of Redfish software. It is just reference test case. You could modify it for your BCM simulator. I could not use a single test case to fit any kind of Redfish software.
John will ask the Redfish Forum regarding which value should be used.
@JasonscHuang With Taskin no longer at Edgecore, Maciej needs a direct channel to you, instead of via Github issues. Please contact either of us via email. Thanks,
@jcleung5549 I am not a contact window. You could post your question to this repository. I could reply to you ASAP.
This was fixed with #52
Tasks (in access_device_PATCH_method.tc) send requests to the following URL:”/redfish/v1/AccountService/Accounts/admin_1” for newly user while there is no such endpoint - “/redfish/v1/AccountService/Accounts/4” is assigned to user 'admin_1' in BMC simulator.
./dm deviceaccess $1:$2:$admin_token:GET:/redfish/v1/AccountService/Accounts/admin_1:""
./dm deviceaccess $1:$2:$admin_token:PATCH:/redfish/v1/AccountService/Accounts/admin_1:1penBmc
./dm deviceaccess $1:$2:$admin_token:GET:/redfish/v1/AccountService/Accounts/admin_1:""