@@ -53,16 +53,18 @@ See [Signed Statement Issuance and Registration](https://datatracker.ietf.org/do
53
53
** Required** The name of the issuer, set to ` CTW_Claims:iss ` .
54
54
See [ Signed Statement Envelope] ( https://datatracker.ietf.org/doc/html/draft-ietf-scitt-architecture#name-signed-statement-envelope ) .
55
55
56
- ## Example usage
56
+ ## Example Usage
57
57
58
- The following example shows a minimal implementation.
58
+ The following example shows a minimal implementation for registering SCITT Signed Statements .
59
59
60
60
Three GitHub Action Secrets are used:
61
61
62
62
- ` secrets.DATATRAILS_CLIENT_ID `
63
63
- ` secrets.DATATRAILS_CLIENT_SECRET `
64
64
- ` secrets.SIGNING_KEY `
65
65
66
+ ### Registering Signed Statements
67
+
66
68
Sample github ` action.yaml `
67
69
68
70
``` yaml
@@ -128,6 +130,20 @@ jobs:
128
130
rm ./signingkey.pem
129
131
` ` `
130
132
133
+ ### Querying DataTrails Events
134
+
135
+ Registered SCITT Statements are available as [DataTrails Events][datatrails-events].
136
+
137
+ > **NOTE**: As the [SCITT Reference API][scrapi] queries mature, additional DataTrails SCITT Query APIs will be made available.
138
+
139
+ Using the ` SUBJECT` from above, query all DataTrails Events (SCITT Registered Statements).
140
+
141
+ ` ` ` bash
142
+ SUBJECT="synsation.io/myproduct-v1.0"
143
+ curl https://app.datatrails.ai/archivist/v2/publicassets/-/events?event_attributes.subject=$SUBJECT \
144
+ | jq
145
+ ` ` `
146
+
131
147
# # Testing Action Updates
132
148
133
149
To test incremental changes to this github action :
@@ -142,3 +158,6 @@ To test incremental changes to this github action:
142
158
uses: synsation-corp/scitt-action@featurebranch
143
159
uses: synsation-corp/scitt-action@5b861ed4722787835cdd5e9d86efc698974f1131
144
160
` ` `
161
+
162
+ [datatrails-events] : https://docs.datatrails.ai/developers/api-reference/events-api/
163
+ [scrapi] : https://datatracker.ietf.org/doc/draft-ietf-scitt-scrapi/
0 commit comments