Service Desk Verification From ServiceNow

The Verify User feature in each user record provides an authentication workflow within the ServiceNow app, when your IT service desk must confirm a caller's identity before providing support. This protects against social engineering attacks where a bad actor impersonates a legitimate user.

To configure Service Desk Verification from within the Imprivata Admin Console, see Service Desk Verification From Imprivata.

Overview

This configuration requires administrators working in both systems, in alternating stages:

  • The ServiceNow administrator, working in the ServiceNow instance, Installing the application, creating a signing key, and configuring the application;

  • The Imprivata administrator, working in the Imprivata Hub, creating the identity verification integration.

Imprivata needs the ServiceNow public key URL before the integration can be created, and ServiceNow needs the client ID that creating the integration produces:

  1. ServiceNow — Install the Imprivata application

  2. ServiceNow — Create the signing key and publish the JWKS endpoint

  3. Imprivata — Create the identity verification integration

  4. ServiceNow — Configure the application with the values from Stage 3, above

  5. ServiceNow — Grant roles and enable email

  6. Both — Verify the setup

Imprivata Requirements

  • The Advanced and Passwordless Access license.

  • A connection to the Imprivata Cloud Platform.

  • Your SMTP server must be specified to send email to users.

  • Staff answering calls to the service desk who need to use this feature must have access to ServiceNow.

ServiceNow Requirements

  • A ServiceNow administrator account, with the ability to elevate to security_admin.

  • Outbound email enabled on the ServiceNow instance

  • The ServiceNow instance reachable from the Internet so Imprivata can fetch its public key.

  • OpenSSL and a terminal (see Stage 2).

  • Service desk callers you intend to verify must have an email address on their ServiceNow user record, and must have notifications enabled.

Stage 1 — Install the Imprivata Application in ServiceNow

  1. Download Imprivata Identity Verification for ServiceNow and install it on your ServiceNow instance.

  2. Note the application's scope name, shown on the application record. Every property and role below is prefixed with it. This topic writes it as <scope>.

    NOTE:

    There is no risk in installing the application before you are ready to configure it. The application installs inactive: it cannot send a verification link or accept a result until Stages 2 through 5 are complete.

Stage 2 — Create the Signing Key and Publish the JWKS Endpoint

ServiceNow authenticates to Imprivata with a digital signature rather than a shared password. Generate a key pair, keep the private half inside ServiceNow, and publish the public half at a URL that Imprivata reads.

2.1 Generate the Key Pair

Run these commands on your workstation, in a directory outside any source repository:

  1. Generate a 2048-bit private key

    openssl genrsa -out private-key.pem 2048

  2. Create a self-signed certificate

    openssl req -new -x509 -key private-key.pem -out certificate.pem -days 3650 \

      -subj "/CN=ServiceNow Caller Verification"

  3. Package both into a PKCS#12 keystore

    openssl pkcs12 -export -inkey private-key.pem -in certificate.pem \

       -out keystore.p12 -name snidv

IMPORTANT:

Choose a strong keystore password when prompted and record it somewhere safe — you need it twice in Stage 2.3 and nowhere else.

2.2 Create the Public Key Document

Convert the public half of the key into a JWKS document. Keep the resulting file; you paste its contents in Stage 2.4.

IMPORTANT:

After this step, delete private-key.pem. ServiceNow holds the key inside the keystore, a copy of a private key on a workstation is a liability.

2.3 Load the Keystore Into ServiceNow

  1. Elevate your session to security_admin first: click your avatar, then Elevate role.

  2. Go to System Definition > Certificates and click New.

  3. Set Type to Java Key Store.

    IMPORTANT:

    Set the type to Java Key Store, not PKCS12 Key Store. The file you generated is PKCS#12, but the certificate record must be of type Java Key Store. The keystore picker in the next step accepts only that type, and a record saved as PKCS12 Key Store cannot be selected there.

  4. Enter a Name, attach keystore.p12, and enter your keystore password in Key store password.

  5. Click Save.

  6. Go to System OAuth > JWT Keys and click New.

    • Name — any recognizable name.

    • Signing Keystore — the certificate record you just created.

    • Key Id — leave blank.

    • Signing Algorithm — RSA 256.

    • Signing Key — the same keystore password.

  7. Click Save.

  8. Go to System OAuth > JWT Providers and click New.

    • Name — any recognizable name.

    • Signing Configuration — the JWT Keys record from above.

    • Expiry Interval (sec) — 60.

    • JWT API Script — leave blank.

  9. Click Save.

  10. With the provider record open, copy its sys_id from the browser address bar. You need it in Stage 4. After saving, the provider shows a Standard Claims list with empty aud, iss and sub rows. Leave them empty — the application builds its own claims.

