Comments (16)
Can you try running the tool from the "Issue18-Debug" branch? There are some trace messages in there to help show what the tool is seeing in some of these steps.
from redfish-protocol-validator.
Hi,
We tried running the tool from the "Issue18-Debug" branch and got the trace message. Attach the following log and report for reference:
210820.txt
RedfishProtocolValidationReport_08_20_2021_194251.zip
We follow the steps but still reproduce the situation that response 201 info when creating session with new account from manual test. We cannot found the crux. Could you add some trace message on the steps about create the account with PasswordChangeRequired set true?
Thanks.
from redfish-protocol-validator.
Hi,
For the previously provided log and report, Does this data help you?
Tell me if you need any help or further information.
Thanks.
from redfish-protocol-validator.
It does; I need to take a deeper look into things, especially based on the comments made in issue #27
I'll let you know if I need help testing new changes.
from redfish-protocol-validator.
Hi,
May I ask about the progress of this issue?
We're looking forward to your reply.
Thanks.
from redfish-protocol-validator.
Unfortunately I have not had time to look further into this. This is still on my todo list to debug further.
from redfish-protocol-validator.
Okay..I'm still looking forward to your help.
May I know when you expect to start working on this issue?
Thanks.
from redfish-protocol-validator.
@FelixD999 could you please run from the branch "Additional-Tracing" with --log-level debug
? This should show traces for all HTTP requests/responses (minus the response body).
from redfish-protocol-validator.
Attached the data for refer:
RedfishProtocolValidationReport_debug.zip
from redfish-protocol-validator.
Following the trace, I see the account created at line 1184, followed by a GET on the account at line 1203 and 1222, and then a POST to the session collection at line 1242 (with the credentials from the first operation).
Since response data is not shown, I'd like to try this with curl. Can you run the following and provide the output? This should mimic the sequence the tool is using.
curl -k -u Administrator:superuser1 -D - -X POST 'https://192.168.0.117/redfish/v1/AccountService/Accounts' -H "Content-Type: application/json" -d '{"UserName": "rfpvd0dc", "Password": "n2ujtfRgDe", "RoleId": "ReadOnly"}'
curl -k -u Administrator:superuser1 -D - 'https://192.168.0.117/<URI from Location header in previous response>'
curl -k -D - -X POST 'https://192.168.0.117/redfish/v1/SessionService/Sessions' -H "Content-Type: application/json" -d '{"UserName": "rfpvd0dc", "Password": "n2ujtfRgDe"}'
curl -k -u Administrator:superuser1 -D - -X DELETE 'https://192.168.0.117/<URI from Location header in first response>'
from redfish-protocol-validator.
Attached the data for refer:
issues28_curl_220317.log
from redfish-protocol-validator.
Ah, I see what's going on; the account started off as disabled after creation.
Can you please try this sequence? If this works, I'll need to add a step to enable the account when performing this testing.
curl -k -u Administrator:superuser1 -D - -X POST 'https://192.168.0.117/redfish/v1/AccountService/Accounts' -H "Content-Type: application/json" -d '{"UserName": "rfpvd0dc", "Password": "n2ujtfRgDe", "RoleId": "ReadOnly"}'
curl -k -u Administrator:superuser1 -D - 'https://192.168.0.117/<URI from Location header in previous response>'
curl -k -u Administrator:superuser1 -D - -X PATCH 'https://192.168.0.117/<URI from Location header in first response>' -H "Content-Type: application/json" -d '{"Enabled": true}'
curl -k -u Administrator:superuser1 -D - 'https://192.168.0.117/<URI from Location header in first response>'
curl -k -D - -X POST 'https://192.168.0.117/redfish/v1/SessionService/Sessions' -H "Content-Type: application/json" -d '{"UserName": "rfpvd0dc", "Password": "n2ujtfRgDe"}'
curl -k -u Administrator:superuser1 -D - -X DELETE 'https://192.168.0.117/<URI from Location header in first response>'
from redfish-protocol-validator.
@FelixD999 I've also updated the "Additional-Tracing" branch to include a potential fix based on curl sequence above.
from redfish-protocol-validator.
Attached the curl data and report for refer:
issue28_debug_0322.zip
from redfish-protocol-validator.
So the updated sequence looks correct. From the output from the test report and the curl results, I see the POST to the session collection does create a new session with the correct message indicating the user needs to change their password, but the HTTP status code is 400 instead of 201. Would you be able to look into why the service is responding with a 400 status code?
from redfish-protocol-validator.
After retried the case by manual in our latest version can reproduced the status code was 400. We will fix this issue then return 201. The step "Enable the account" help us to explain the confusion about the 401 status code.
Many thanks.
from redfish-protocol-validator.
Related Issues (20)
- Some error response checking only inspects `@Message.ExtendedInfo`
- Invalid JSON responses crash tool HOT 1
- Clarification on SEC_ACCOUNTS_SUPPORT_ETAGS test HOT 5
- New Test Case to Ensure PATCH Responses Are Correct
- Test query parameters HOT 5
- SERV_SSE_EVENT_DEST_DELETED_ON_CLOSE should wait much longer than 3 seconds HOT 3
- Some questions about SSDP test cases HOT 7
- Regarding the specification of AL HOT 3
- Returned 202 status code after disabling SSDP HOT 4
- Redfish Protocol Validator report FAIL HOT 8
- urllib3 2.0 support
- Ongoing or upcoming plans to address pending work (# TODOs) HOT 1
- etag is mandatory or not HOT 2
- Issue in SERV_SSE_CLOSE_CONNECTION_IF_EVENT_DEST_DELETED HOT 11
- New error says "shall" where spec says "should" HOT 5
- Request for guidance on assertion REQ_DATA_MOD_ERRORS HOT 4
- Query on data_modification_requests_no_auth() in resources.py HOT 1
- /archive/reds/tags/{file}.zip points to a different version as the name of the {file}. HOT 3
- Tool no longer works with python 3.6 HOT 3
- Basic Auth updates
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from redfish-protocol-validator.