-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redfish: Violations: /redfish/v1/Managers/bmc/Truststore/Certificates #119
Comments
If your question is about the below URL should be a valid path, then I guess you are correct, but there is nothing that we can show there when compared to the other URL''s like HPPTS and LDAP. $ curl -k https://${bmc}/redfish/v1/Managers/bmc/Truststore |
@devenrao This violates the Redfish spec, Redfish has expanded where the Certificate schema can be implemented. https://redfish.dmtf.org/schemas/v1/CertificateCollection_v1.xml
Can we move to one of these ? |
Here
|
Manager.Certificates would generally be used for this purpose, which was added in 2021.2 |
If I understand the use case here the better place would actually be: /redfish/v1/Managers/{ManagerId}/SecurityPolicy/TLS/Client/TrustedCertificates |
Agreed. But SecurityPolicy is introduced in Manager v1.16+, now bmcweb is still using Manager v1.14, a schema verison bump is needed. |
Yep, this is what I meant (my message was not very clear). |
This is still a problem, https://gerrit.openbmc.org/c/openbmc/bmcweb/+/61958 was an attempt to fix but needs more thought |
https://redfish.dmtf.org/schemas/v1/CertificateCollection_v1.xml
The options under Managers are:
/redfish/v1/Managers/{ManagerId}/RemoteAccountService/Accounts/{ManagerAccountId}/Certificates
/redfish/v1/Managers/{ManagerId}/RemoteAccountService/ActiveDirectory/Certificates
/redfish/v1/Managers/{ManagerId}/RemoteAccountService/LDAP/Certificates
/redfish/v1/Managers/{ManagerId}/RemoteAccountService/ExternalAccountProviders/{ExternalAccountProviderId}/Certificates
/redfish/v1/Managers/{ManagerId}/NetworkProtocol/HTTPS/Certificates
The text was updated successfully, but these errors were encountered: