Skip to main content

NHS Smartcard Connect

NHS Smartcard Connect is the authentication client using CIS2 Authentication, installed as part of a package including version 4.1 of NHS Credential Management.

This guidance is aimed at IT managers and administrators, suppliers of desktop and support services, and any other person who has responsibility for installation, configuration, support and management of NHS authentication software. 


NHS Smartcard Connect is the authentication client using CIS2 Authentication. It allows existing smartcards to authenticate directly over the internet, and HSCN.

Smartcard Connect is installed as part of a package that includes the latest version of NHS Credential Management. It includes all the previous functionality of older versions of NHS Credential Management.

NHS Credential Management with Smartcard Connect is no longer installed alongside the legacy NHS Identity Agent.

Smartcard Connect user changes

Smartcard Connect authentication is different to what you may be used to with Identity Agent.

Inputting your smartcard into the reader does not generate a pop-up box - you will instead need to enter your PIN when you access a system.

Removing your smartcard from the reader does not log you out - you'll need to manually log out of an application when you're finished.

You'll need to enter your PIN each time you open a new application.

Compatibility

Smartcard version Works with Identity Agent v2.4.10.0? Works with Smartcard Connect?
Series 8 (Oberthur) Yes (until 28 February 2027) Yes
Series 9 (Idemia) Yes (until 28 February 2027) Yes
Series 10 (Idemia) Authentication only (until 28 February 2027) Yes

Please note: Smartcard Connect should not be installed on a machine until all Spine applications used on that machine support CIS2 Authentication.

Current authentication methods

CIS1 authentication allowing access to CIS1 and CIS2 enabled applications

Our current authentication method uses the legacy Identity Agent client installed on the user's device. This client authenticates the user with their smartcard and passcode against the CIS1 authentication stack which is only available through HSCN. Once authenticated, the client holds a secure single sign-on (SSO) token locally. 

When the user tries to access CIS1 Spine applications, the applications obtain the SSO token and work as they have always worked in the past. 

When the user tries to access CIS2 enabled Spine applications, the application redirects the user through an OpenID Connect (OIDC) flow. That flow communicates with the legacy Identity Agent on the local machine, retrieves the SSO token, and then that token is swapped by CIS2 for OIDC tokens. These are then used to authenticate the user via CIS2, granting them access. 

This is how the majority of the NHS is currently able to access both CIS1 and CIS2 enabled Spine applications. All Spine applications are either already CIS2 enabled, or are in the process of migrating to be CIS2 enabled. 

CIS2 authentication allowing access to CIS2 enabled applications only

With the new authentication client Smartcard Connect, the process is simpler and more secure. Users no longer need to keep their smartcard inserted continuously, and there’s no local client storing tokens. When accessing a Spine Application, users are prompted to insert their smartcard and enter their passcode. 

Smartcard Connect then directly communicates with the CIS2 identity service using OpenID Connect (OIDC). The user is authenticated in real time, and a secure OIDC token is returned to the application, granting access. This approach reduces complexity, improves performance, and aligns fully with modern NHS CIS2 standards — all without compromising security. 


System requirements

Operating systems and browsers

The NHS England Warranted Environment Specification (WES) lists all supported software configurations.

Environments

This version of NHS Credential Management with Smartcard Connect supports CMS (Card Management Services) operations in other environments such as Citrix/VDI/Terminal Services.


Download

Download Smartcard Connect v4.1.

Please note the software package you'll download retains the name Credential Management.

File information

Downloaded file 

  • SHA1 - 66BB0FC235B1B47C222F3CF8BA08FCCB93AE22DB
  • MD5 - 7364557EF9C68F903A01E551B175336D

Program Executables 

NHS Smartcard Connect 

  • .exe Name - NHSD.IdentityAgent.exe
  • SHA1 - A208E61FC5A1104963D6470D884A49DA9EB29BC2
  • MD5 - F223B635A63604E943C12E64E7E813DC

NHS Credential Management 

  • .exe Name - NHSHub.UI.exe
  • SHA1 - 057D080A452D2FE8928F165DBA28675BB99606CA
  • MD5 - BBC892C7D61EBDA315BAD0AB8B0A6039

NHS Smartcard Diagnostics

  • .exe Name - DiagnosticTool.UI.exe
  • SHA1 - 7BB67830742C8D1F787551D36CE3C6A58795715D
  • MD5 - 1A90A853B3FB30688C366DE008AD0254
Release notes

v4.1.2.0 - 27 May 2026

  • Upgrade to .NET10
  • Improved timing enhancements around authentication and CMS operations
  • Support for Series 10 (due summer 2026)

v3.13.5.0 - 6 November 2025

  • Improved authentication and CMS operations coverage by extending support to smartcard readers operating with the T=0 protocol.

Installation

We strongly recommended that you uninstall any previous versions of NHS Credential Management and the legacy NHS Identity Agent before beginning any new installation.

1. Download the Installer: 

  • Go to the download section. 

  • Download the installer file. 

2. Run the installer: 

  • Navigate to the location where the installer file was downloaded. 

  • Double-click the installer file to start the installation process. 

3. Follow the on-screen instructions: 

  • The installer will open a setup wizard. 

  • Follow the prompts, which typically include agreeing to the terms and conditions, choosing the installation directory and, if applicable, selecting additional features or components to install. 

4. Complete the installation

  • Once you've made your selections, click the Install button to begin the installation. 

  • Wait for the installation process to complete. This may take a few minutes depending on the application size and your system's performance. 

