Public Attestation

Transparency through Public Attestation

You may wish to attest information to the general public, without the need for viewers to log-in to their RKVST account. Public Assets can be used to publicly assert data, also referred to as Public Attestation. For example, you may attest to data containing a vulnerability report against an OpenSource software package or the maintenance records for a building.

Permissioned Assets can only be shared through the creation of Access Policies. Public Assets, however, may be shared with a Public URL that points to a read-only view of the Asset, similar to the link sharing you may have seen in file sharing services such as Google Drive or DropBox.

Any Events updating a Public Asset will also be public, and will each have their own unique Public URL.

Following the link to a Public Asset or Public Event will allow read-only access to its information, without the need to sign in to RKVST.

For more detailed Asset creation instructions, visit Creating an Asset.

Creating a Publicly Attested Asset

Warning: Assets can only be made public at Asset Creation and cannot be made private afterwards. The Asset and all its Events will be publicly accessible forever.
  1. Create an Asset with your desired attributes and set it to public. See Creating an Asset for detailed instructions.

Select Register Asset from the sidebar and fill in the desired details.

Asset Details

Check the box next to Make Asset Public.

Check Asset as Public

Create a JSON file with your desired Asset details. Set keyword public to true.

{
    "behaviours": ["RecordEvidence", "Attachments"],
    "attributes": {
        "arc_display_name": "Publicly Attested Asset",
        "arc_display_type": "Example",
        "arc_description": "This example asset is publicly attested, so anyone with the link can access its details without signing in to RKVST."
    },
    "public": true
}
  1. Publish your Public Asset.
WARNING: Once an Asset is made public, it cannot be made private. The Asset and all its Events will be publicly accessible forever.

Click Create Asset to complete your Public Asset creation.

Publish Your Asset

Use the curl command to run your JSON file. See instructions for creating your BEARER_TOKEN_FILE here.

curl -v -X POST \
    -H "@$BEARER_TOKEN_FILE" \
    -H "Content-type: application/json" \
    -d "@/path/to/jsonfile" \
    https://app.rkvst.io/archivist/v2/assets
  1. Retrieve public link to share your Public Asset with others.
NOTE: A Public Asset may only be updated by the Tenancy that created it. Anyone viewing the Asset using the public link will have read-only access.
  1. The following screenshot shows the public view of the Asset when the link is followed.
    Public View

Adding an Event to a Public Asset

NOTE: Any Events added to a Public Asset will also be public. Events may only be added by the tenancy that originally created the Public Asset.
  1. Create an Event with your desired attributes. See Creating an Event for detailed instructions.

Select Record Event from the Asset view and fill in the desired details. When finished, click Record Event at the bottom right of the pop-up.

Event Details

Create a JSON file with your desired Event details.

{
  "operation": "Record",
  "behaviour": "RecordEvidence",
  "event_attributes": {
    "arc_description": "Adding new information to public asset.",
    "arc_display_type": "Update",
    "Public Update": "New Information"
  }
}

Use the curl command to run your JSON file. See instructions for creating your BEARER_TOKEN_FILE here.

curl -v -X POST \
    -H "@$BEARER_TOKEN_FILE" \
    -H "Content-type: application/json" \
    -d "@/path/to/jsonfile" \
    https://app.rkvst.io/archivist/v2/assets/<asset-id>/events
  1. Your Event will be readable when the Public Asset link is followed.
Event Listed in Public View
Event Information
  1. You may also retrieve a public URL to the Event itself, using the Assets API.

Edit this page on GitHub