Challenge
A Swedish municipality needs to give its employees and consultants access to the municipality's system for digital workflows, ServiceNow. The municipality's users consist of various professions, including:
Nursing staff
Case manager
Administrators
External consultants
To minimize administration, the municipality wishes to use existing user accounts in the municipality's user directory, Active Directory, for authentication. For security reasons, to avoid hackers being able to crack passwords and access the organization's digital information in ServiceNow, the organization wants to use a more secure method than passwords for authentication. The method must be easy to use and involve minimal work with administration, in order to save time and money.
Solution
With Fortified ID Integrity, different e-identifications can be used as an authentication method against ServiceNow. In order for the various professions in the municipality to be able to log in to ServiceNow, a number of different e-identifications are exposed as choices for the user when logging in:
SITHS, for healthcare professionals
EFOS, for case managers and administrators
Freja OrgID, for employees
Freja eID, for external consultants
BankID, for external consultants
The solution is cost-effective:
The process for issuing an e-identification to users is handled outside the municipality
Requires minimal administration in the organization
Standardized integration
The solution provides support for authentication via SITHS card or mobile SITHS. The solution provides support for authentication via EFOS card or mobile EFOS. The solution provides support for authentication via mobile BankID or BankID. The solution provides support for authentication via Freja eID and/or Freja OrgID. It is easy to deactivate variants that are not to be used, for example a municipality can choose not to use mobile SITHS. The graphical interface, the one that meets users, is fully customizable to be able to align with the organization's graphical profile.
Other
The connection between the user's e-identification and the user's account in the organization usually takes place against Active Directory (AD) via a lookup against the directory service. The solution uses the identifier on the user's eID, which can be a social security number or HSA ID, depending on the eID, with an attribute on the user's account in AD. The organization can choose which attributes to use for this mapping. The protection of ServiceNow is configured via a standard (OpenID Connect) between ServiceNow and Integrity.