feat(agent): enable parsing of enterprise invitation and add prism agent

[goncalo-frade-iohk]

Fixes ATL-2497

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ REPOSITORY	checkov	yes		no	10.03s
✅ REPOSITORY	dustilock	yes		no	0.02s
✅ REPOSITORY	gitleaks	yes		no	4.45s
✅ REPOSITORY	git_diff	yes		no	0.16s
✅ REPOSITORY	secretlint	yes		no	2.37s
✅ REPOSITORY	syft	yes		no	0.56s

See errors details in artifact MegaLinter reports on CI Job page
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by

[goncalo-frade-iohk]

@milosh86 @elribonazo this is the parsing for the invitation request like this:

{
    "@type": "https://atalaprism.io/did-request",
    "onboardEndpoint": "https://demo.atalaprism.io:8085/onboard/uuid-1234-7273-1878",
    "from": "Government Issuer"
  }

And it returns an object prism onboarding object.

[goncalo-frade-iohk]

@milosh86 @elribonazo This is a very simple method to just get that parsed object returned previously and send the DID to the endpoint

[rodolfomiranda]

@goncalo-frade-iohk . Just to clarify. For DIDComm OOB invitations you use DID Peers. For Prism Invitations, do you use DID Peer or DID Prism?

[goncalo-frade-iohk]

That is a good question and something I asked and still require clarification. But the initial conclusion is we use DIDPeer as well

[yshyn-iohk]

just wonder, which default parameters for signing do we use here?

[goncalo-frade-iohk]

In this case there are no default parameters.

The Agent is always initiated with a valid Seed as requirement, this function signWith(did: DID, message: Data) has DID and the message bytes as parameters.

What the Agent is going to do is check if the DID information ( in this case the KeyPairIndex) was persisted before, return it from the database and create the DID private key with Seed+KeyPairIndex to then sign the message.