Weekly meeting 08/05/23

Owned by sasi
Last updated: May 10, 2023
2 min read

Attendees

  •  Jurgen, Sasikumar

Meeting Presentation

 

 

Meeting Recording

GovStack- e-signature BB- Weekly Call

 

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Review the Yaml file

Jurgen

Review and discuss the abilities.

 

 

 

 

 

 

 

 

 

 

Action Items

Ask Ramkumar about the format and how to finalize the scoping document.
@Jürgen Niinre Add a new sequence diagram for onboarding in QSCD.
@Jürgen Niinre Add a new sequence diagram with payment.
@Jürgen Niinre Add a new sequence diagram for redirection from registration BB.
uniquePseudonym , needs more discussion. unique per person or unique globally?
Finalised to have this as one per certificate.
Finalized unique globally
@Jürgen Niinre create cert should have proper error codes.
get the status out of the way for the list API.
patch API should have to request JSON as Suspend, Revoke, Active. Revoked certificates can not be moved to active. @Jürgen Niinre to change.
we should have query enum (ALL, SUSPENDED, EXPIRED, REVOKED), request enum (SUSPEND, REVOKE), response enum (SUSPENDED, EXPIRED, REVOKED)
can we create two sign API’s? One with certificate id and another with pseudonym
add a timestamp in all the API’s both in request and response.
add the support for one-time signature in the sign API.
Open issue to be filed for
Currently, we have no way to validate the app. We will introduce the V2 version of the create API with this feature.
Sign API should have certid or pseudonym
Documentation
terminology is to be updated with the proper acronym.
Key digital functionalities - Fix the sentences
Cross-cutting any changes - @sasi to do.
Functional requirement - pick it from the scope document in confluence. alter the sequence diagram to match today's discussion of downloading the app and initiating the QSCD onboarding.
Internal workflow to be created.
It was noted that the Sign API’s with pseudonym and certid needs to change using redirect as they could leak information to the relying party.

Decision

 

Changes needed in the YAML.