Fix issuance options after rebase, add security to endpoint xml.

w3c-ccg · Mar 26, 2024 · afcb511 · afcb511
1 parent ec5daed
commit afcb511
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 6 deletions.
diff --git a/components/IssueCredentialOptions.yml b/components/IssueCredentialOptions.yml
@@ -20,12 +20,6 @@ components:
         created:
           type: string
           description: The date and time of the proof (with a maximum accuracy in seconds). Defaults to current system time.
-        challenge:
-          type: string
-          description: A challenge provided by the party requesting the proof. For example, 6e62f66e-67de-11eb-b490-ef3eeefa55f2
-        domain:
-          type: string
-          description: The intended domain of validity for the proof. For example, website.example
         mandatoryPointers:
           type: array
           items:

diff --git a/verifier.yml b/verifier.yml
@@ -79,6 +79,10 @@ paths:
   /challenges:
     post:
       summary: Passing an empty body to this endpoint creates and returns a challenge string in the response body.
+      security:
+       - networkAuth: []
+       - oAuth2: []
+       - zCap: []
       operationId: challenge
       description: Creates a challenge to be used as `options.challenge` in future requests.
       responses: