SigneringV2 service

[HauklandJ]

The signing service is a service for handling any signee assignment, signing and correspondance. Signees can be configured by a user in the policy file by hardcoding the signee role, it can be derived by an implementation of the ISigneeLogic interface, or signees can be added runtime by an app user via GUI.

There are three main use cases for the service - assignment, signing and retrieving signee information.

In assignment, the signees are derived from the possible sources listed above, and the relevant parties are delegated rights to the sign action. The signees are then notified of this via the Altinn Inbox using the Correspondance API.

In signing, the signclient is used to generate and persist a signature, and the app instance owner is notified of which signee has signed.

In reading signee information, the service is called from app-frontend-react via an endpoint and returns a list of spefic people expected to sign, which role is expected to sign, or both.

SigningService - use case

Based on the implementation(s) of the interface for signee logic, calls ActionAccessDelegationService to grant access for the relevant parties.

public
List GetSignees (reads from storage)
SetSigneesResult SetSignees (store who signees are, give access and send notifications)

private
SetSigneeResult SetSignee ( give access and send notification to single signee)

• Do we keep state about which grant access and send notification requests that succeeded/failed, so that we don't do it again?
• Exponential back-off retries? Generalized solution for this?

Order:

1. Store signee in storage
2. Give access rights
3. Send notification