[Sub Component] SO-Audit (Auto) Microservice

[TanmoySG]

Implementation of Audit Microservice for auditing and validating the contract partially.

[Parent Component]

• 1

• 2

[Checkpoints]

• [x] Service Name Audit - not strict
  • Check if Service Name already exists
  • Check Name Friendliness
  • If duplicate, check fails, but is passed to manual check
  • Manual check might also be a patching point where the manual checker mails/asks the devs to update name
  • Not strict
• [x] Repository Audit - not strict
  • The Repo check is not strict, that is, if test/check method fails, it is passed for manual check
  • Pings the Repository
  • If the repo exists , and is public, a response is received and the check is considered as pass
  • If repo doesn't exist or is not public a 404 response is received and the check fails
  • Even though the check fails, the contract is not rejected as repo check is not strict and is passed to manual check
  • Manual check is also non-strict
• [x] Data Access - strict
  • Iterate through each data access request block
  • Check each data-field to verify if it is exposed
  • If it is exposed, check the access requested (read, write, etc)
  • If the requested access is in the data-field's allowed access list, check passes
  • Else, fails (Strict)
  • If Not exposed, check fails (Strict)
  • Use something like Access Control List
• [x] Implement Access Control List

  • 10

• [x] The audited contract should be moved to the WDB data store for further manual auditing

[Additional Details]

[TanmoySG]

To parse multi-level nested JSON

https://blog.serverbooter.com/post/parsing-nested-json-in-go/

[TanmoySG]

Dependancy

The Onboarding Audit-Validation Step depends on the existence of the service-repository part of the service manager. A mock service-manager with minimal data emission, that can closely mimic the working of the real one is required.

• Create a Mock/Placeholder Services Repository