2.4 Publish the Public Key

Go to System Properties and set <scope>.jwks to the entire contents of your JWKS document from Stage 2.2.

IMPORTANT:

Paste it using a method that does not reflow text — a paste through a soft-wrapping editor window can insert whitespace into the key, which produces an authentication failure that is very hard to diagnose.

2.5 Confirm Both Public Endpoints

  1. The application exposes two URLs that must be reachable without signing in. Check them from a logged-out browser or a different machine.

    URL Expected result
    https://<instance>.service-now.com/api/<scope>/verify/jwks

    Your JWKS document

    https://<instance>.service-now.com/api/<scope>/verify/callback

    A response, not a login page

  2. Send both URLs to your Imprivata administrator for Stage 3. Label them clearly:

    Send as Value
    JWKS URI

    https://<instance>.service-now.com/api/<scope>/verify/jwks

    Redirect URI

    https://<instance>.service-now.com/api/<scope>/verify/callback

    IMPORTANT:

    Send the redirect URI exactly as it appears. ServiceNow answers on both /verify/callback and /verify/v1/callback. Imprivata matches the value exactly, so if the registered form and the form the application sends differ, every verification fails. Pick one form and use it consistently.

Stage 3 — Create the Integration in Imprivata Hub

Performed by the Imprivata administrator, using the two URLs from Stage 2.5.

  1. In Imprivata Hub, go to Global settings > Integrations > Identity verification.

    The Identity verification integrations page lists any existing integrations with their type, redirect URIs and client ID.

  2. Click Add integration > ServiceNow identity verification.

  3. Choose a Display name that identifies the customer and instance, for example Memorial Health — production.

    This is shown only to Imprivataadministrators, never to a caller.

  4. Authentication — Enter the JWKS URI from Stage 2.5. Private-key JWT requires a JWKS URI. Imprivata does not store a shared secret.

  5. Enter the Redirect URI from Stage 2.5, exactly as sent. This is where users return after identity verification. Use Add another redirect URI if more than one is needed.

  6. Click Save.

  7. The Integration created dialog appears, confirming the integration. This dialog includes the Client secret, client ID, and endpoints you will provide to the system you're integrating with.

    Shown As Send To ServiceNow As
    Client ID

    The client_id property

    Authorization endpoint

    The authorize_url property

    Token endpoint

    The token_url property

    IMPORTANT:

    Copy and store the client secret now. It won't be shown again after you close this window.

  8. Click Done. This new integration is now listed on the OIDC integrations page.

    All three values remain available. To see them again, find the integration in the list, click the menu on its row, and choose Edit. The Client ID and both endpoints are shown read-only, with copy buttons, below the editable fields. Use the same Edit dialog to change the JWKS URI or redirect URIs if needed.

    There is no client secret to issue or record. Imprivata does not store a shared secret for this integration — authentication relies entirely on the key you published in Stage 2.

What to Send Back to the ServiceNow Administrator

Value Where it comes from
Client ID The Integration created dialog
Authorization endpoint

The Integration created dialog, copied whole

Token endpoint

The Integration created dialog, copied whole

Issuer URL

Not shown in the portal — see below

Environment Integration or production — state it explicitly
  1. Copy the two endpoints exactly as shown, including the case of the tenant name. Do not retype them or adjust them to match the address of the Imprivata Hub you are signed into.

    The issuer URL is the one value the portal does not display. The ServiceNow administrator needs it for the jwt_audience property. It is the address of the tenant itself, which is the first part of the two endpoints you just copied — take either endpoint URL and remove the path:

    Token endpoint https://YOURTENANT.sys.example.imprivata.cloud/idp-web/oidc/token

    Issuer URL https://YOURTENANT.sys.example.imprivata.cloud

    Keep the scheme and the host, including the case of the tenant name, and drop everything from /idp-web onwards. No trailing slash.

  2. To confirm it — or if the tenant's endpoints are laid out differently from the example above — read the issuer field from the tenant's discovery document, which is the authoritative source:

    https://<tenant-host>/.well-known/openid-configuration

    NOTE:

    Discovery is published at the host root, not under the /idp-web/oidc/ path the endpoints use. Appending .well-known/openid-configuration to the endpoint path returns a 404 error.

    Common Errors

    • The Imprivata Hub address is not the identity provider address.

      • The Imprivata Hub is at <tenant>.access.<domain>

      • The OIDC endpoints are at <tenant>.sys.<domain>.

    • The URL in your browser is not the one to send.

    • The Issuer URL and the token endpoint are different values, and the issuer has no path. The token endpoint is onscreen in front of you and the issuer is not, which makes this an easy substitution to make — but using the token endpoint as the issuer produces a configuration that passes every check in ServiceNow — and then fails at sign-in.

