Home
last modified time | relevance | path

Searched refs:KeyUsage (Results 1 – 7 of 7) sorted by relevance

/openbmc/bmcweb/redfish-core/include/generated/enums/
H A Dcertificate.hpp17 enum class KeyUsage{ enum
58 NLOHMANN_JSON_SERIALIZE_ENUM(KeyUsage, {
59 {KeyUsage::Invalid, "Invalid"},
60 {KeyUsage::DigitalSignature, "DigitalSignature"},
61 {KeyUsage::NonRepudiation, "NonRepudiation"},
62 {KeyUsage::KeyEncipherment, "KeyEncipherment"},
63 {KeyUsage::DataEncipherment, "DataEncipherment"},
64 {KeyUsage::KeyAgreement, "KeyAgreement"},
65 {KeyUsage::KeyCertSign, "KeyCertSign"},
66 {KeyUsage::CRLSigning, "CRLSigning"},
[all …]
/openbmc/openbmc-test-automation/docs/
H A Dcertificate_generate.md164 "KeyUsage": [],
/openbmc/bmcweb/
H A DRedfish.md92 - KeyUsage
704 - KeyUsage
/openbmc/docs/designs/
H A Dredfish-tls-user-authentication.md208 - does KeyUsage contain required data ("digitalSignature" and "keyAgreement")
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Certs/
H A DREADME.md137 "KeyUsage":["ServerAuthentication","ServerAuthentication"],
/openbmc/qemu/tests/unit/
H A Dpkix_asn1_tab.c.inc31 {"KeyUsage", 1610874886, 0},
/openbmc/docs/security/
H A DTLS-configuration.md23 - `KeyUsage` contains required purpose `digitalSignature` and `keyAgreement`