Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
This article provides detailed information about the Nexus Smart ID solution Physical ID.
Scroll ignore | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Anchor | ||||
---|---|---|---|---|
|
Expand | ||
---|---|---|
| ||
Basic branding is included in the Physical ID module, by displaying the customer logotype in PRIME Explorer and User Self-Service Portal. |
Expand | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||
Nexus provides basic templates for the email notifications included in the common use cases, for example when a card has been activated or is about to expire. During the implementation project, Nexus consultants or partners adapt the email templates for the customer needs. When the Physical ID module is up and running, email templates can be updated by a user that has the Super user role.
The following email templates are included:
|
Expand | ||
---|---|---|
| ||
The following standard reports are included in the Smart ID solution:
The reports are created using searches in PRIME Explorer. |
Expand | ||
---|---|---|
| ||
Supported languages are listed in PRIME requirements and interoperability. |
Expand | ||
---|---|---|
| ||
As part of the Smart ID solution, the customer can choose to include the PRIME User Self-Service Portal (USSP). The available self-service tasks in the USSP can help minimizing administrative work. The following self-service tasks are available in the User Self-Service Portal:
|
Installation requirements
title | Installation requirements on server |
---|
The following installation requirements apply to the server in the Smart ID solution:
SQL Server 2014 or later installed with TCP port 1433 enabled. The Standard edition is recommended. The Express edition is also supported but has limited storage capacity.
Scroll ignore | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
For more information, see https://www.microsoft.com/en-sa/sql-server/sql-server-2017-editions. |
Requirements on Active Directory setup:
- A Service account in AD who is a Domain User
- Active Directory Tools installed on PRIME Server
- The OU where PRIME shall get all needed users (example, OU=Employee, DC=example, DC=com).PACS-specific user service account for PACS connector communication.
Requirements for ADCS setup:
- All the CA certificates that are needed on file on Prime server (ex, ca1.cer, ca2.crt).
- Two certificate templates for Smartcard created in ADCS, one for Smart Card Authentication and one for Digital signature is going to be created in the ADCS, we do this together with the customer
- An SSL certificate with both certificate and key (pfx,p12) for PRIME saved on PRIME server, with Common Name and SAN name like prime.shb.se or similar.
- An SSL certificate with both certificate and key (pfx,p12) for PRIME ADCS Connector saved on PRIME server, with Common Name and SAN name like primeinternal.shb.se or similar. This is only going to be used internally on PRIME Server.
- A Certificate with both certificate and key (pfx,p12) for PRIME to use when authenticate from PRIME to the ADCS Connector, the certificate needs to have Client Authentication as Extended Key Usage.
- RSASSA-PSS must not be used as the signature algorithm. This can be verified in a certificate, by checking the signature algorithm. SHA256 is the preferred signature algorithm, and SHA1 is also supported.
Expand | ||
---|---|---|
| ||
The following installation requirements apply to the client in the Smart ID solution:
|
Anchor | ||||
---|---|---|---|---|
|
Expand | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||
Additional workflows that are included in the price for the Smart ID solution:
These additional workflows must be specified during the implementation project, and will be implemented by Nexus consultants or partners. |
Expand | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||
These choices are available in the standard workflows:
These options must be specified during the implementation project, and will be implemented by Nexus consultants or partners. |
Expand | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||
Optionally, Nexus Service Station can be used to collect employee photos. There are standard workflows for that purpose, that are included in the solution. The Service Station hardware is an add-on.
|
Scroll ignore | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Related information
|