Stage 4 — Configure the Application in ServiceNow

Go to System Properties and set the following. All are prefixed with your scope name.

Property Value
<scope>.client_id The client ID from Stage 3
<scope>.authorize_url The authorize URL from Stage 3, copied whole
<scope>.token_url

The token URL from Stage 3, copied whole

<scope>.jwt_audience

The issuer URL from Stage 3 — no path

<scope>.redirect_uri Your redirect URI, matching Stage 3 exactly
<scope>.jwt_provider_id

The JWT Provider sys_id from Stage 2.3

<scope>.jwks

Already set in Stage 2.4

<scope>.scope

Leave as openid profile email

<scope>.jwt_kidx

Leave blank

NOTE:

The authorize and token URLs must each be https, with no query string and no fragment.

Stage 5 — Grant Access and Enable Email

  1. Grant cross-scope access. The application writes to the incident table, which requires a cross-scope privilege. Go to System Applications > Application Cross-Scope Access and approve the entries for this application.

  2. Grant the roles:

    Role Grant to
    <scope>.user

    Service desk agents who will verify callers

    <scope>.admin

    Administrators who configure the application

    Nobody holds either role after installation. Until you grant <scope>.user, the verification button does not appear for anyone.

  3. Confirm outbound email works on the instance, and send a test notification to yourself. The caller receives their verification link by email.

  4. Optional — brand the email templates. The application ships an HTML and a plain-text verification email. Edit both; callers may see either.

  5. Optional — add the verification list to the incident form so agents can see past verification attempts on an incident.

  6. Optional — decide who is notified of a suspected mismatch. Route this to your security or service desk management function rather than to the agent who pressed the button: that agent may themselves be the target of an impersonation attempt.

Stage 6 — Verify The Setup

Imprivata Administrator

  1. The tenant's discovery document resolves, and token_endpoint_auth_methods_supported includes private_key_jwt.

  2. authorization_endpoint and token_endpoint in the discovery document match the URLs you sent.

  3. The ServiceNow JWKS URI is reachable from outside the customer's network and returns a key. Imprivata fetches this URL at the time it is needed and does not report a fetch status. Check it directly.

ServiceNow Administrator

  1. Open an incident with a caller who has a valid email address.

  2. Click the verification button. The caller receives an email within a minute or two.

  3. The caller opens the link, completes the identity check, and the incident receives a work note with the result.

    NOTE:

    A verification link works only once. Opening a caller's link consumes that caller's verification. They cannot reuse it. Each verification consumes a billable identity check.

Workflow During A Service Desk Call

  1. A user calls the service desk. The service desk agent must confirm a caller's identity before providing support.

  2. In ServiceNow, the agent opens or creates the incident, and clicks Verify User.

  3. The service desk agent tells the caller to open the email while they are on the line; the link in the email expires in 15 minutes.

  4. The user opens the email.

    The user clicks the link in the message. If they opened the link from a desktop computer without a camera, the workflow can be handed off to a mobile device with a camera, via a QR code.

  5. A browser window opens with the user interface common to many Imprivata authentication workflows.

  6. The caller photographs their government ID and takes a selfie.

  7. After the user successfully completes the authentication, a success screen appears, and they may close their browser window.

  8. Imprivata returns the result to ServiceNow, and a work note is added with the results of the identity verification.

  9. The agent compares these results with the caller on the incident and decides whether they match. The application does not make this comparison. The work note gives the agent the evidence; the judgment is theirs.

  10. The service call may begin.

Troubleshooting

Symptom Likely cause
The verification button does not appear

The agent does not hold the <scope>.user role

The caller never receives an email
  • Outbound email is not enabled

  • The caller has no email address on their user record

  • The caller has notifications disabled

Sign-in fails immediately for every caller

The redirect URI in Imprivata does not match the redirect_uri property exactly

Sign-in fails after the identity check
  • jwt_audience holds the token URL instead of the issuer URL;

  • The endpoints are from the wrong environment

Imprivata reports it cannot verify the client

The JWKS endpoint is unreachable, returns a login page, or the jwks property contains stray whitespace

The caller is told verification failed, but the check succeeded

Known timing behavior — the caller can reopen the same link after about ten minutes, within its thirty-minute lifetime. Starting a new verification restarts the identity check.