Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Problem Statement

Currently to update the content implementation team needs to make multiple calls, which makes it a difficult process. Additionally there is no auditing in place to track as content was updated by whom. There should be an easier way to update the content.

SB-10220 - Getting issue details... STATUS

Solution Approach

Solution approach is divided into multiple part

  • There should be generated key to facilitate the process of update of content in a channel by anyone who has the key, hence bypassing the user authentication processĀ . The details of the master key generation design and approach are here (Master Key APIs).
  • Auditing of the update of the content by keys.
  • No labels