Checks the status of a sign request. Typically used with the sign API module. Because of this, the data used is expected to come from the request. Not an item.
The valve will create an item if...
Checks the status of a sign request. Typically used with the sign API module. Because of this, the data used is expected to come from the request. Not an item.
The valve will create an item if...
Checks the status of a sign request. Typically used with the sign API module. Because of this, the data used is expected to come from the request. Not an item.
The valve will create an item if...
Creates a sign request to the Freja e-ID backend. Typically used with the sign API module. Because of this, the data used is expected to come from the request. Not an item.
The valve will create...
Creates a sign request to the Freja e-ID backend. Typically used with the sign API module. Because of this, the data used is expected to come from the request. Not an item.
The valve will create...
Creates a sign request to the Freja e-ID backend. Typically used with the sign API module. Because of this, the data used is expected to come from the request. Not an item.
The valve will create...
Used when authenticating or signing against Freja eID.
Only QR-code is available when using other device. No user input required by the user. On same device (mobile client) the pattern of...
Overview
To use the API, two methods must be called. The first API method call is to trigger the signing. This will return a signing reference alue. The second API method call will poll the status...
Overview
This article describes how to setup PhenixID Signing Services for local (indirect) signing using Freja eID.
This setup includes the use of Freja OrgID.
Prerequisites
- Freja eID client...
DEPRECATED! Use FrejaEIDAuthRequestValve instead.
Trigger Freja eID authentication. Used in the context of the HTTP API.
On successful execution a new property, 'frejaeidresponse', will be added to...