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 10
    • Merge Requests 10
  • 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
  • #9

Closed
Open
Opened Jan 08, 2020 by Oleksandr Andrieiev@OleksandrContributor

[Feature] Auditable Events

Need to implement new SVR: /oic/sec/ael

Read-only properties and their default values:

  • events: []
  • usedspace: 0
  • maxspace: 2000
  • unit: "Byte"

Read-write properties and their default values:

  • categoryfilter: 0xff
  • priorityfilter: 4

API has to be callable from any parts of security stack. Input parameters are: message, category, priority, auxiliaryinfo. The call results:

  1. Addition of new Auditable Event in events array, if filtering passes
  2. Removal of oldest Auditable Event(s) in events array, while max size is exceeded
  3. The change has to be reflected in a persistent storage

Properties of Auditable Event data type and their default values:

  • devicetype and di: copied from /oic/d
  • category and priority: defined in specification table per each event, input in API call
  • timestamp: does not have to be real time, can just be an incremented global value
  • message: input in API call
  • auxiliaryinfo: defined in specification table per each event, input in API call

Relevant BZ tickets:

  • https://bugzilla.openconnectivity.org/show_bug.cgi?id=3035
  • https://bugzilla.openconnectivity.org/show_bug.cgi?id=3149
  • https://bugzilla.openconnectivity.org/show_bug.cgi?id=3150
Edited Jan 22, 2020 by George Nash
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
Feb 7, 2020
Due date
Feb 7, 2020
Reference: iotivity/iotivity-lite#9