Registering the Signer Printer in GrantID
The Signer Printer is a Windows app that sends documents to Signer from the Print dialog of any program. People sign in to it with the same GrantID account they use for the Signer web app.
For that to work, the GrantID tenant behind your Signer instance needs one more application: the Signer Printer's sign-in registration. It is made once, by hand, in the GrantID console. Until it exists, the Signer Printer says the instance isn't ready and points people to this page.
Requirements
- Signer 2.11.0 or later.
- GrantID 4.6.0 or later. It is the first release that can register an application without a client secret.
Who can make it
An Administrator of the GrantID subscription that holds the Signer web app's application.
GrantID releases before 4.11.0 check a looser permission, so a Manager of the subscription can also create applications there. Even so, the person who makes this registration should be the one who looks after the Signer web app's sign-in rules, since the two must stay the same (see below).
A second door into the same Signer
The sign-in registration is a second door into the same Signer. Anyone who signs in through it can send documents as themselves, just as in the web app. So it must carry the same sign-in rules as the Signer web app's application: second factor, digital certificate login, required and verified e-mail, required phone, lockout, required claims.
A new GrantID application starts with none of these rules, and nothing in GrantID keeps the two applications in step. Whenever you tighten the web app's sign-in rules, tighten this registration's too.
The second factor matters most. It is on its own tab and can only be seen and set in the console.
Before you start
Find two values from your Signer instance. Open https://<your Signer>/api/configuration in a browser (no sign-in needed) and note:
clientId: the App-Id of the Signer web app's application, for examplesigner. The Signer Printer's App-Id is this value followed by-printer, for examplesigner-printer.apiName: the Signer API scope, for examplesigner-api.
Then, in the GrantID console, open the Signer web app's application (the App-Id equal to clientId) and keep it open in another tab. You will copy several settings from it.
Creating the registration
Creating the application takes two saves. After the first, the application already exists, but with a client secret required and no redirect address, so nobody can sign in through it yet. Carry on to the second save straight away.
1. Create the application
In the GrantID console, open the subscription and create a new application:
| Field | Value |
|---|---|
| Name | Lacuna Signer Printer |
| App-Id | the clientId followed by -printer, for example signer-printer |
| Type | Code flow |
Save. The application opens.
2. The Settings tab
Set these values on the Settings tab. Labels are the console's.
| Setting | Value |
|---|---|
| Require Client Secret? | off |
| Require PKCE? | on |
| Allow offline access? | on |
| Require consent? | on |
| Allow access tokens via browser? | off |
| Access Token Type | JWT |
| Access Token Lifetime | 3600 seconds |
| Refresh token expiration type | Sliding |
| Sliding refresh token lifetime | 7776000 seconds (90 days without use ends the session) |
| Refresh Token Lifetime | 31536000 seconds (one year at most) |
| Refresh token usage | One time |
| Redirect | the three addresses below, exactly as written |
| Post Logout, CORS Origins, Application Url, Logo Url | empty |
| Allowed API Scopes | the apiName from /api/configuration |
| Allowed Identification Scopes | the same as the Signer web app's application |
The three redirect addresses, one per line, exactly as written:
http://127.0.0.1:43873/callback
http://127.0.0.1:43874/callback
http://127.0.0.1:43875/callback
GrantID compares redirect addresses character by character, so any difference (localhost instead of 127.0.0.1, a trailing /) stops sign-in.
You may set shorter token lifetimes if your organization requires it. The Signer Printer copes with any.
The two switches "Front-channel logout session required?" and "Back-channel logout session required?" can stay at their default. The registration has no logout addresses, so they have no effect.
3. The sign-in options
Copy each of these from the Signer web app's application. They are in three places in the console:
- Login Options, on the Settings tab: digital certificate login (enable, prioritize, require), disable password login, password input mode, e-mail required and verified, phone required and verified, disable sign-up on the login page, external identity providers, and required claims.
- Enable user lockout?, under General Settings on the Settings tab.
- The second factor, on its own tab, Authentication Factors.
Save the Settings tab, then save the Authentication Factors tab.
A new application's defaults are all off. On one Signer instance, five of these had to be changed to match the web app: user lockout, digital certificate login, e-mail required, e-mail verified and phone required. Check every one rather than assuming the defaults match.
Checking it
Reload the application in the console and check every value against the tables above. Then sign in from the Signer Printer: the browser opens GrantID's sign-in page, and after signing in a consent page names "Lacuna Signer Printer".
Changing it later
Keep the values on this page as they are. Every Signer Printer depends on them, and a later release only asks for a change if it cannot avoid one; its release notes will say so.
The one change that is always yours to make: when the Signer web app's sign-in rules change, make the same change here.