Signicat Connector ¶
Author: Peter Holko (peterholko@pingidentity.com)
Introduction ¶
The Signicat DaVinci connector redirects to the Signicat Identity Broker service which is a cloud platform where organisations can easily integrate a large number of ID methods via a simple user interface.
Setup ¶
Resources ¶
For information and setup help, see the following sections of the Signicat documentation and lick on OpenID Connector tab: https://developer.signicat.com/express/docs/identification/guides/quick-start/#get-started
Requirements ¶
To use the connector, you'll need:
- A configured Signicat tenant
- A Signicat user account to test authentication
Setting up the Signicat connector configuration ¶
In DaVinci, add the Signicat connector. For help, see Adding a connection.
Connector settings ¶
Signicat provides an OpenId Connect (OIDC) Identity Provider API. Default values are provided for OIDC settings where appropriate.
To obtain a Client ID and Client Secret create a OIDC client in the Signicat Dashboard. The DaVinci redirect URI is available on the Signicat Connector configuration screen which must be configured in the Signicat Dashboard.
Client ID ¶
The OIDC Client ID. This value is provided during the Signicat OIDC client creation.
Client Secret ¶
The OIDC Client Secret. This value is provided during the Signicat OIDC client creation.
Redirect URL ¶
This value is generated automatically by Davinci. It must be copied to the Signicat OIDC client in the Signicat Dashboard.
Issuer URL ¶
OIDC Issuer Identifier for your Signicat tenant.
Authorization Endpoint ¶
OIDC Authorization Endpoint for your Signicat tenant.
Token Endpoint ¶
OIDC Token Endpoint for your Signicat tenant.
User Info Endpoint ¶
OIDC UserInfo Endpoint for your Signicat tenant.
Send state with request ¶
When enabled, Davinci will auto-populate a random value to pass as the OIDC state parameter. This is enabled by default, but can be disabled if you want to provide a custom state as a query parameter in your flows.
If disabled, your flows should provide an alternative state as a query parameter.
Most deployments should not need to change this from the default value.
Using the connector in a flow ¶
Authenticating users with Signicat ¶
In your flow, perform the following steps (note the example below provides a login_hint query parameter to Signicat):
- Add the Signicat Connector.
- Next in your flow, add the Signicat Connector.
- Configure the Signicat node:
- Under Query Parameters, click + to add a parameter.
- Enter
login_hintfor the Key. - For the Value, click {} and select the
userNameoutput variable from your HTML Form above. - Click Apply.
-
Show the result of Signicat authentication
-
Next in your flow, add the HTTP connector and select the Custom HTML Message capability.
Note: In a production authentication flow, you will redirect the user to the resource they were attempting to access. In this demonstration flow, we'll just show the response from Signicat.
-
Configure the Custom HTML Message node:
- Choose a Title, such as
Sign in complete. - In Message, click {} and select the output variable from your Signicat Connector node by clicking +.
- Click Apply.
- Choose a Title, such as
-
Test the flow
-
Click Save, Deploy, and then Run.
- On the Sign in page, enter the username of your Signicat test user account. Click Continue. The browser will redirect to Signicat login.
- Log in with Signicat.
- On success, the browser redirects back to DaVinci. Your Custom HTML Message shows the result from Signicat.
For additional help, see the Creating an authentication flow guide.
Capabilities ¶
Authenticate with Signicat (loginFirstFactor) ¶
Redirects to Signicat via OIDC