Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
I
iotivity-lite
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 41
    • Issues 41
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 12
    • Merge Requests 12
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • IoTivity
  • iotivity-lite
  • Issues
  • #98

Closed
Open
Opened Aug 09, 2019 by Rami Alshafi@ramiOwner

OBT aspects of Random PIN-based OTM Clarifications

CR 2999 adds some clarification about OBT aspects of Random PIN-based OTM. 

  • DOTS could retrieve new Devices UUID from "psk_identity_hint", and make that value available to application layer. This is not OBT behaviour mandated by the CR, but the corresponding Device side CR (CR 2725) spec makes it clear that "deviceuuid" Property of the "/oic/sec/doxm" Resource being sent in responses when the new Device is in RFOTM and when a Device Onboarding Connection is not currently established.
  • DOTS shall set "psk_identity" to the string "oic.sec.doxm.rdp".

JIRA migration meta data

  • JIRA Issue ID: LITE-75
  • Reporter: phawkes
  • Assignee: avolkov
  • Creator: phawkes
  • Created at: 2019-08-08T21:45:46.000-0700
  • 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: 2999
  • Product: None
  • Status: Done
  • Components: security
  • Priority: P1
  • Due Date: None
  • Issue Type: New Feature
    END of JIRA migration meta data

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: iotivity/iotivity-lite#98