5. Launch the application

  • After the installation is complete, you can find NHS Credential Management and Smartcard Connect under NHS in the Start Menu. 

  • Click on the application icon to open and start using it. 

Silent installation 

The NHS Credential Management with Smartcard Connect supports silent installation using standard deployment tools that recognise .msi packages. Alternatively, you can use the following command line for script-based installation: 

%SystemRoot%\System32\msiexec.exe /i "NHS.Credential.Management.4.1.2.0.signed.msi" /qn

Software will be installed in the following locations: 

  • C:\Program Files (x86)\NHS\NHS Credential Management 

  • C:\Program Files (x86)\NHS\NHS Port Service 

  • C:\Program Files (x86)\NHS\NHS Smartcard Connect

  • C:\Program Files (x86)\NHS\NHS Smartcard Diagnostics

NHS Port Service 

As part of the installation, the NHS Port Service will be installed on a machine and will automatically start. 

This service is required for NHS Credential Management to function correctly and should not be stopped or barred from executing. 


Uninstallation

It is strongly recommended that you uninstall any previous versions of NHS Credential Management and the legacy NHS Identity Agent before beginning any new installation. No other programs are removed as part of this process.

Note: earlier releases of NHS Credential Management (during 2020) had a different name: NHS Identity Hub.

These steps apply to any version of the NHS Identity Agent and NHS Credential Management.

Uninstall via Control Panel

1. Open the Control Panel

  • Press the Windows key + S and type Control Panel. 

  • Select Control Panel from the search results. 

2. Navigate to Programs and Features

  • In the Control Panel, click on Programs. 

  • Click on Programs and Features. 

3. Find the application to uninstall

  • Scroll through the list of installed programs to find the application you want to uninstall. 

4. Uninstall the application

  • Select the application from the list. 

  • Click on Uninstall at the top of the list. 

  • Follow the prompts to complete the uninstallation process. 

Uninstall via Settings

1. Open Settings

  • Press the Windows key + I to open Settings. 

  • Go to Apps > Apps & features. 

2. Find the application to uninstall

  • Scroll through the list of installed applications to find the one you want to uninstall. 

  • Alternatively, you can use the search bar to quickly locate the application. 

3. Uninstall the application

  • Click on the application. 

  • Click on Uninstall and follow the prompts to complete the uninstallation process. 

Uninstall using Command Prompt

1. Open Command Prompt as administrator

  • Press Windows key + X and select Command Prompt (Admin). 

2. Use WMIC to uninstall

  • Type the following command to list all installed applications: 

Cmd - wmic product get name

  • Find the name of the application you want to uninstall. 

  • Type the following command to uninstall the application: 

cmd 

wmic product where "name='Your Application Name'" call uninstall 

(Replace Your Application Name with the actual name of the application.)


Using the software

Launch 

Once NHS Credential Management, NHS Smartcard Diagnostics and Smartcard Connect have been installed, an icon will be placed in the Programs list under the NHS area of the start menu.

NHS Credential Management and NHS Smartcard Connect do not automatically start after installation but will automatically start on a subsequent user login or machine restart.

Included in the package is the NHS Smartcard Diagnostics tool, which will need to be launched from the start menu each time it's required.

Close 

An icon will be visible in the system tray when the applications are running. The programs can be closed by right clicking the chosen icon and selecting Close. Right click and select Status to show the currently installed version.

Log paths 

NHS Credential Management:

C:\Users\{username}\AppData\Local\NHS\NHS Credential Management

NHS Port Service:

C:\ProgramData\NHS\NHS Port Service

NHS Smartcard Connect:

C:\Users\{username}\AppData\Local\NHS\NHS Smartcard Connect

NHS Smartcard Diagnostics:

C:\Users\{username}\AppData\Local\NHS\NHS Smartcard Diagnostics


Configuration and troubleshooting

Read full guidance and instructions on how to set up and troubleshoot Smartcard Connect. Read on for registry settings specific to Smartcard Connect.

Printing smartcards

For printing all smartcard versions with Smartcard Connect v4.1, you will need to make sure you have the latest printer smartcard reader driver.

Registry settings

The Smartcard Connect client reads settings from three separate areas of the registry. The locations have different purposes, and this is reflected in the order in which they are prioritised. The priority order is controlled by Windows. 

1. Set by Group Policy

These settings will be applied by group policy. System administrators can create their own template(s) from the registry setting information provided in this document for policy rollout if required. These settings will always take precedence. 

2. All Users (Local Machine)

These settings are machine-wide and will apply to any user who logs in to the system. The settings will remain machine specific, meaning that a user will always adopt these in preference to user settings. 

3. Current User

These settings apply only to the current logged in user and will persist with the user profile. If the user has a roaming profile, then the settings will travel with the user between machines. 

The Smartcard Connect process runs as a 32-bit process regardless of whether the operating system is 32-bit or 64-bit.

64-bit operating system

Authentication and common settings 

Set by Group Policy 

HKLM\SOFTWARE\Policies\NHS\SmartcardConnect 

All Users 

HKLM\SOFTWARE\Wow6432Node\NHS\SmartcardConnect 

Current User 

HKCU\SOFTWARE\NHS\SmartcardConnect 

Registry keys

Pin Form Timer

By default there is a countdown timer built-in to the Smartcard Connect client which is set to 5 minutes (300 seconds). You can alter and change this by configuring the below registry: 

  • Location: Preference as above 
  • Value name: TimeToShowPinForm 
  • Type: Reg_SZ 
  • Value: 300

Note: CIS2 enabled applications also set timeouts for authentication which could collide with this setting. 

Last edited: 10 June 2026 12:32 pm