DELTE acl2 use case looks only for an IPv6 endpoint (and not the best available)
OTGC's DELETE acl2 procedure issues requests to the endpoint obtained from device.getIpv6SecureHost() and thereby looks only for an IPv6 endpoint.
However, Servers responding to discovery over IPv4 will return only IPv4 endpoints and in this situation, device.getIpv6SecureHost() will always return NULL.
So, a better strategy is to use the endpoint obtained using
iotivityRepository.getSecureEndpoint(device) and pass that endpoint to all calls in the DELETE acl2 use case. This is infact how it seems to be done elsewhere, in the DELETE creds use case, for e.g.
The attached patch resolves this issue.
JIRA migration meta data
- JIRA Issue ID: LITE-93
- Reporter: kmaloor
- Assignee: kmaloor
- Creator: kmaloor
- Created at: 2019-10-13T19:20:05.000-0700
- Found in Version: 2.1.0
- Fix in Version: None
- Issue Severity: Critical
- Reproducibility: Always (100%)
- Operating System: Android
- Hardware/ OEM Platform: None
- External URL: None
- Bugzilla ID: None
- Product: None
- Status: Done
- Components: otgc
- Priority: Undecided
- Due Date: None
Issue Type: Task
END of JIRA migration meta data