TODO
-
Communication with OCM (link to the epic https://code.vereign.com/gaiax/ocm/proof-manager/-/issues/14)
-
@yordan.kinkov Rego extensions using OCM client and deciding how to build OCM query
-
@yordan.kinkov Modify the GetLoginProofInvitation and GetLoginProofResult policies to substitute mocks with the actual OCM calls
-
@kalin.canov add additional credential type to the attestation manager
-
@kalin.canov modify getPresentationID details
-
- @lyuben.penkovski create extensions for signing with Vault (getting public keys is more important functionality to generate did document inside of the policy) @valerii.kalashnikov check the requirements
- (Bug) Sync task templates and task list with Git and Mongo
- (Bug) Synching repo with incorrect file structure creates incorrect records in database after synchronisation. Expected having an error during synchronisation process in case of incorrect file structure
- Performance tests
- Persistence policies
- Crypto libs to work with ursa (sign, key management)
- Policy to generate an endpoint in Kong
- Resolving DID asynchronously
- Handling gone state of every task execution
- Sign trusted information export with OCM option
- review next week (31st May) the
Featurelist and more specifically https://code.vereign.com/gaiax/tsa/tests/-/blob/main/features/trustedInfoExport.feature
High priority
TSA tasks
- develop extension for Vault transit signing interface
- @yordan.kinkov Modify Golang OCM client for requesting multiple types. - We can start working on while the change for on the proof manager are in develop. So both task can be develop in parallel.
OCM
-
@suneet.aw Principal credential type in side of the in OCM and the credDef needs the same fields as lissi GAIA-X employee credential form registration page. But the name should be
Principal credentialin the OCM. - this can be developed in parallel -
@kalin.canov Update the proof manager to accept multiple cred def attribute - its in progress. The endpoint will be the same , just adding option for more parameters.
Test integration flow AA - OCM - TSA
Requirement
- PCM - with trusted connection with OCM
- OCM should issue 3 credentials to PCM -
VC
-
Principal
- registration fields
-
University,
- first name
- degree
-
Email scope
Mapping from scopes to credential type - exist already
- mapping between the AA fields and OCM via policy @suneet.aw to send the attribute names to @yordan.kinkov , then Dancho will transform these attributes to map the AA attributes . The transformation needs to happen in rego policy.
Low priority
- generate DID document(thats after the TSA get an access to Vault) - wish list (low priority)
- deploy KONG or ISTIO? - this will be discussed in the next weeks
- Add a plugin to the signer service for signing/verifying through the OCM - Low priority
- Implement policies export / import (IDM.TSA.00028, IDM.TSA.00028) ??? - Low priority
- Trusted Identity Information (IDM.TSA.00053) ??? - query the cache (dataGrid) with specific scope/parameters
- make an extension for OCM signing interface - OCM needs to provide few more endpoint. And needs further thinking where we really need this.