Connective Signing Providers
Two connective identity providers need to be configured to allow a fully functioning feature.
ConnectiveSigningProviderConnectiveScheduledProvider
- Signing Provider V2
- Signing Provider
- Scheduled Provider
🎯 Functional documentation
Connective as a signing provider allows counterparties in the flow to provide an advanced signature using BE-ID, SMS-code, itsme or manual signing. The provider also generates a specific signature stamp on the document depending on the configured signing types.
⚙️ Configuration
resourceUri:https://harmoney-test.connective.eu/esig/webportalapi/v4
Settings Configuration
Examples
Implementation classes
ConnectiveV2SigningProvider
Custom signing method
In addition to the standard signing types (EID, MANUAL, SMS, ITSME, EMAIL), Signing Provider V2 supports provider-specific signing methods that are not covered by the built-in options.
To use a custom signing method:
- Add
CUSTOM_METHODtoSIGNING_TYPES. - Set
customSigningMethodto the exact Connective API method string for that method.
:::note Validation rules
customSigningMethod is required when CUSTOM_METHOD is listed in SIGNING_TYPES, and must not be set when CUSTOM_METHOD is absent from SIGNING_TYPES.
:::
🎯 Functional documentation
Connective as a signing provider allows counterparties in the flow to provide an advanced signature using BE-ID, SMS-code, itsme or manual signing. The provider also generates a specific signature stamp on the document depending on the configured signing types.
⚙️ Configuration
resourceUri:https://harmoney-test.connective.eu/esig/webportalapi/v4
Settings Configuration
Examples
Implementation classes
ConnectiveSigningProvider
🎯 Functional documentation
The scheduled provider must be configured to allow a scheduled data removal of orphan documents. For example, signatures that were initiated on the Connective platform, but were never finalized, must be deleted. Since the user aborted the signing process, a separate provider is necessary to perform the cleanup. All documents older than 7 days are removed.
⚙️ Configuration
Required authorization settings
Same as for the signing provider.
Implementation classes
ConnectiveScheduledProvider
Settings
- CRON_SCHEDULE Example
{
"CRON_SCHEDULE": "0 23 * * *"
}