MitID Integration - Revision history

Tvi: Added Signer.StatusUploaded

2024-09-05T13:40:31Z

Added Signer.StatusUploaded

← Older revision		Revision as of 15:40, 5 September 2024
Line 93:		Line 93:
	\|Signer.StatusSigned		\|Signer.StatusSigned
	\|Status that the record should enter when all signatures are collected. Defaults to 0.		\|Status that the record should enter when all signatures are collected. Defaults to 0.
			\|-
			\|Signer.StatusUploaded
			\|Status that the record should enter when it has been uploaded to signing service. Defaults to 0.
	\|-		\|-
	\|Signer.StatusDisableCodeunits		\|Signer.StatusDisableCodeunits

Tvi: /* Configurations */

2023-08-09T09:41:28Z

Configurations

← Older revision		Revision as of 11:41, 9 August 2023
Line 93:		Line 93:
	\|Signer.StatusSigned		\|Signer.StatusSigned
	\|Status that the record should enter when all signatures are collected. Defaults to 0.		\|Status that the record should enter when all signatures are collected. Defaults to 0.
			\|-
			\|Signer.StatusDisableCodeunits
			\|Whether codeunits should be executed or not, when the signing completes or fails. Defaults to false (do execute).
	\|-		\|-
	\|Signer.EmailSubject		\|Signer.EmailSubject

Tvi: Generator info

2023-05-09T12:06:45Z

Generator info

← Older revision		Revision as of 14:06, 9 May 2023
Line 52:		Line 52:

	=== Document signing ===		=== Document signing ===
	To start the signing process, setup the configuration and execute a Status Action that executes the codeunit <code>dk.tempusserva.signing.criipto.CriiptoStatusAction</code> or access a url with <code>command=dk.tempusserva.signing.criipto.CriiptoPage&SagID=[SagID]&DataID=[DataID]</code> (not ready).		To start the signing process, setup the configuration and execute a Status Action that executes the codeunit <code>dk.tempusserva.signing.criipto.CriiptoStatusAction</code> or <code>dk.tempusserva.signing.criipto.CriiptoStatusActionGenerator</code> or <code>dk.tempusserva.signing.criipto.CriiptoStatusActionGeneratorAlt</code> or access a url with <code>command=dk.tempusserva.signing.criipto.CriiptoPage&SagID=[SagID]&DataID=[DataID]</code> (not ready).

	This will try to lookup and send the document(s) out for signing.		This will try to lookup and send the document(s) out for signing.
Line 74:		Line 74:
	\|-		\|-
	\|Signer.FieldFil *		\|Signer.FieldFil *
	\|System name for the field with documents that should be send, all documents found here will be send. Defaults to "FILES".		\|System name for the field with documents that should be send, all documents found here will be send. Defaults to "FILES". Also used to store generated files.
	\|-		\|-
	\|Signer.FieldCPR		\|Signer.FieldCPR
Line 129:		Line 129:
	\|Signer.OverwriteOnReupload		\|Signer.OverwriteOnReupload
	\|true/false, default false. If enabled the system allows re-sending a record for signing, overwriting the old one.		\|true/false, default false. If enabled the system allows re-sending a record for signing, overwriting the old one.
			\|-
			\|Signer.FileName
			\|Name of generated file, defaults to kontrakt.docx, used by CriiptoStatusActionGenerator
			\|-
			\|Signer.TemplateID
			\|ID of template to be rendered and saved before sending it of to be signed, used by CriiptoStatusActionGenerator
			\|-
			\|Signer.FileNameAlt
			\|Name of generated file, defaults to kontrakt.docx, used by CriiptoStatusActionGeneratorAlt
			\|-
			\|Signer.TemplateIDAlt
			\|ID of template to be rendered and saved before sending it of to be signed, used by CriiptoStatusActionGeneratorAlt
	\|}		\|}

Tvi at 15:09, 13 March 2023

2023-03-13T15:09:42Z

← Older revision		Revision as of 17:09, 13 March 2023
Line 30:		Line 30:

	=== Document signing ===		=== Document signing ===
			Requires version 7336 or newer.

	Head to "Application" in the Criipto menu, click "Add signatures application" (if it excists), otherwise click "Add login application" and add <code>?tags=signatures</code> to the end of the url.		Head to "Application" in the Criipto menu, click "Add signatures application" (if it excists), otherwise click "Add login application" and add <code>?tags=signatures</code> to the end of the url.

Line 37:		Line 39:

	== Setup in TS ==		== Setup in TS ==
	There are 25 parameters available. Some of these must be set for the integration to work, depending on the integration.		There are a lot of parameters available. Some of these must be set for the integration to work, depending on the integration.

	=== Sign in ===		=== Sign in ===

Tvi: /* Configurations */

2023-03-13T09:16:54Z

Configurations

← Older revision		Revision as of 11:16, 13 March 2023
Line 81:		Line 81:
	\|-		\|-
	\|Signer.FieldEmail *		\|Signer.FieldEmail *
	\|System name for the field with an email, that will be notified about the signature request. Also used with MultipleSigners.		\|System name for the field with an email, that will be notified about the signature request. Also used with MultipleSigners. Defaults to "EMAIL".
	\|-		\|-
	\|Signer.FieldSigners		\|Signer.FieldSigners
Line 124:		Line 124:
	\|Signer.CriiptoClientSecret *		\|Signer.CriiptoClientSecret *
	\|The client secret from Criipto application.		\|The client secret from Criipto application.
			\|-
			\|Signer.OverwriteOnReupload
			\|true/false, default false. If enabled the system allows re-sending a record for signing, overwriting the old one.
	\|}		\|}

Tvi: Created the page

2023-03-02T11:12:05Z

Created the page

New page

== What it does ==
We have a generic integration to Criipto (a MitID, and other eID, broker) and an account, allowing for sign in and document signing with MitID/nemID.

=== Sign in ===
Sign in can be setup as a webinterface or as SSO from the login-page (not fully supported yet), the authentication method isn't available in the dropdown for the webinterface, as of writing, it has to be set through the database (the live database).<syntaxhighlight lang="mysql">
UPDATE forminterface SET AuthenticationType = 5 WHERE InterfaceID = [ID];
</syntaxhighlight>

=== Document signing ===
One or multiple documents can be send for signature, one or more people can sign the batch and it is possible to enforce CVR or CPR. This process can be initiated from a StatusAction or be accessing a url.

A page is appended to the signed documents showing who signed it and when, in the order they signed it.

== Prereq ==
To setup this an "Application" has to be set up in Criipto, one for sign in and one for signatures, and a CNAME dns-record has to be created.

The ID's and secrets created here will be needed later.

== Setup in Criipto ==
First, a domain has to be added.

Haed to the Criipto Dashboard, select "Domains" in the menu, make sure that you are in "Production", click "Add production domain".

Name it <code>[customer]-eid.tsnocode.com</code> and head to CloudFlare and add a CNAME record that points to <code>idp.criipto.id</code>.

Once the domain is active you can progress.

=== Sign in ===
Coming

=== Document signing ===
Head to "Application" in the Criipto menu, click "Add signatures application" (if it excists), otherwise click "Add login application" and add <code>?tags=signatures</code> to the end of the url.

Name the application <code>[customer] eSign</code>, select their domain and check the eID's that should be available, select <code>java</code> as technology.

A secret might pop up or be shown, take note. It is possible to add more after the fact and re-issue them.

== Setup in TS ==
There are 25 parameters available. Some of these must be set for the integration to work, depending on the integration.

=== Sign in ===
Coming

===== Policies =====

* oauthCriiptoAllow
* oauthCriiptoHost
* oauthCriiptoClient
* oauthCriiptoSecret

=== Document signing ===
To start the signing process, setup the configuration and execute a Status Action that executes the codeunit <code>dk.tempusserva.signing.criipto.CriiptoStatusAction</code> or access a url with <code>command=dk.tempusserva.signing.criipto.CriiptoPage&SagID=[SagID]&DataID=[DataID]</code> (not ready).

This will try to lookup and send the document(s) out for signing.

==== Configurations ====
{| class="wikitable"
!Configuration
!Description
|-
|Signer.MultipleSigners
|Whether multiple signers is allowed (true/false)
|-
|Signer.MaximumSigners
|How many signatures are needed. Defaults to "COUNT", which counts the number of signers, when using MultipleSigners, otherwise 1. Can otherwise be set to a number.
|-
|Signer.ExpiresInDays
|Number of days the recipient has to sign the document. Default is 30.
|-
|Signer.FieldMaximum
|Not implemented
|-
|Signer.FieldFil *
|System name for the field with documents that should be send, all documents found here will be send. Defaults to "FILES".
|-
|Signer.FieldCPR
|System name for the field with a CPR, that the signer has to have to sign the document. Also used with MultipleSigners.
|-
|Signer.FieldCVR
|System name for the field with a CVR, that the signer has to have to sign the document. Also used with MultipleSigners.
|-
|Signer.FieldEmail *
|System name for the field with an email, that will be notified about the signature request. Also used with MultipleSigners.
|-
|Signer.FieldSigners
|System name for a list-of-children-field. All records found here will be required to sign the document. Required when using MultipleSigners.
|-
|Signer.StatusError
|Status that the record should enter if the signature request failed (was rejected or timed out). Defaults to 0.
|-
|Signer.StatusSigned
|Status that the record should enter when all signatures are collected. Defaults to 0.
|-
|Signer.EmailSubject
|The subject of the email send to the signer. Defaults to "Dokument til signering".
|-
|Signer.EmailBody
|The email-body of the email send to the signer. Defaults to "Du kan underskrive her: {LINK}".
|-
|Signer.NotificationSubject
|The subject of the email send to EmailWarner, when all signatures have been collected. Defaults to "Dokument til signering er blevet underskrevet"
|-
|Signer.NotificationBody
|The body of the email send to EmailWarner, when all signatures have been collected.
Defaults to "Alle parter har nu underskrevet dokumentet. {LINK}". Links to the record.
|-
|Signer.NotificationBodyExt
|The body of the email send to all signers of a document, when all have signed.
Defaults to "Alle parter har nu underskrevet dokumentet. Du kan downloade det underskrevne dokument her: {LINK}". Links to the signed document at Criipto.
|-
|Signer.EmailWarner
|Can be an email or the system name of a field containing an email.
The email found here will be notified when a signature fails and completes. If an email is not found, the email of the current user will be used, if not a status action. Required for status action.
|-
|Signer.WarningSubject
|The subject of the email send to EmailWarner, when a signature request fails. Defaults to "Dokument til signering blev afvist".
|-
|Signer.WarningBody
|The body of the email send to EmailWarner, when a signature request fails. Defaults to "En underskrift blev afvist. {LINK}". Links to the record.
|-
|Signer.CriiptoClientID *
|The client ID from Criipto application.
|-
|Signer.CriiptoClientSecret *
|The client secret from Criipto application.
|}