IoTivity uses DER encoding which no loger allowed by schema
After pulling schemas from branch OCF-v2.1.0 into the CTT, IoTivity Classic started failing Check 8 in CT1.2.2 that does validation of resources against schemas. Results attached.
Currently the schema definition of publicdata.encoding property is:
"publicdata": {
"properties": {
"data": {
"description": "The encoded value.",
"maxLength": 3072,
"type": "string"
},
"encoding": {
"description": "Public credential information\nA string specifying the encoding format of the data contained in the pubdata.",
"x-detail-desc": [
"oic.sec.encoding.pem - Encoding for PEM encoded certificate or chain."
],
"enum": [
"oic.sec.encoding.pem"
],
"type": "string"
}
},
"type": "object"
},
Now the only allowed encoding of publicdata.data is "oic.sec.encoding.pem", but Classic has the odd credential of type 4 that it creates automatically upon request to /oic/sc/csr, which has encoding of "oic.sec.encoding.der":
{
"creds": [
{
"credid": 1,
"subjectuuid": "11111111-2222-3333-4444-555555555555",
"credtype": 1
},
{
"credid": 2,
"subjectuuid": "9e1e744f-aa17-4aa0-98c2-eeb9f08b25de",
"credtype": 4,
"publicdata": {
"encoding": "oic.sec.encoding.der",
"data": "MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEk17xBJ_EPiQ3oOBsW84gWTL4FihNjqXjYkZPKeeupRYzi6waiM4gGfR7ZCzTjXPNBsriNebO_2Ec8c3pktUDRw"
},
"credusage": "oic.sec.cred.cert"
}
],
"rowneruuid": "11111111-2222-3333-4444-555555555555",
"rt": [
"oic.r.cred"
],
"if": [
"oic.if.baseline"
]
}
JIRA migration meta data
- JIRA Issue ID: IOT-3306
- Reporter: krzysztof.j.wlodarczyk
- Assignee: nathanheldtsheller
- Creator: krzysztof.j.wlodarczyk
- Created at: 2019-12-03T06:37:17.000-0800
- Found in Version: master
- Fix in Version: None
- Issue Severity: Normal
- Reproducibility: Always (100%)
- Operating System: None
- Hardware/ OEM Platform: None
- External URL: None
- Bugzilla ID: None
- Product: None
- Status: Open
- Components: Security
- Priority: Undecided
- Due Date: None
-
Issue Type: Bug
END of JIRA migration meta data