Skip to content

Component logs are contains sensitive data #8

@stas-fomenko

Description

@stas-fomenko

Description: Components action logs contains sensitive data

STR:

  1. Create new flow with simple-trigger as step When result of JSONata evaluation is empty (undefined) - empty message is sent #1.
  2. Add sample manually:
    { "Account": { "Account Name": "Firefly", "Order": [ { "OrderID": "order103", "Product": [ { "Product Name": "Bowler Hat", "ProductID": 858383, "SKU": "0406654608", "Description": { "Colour": "Purple", "Width": 300, "Height": 200, "Depth": 210, "Weight": 0.75 }, "Price": 34.45, "Quantity": 2 }, { "Product Name": "Trilby hat", "ProductID": 858236, "SKU": "0406634348", "Description": { "Colour": "Orange", "Width": 300, "Height": 200, "Depth": 210, "Weight": 0.6 }, "Price": 21.67, "Quantity": 1 } ] } ] } }
  3. Add new step with jsonata-transform-component
  4. Input: { "account": Account."Account Name", "products": Account.Order.Product.({ "name": $."Product Name", "revenue": (Price * Quantity) }), "orderIDs": Account.Order[].(OrderID) }
  5. See sensitive data in logs:
    image

AR: Component logs are contains sensitive data

ER: Component logs does not contain any sensitive data.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions