This section allows the operator to manage all roles created in the enterprise.


Follow the steps given below to navigate to the 'Roles' screen. 


  1. In the admin portal, click the 'Enterprises' module from left menu, and then click 'Registered' to open the list of registered enterprises. 
  2. Click the three-dotbutton next to the enterprise you want to access, and select 'Manage' to navigate to the enterprise menu. 
  3. Click the 'Roles' module present in the enterprise menu. 


Create a New Role


To create a new role in the enterprise:


  1. The operator can add a role by clicking on the button. 
  2. The operator then needs to enter the name and description, and can also set that role as default by ticking the check box 'Default'. 



The operator can also set a role as 'Default'. 


When an operator adds or edits a role, the 'Module' screen appears and displays all modules that can be allowed to a user. The operator can choose whether to allow Read, Add/Edit, and Delete permissions for each selected module. 



To delete an enterprise role, click the three-dotbutton next to the role and select 'Delete'.


   

The system will display a confirmation dialog, click 'Yes' to proceed with the deletion. 



To modify permissions within a role, click the three-dotbutton and select 'Edit'. The operator can make changes in the following sections of the role: 


  1. Module 
  2. Certificate Management 
  3. Enrolments 
  4. More Settings
  5. Login Authentications 


  1. Module 


When an operator creates a new role, all options to "Read, Add/Edit and Delete" against the allowed modules are unchecked. The operator can choose from the options present in the module section to assign it with the role.  




  1. Certificate Management 


In the Certificate Management section, the operator can assign profiles to the role, allowing a user to create different types of certificates from the user portal. 



Key Stores

Field

Description 

Server-side Keys & Certificates

Select this checkbox to configure profiles for server-side keys and certificates. Then select the profiles from the drop down to that you want to allow for a role that belongs to an enterprise. 

Certificates with CSR 

Select this checkbox to configure profiles with CSR.Then select the profiles that you want to allow for a role that belongs to an enterprise. 

Keys on Smartcard/Tokens

Select this checkbox to configure profiles with keys on smartcard/tokens. Then select the profiles that you want to allow for a role that belongs to an enterprise. 

Unified Certification Profiles > Profiles for Certificates

Enable this checkbox and select the Unified Certification Profiles to configure for the role. The selected profiles will be available for the user to generate certificates in the User Portal.

Virtual ID check box

Select this checkbox to configure profiles to enable Virtual ID.

Profiles to create certificates for Virtual ID (remote authorisation) 

Select the profiles that you want to use to create Virtual ID certificates.

Certificate profile for user registration (Virtual ID)

Select a profile to create a default Virtual ID certificate.

Enable Virtual ID Auto Registration

Select this checkbox to allow auto registration of Virtual ID in ADSS Server while user registration in ADSS Web RA Server. 

Desktop Signing check box

Select this checkbox to configure profiles to enable Desktop Signing.

Profiles to create certificates for Desktop Signing

Select the profiles that you want to use to create certificates for Desktop Signing.

Desktop Signing profile for user registration 

Select a profile that you want to use to register user and create a default certificate for Desktop Signing. 

Provision certificates in Desktop Signing 

Select this checkbox to allow certificate provisioning for Desktop Signing to users allowed in this role. 

SigningHub check box 

Select this checkbox to configure profiles to enable SigningHub. 

Default certificate profile for SigningHub

Select a profile that you want to use to register user and create a default certificate for SigningHub using Virtual ID. 

Enable SigningHub Auto Registration 

Select this checkbox to allow auto registration of user in SigningHub while user registration in ADSS Web RA Server. 




  1. Enrolments 


A user can create specific certificates by using different configurations and will be able to manage certificate key generation for the following:


  • Device Enrolment
    • SCEP
    • CMP
    • ACME
    • EST


  • Windows Enrolment 
    • WIndows User Enrolment 
    • Windows Device Enrolment 



  1. More Settings 


Certificate Access


This setting allows an enterprise owner to manage certificate access and certificate sharing amongst the enterprise users.



PIN/PUK Resend


Enable resend PIN/PUK


This setting allows the enterprise owner to enable or disable the Resend PIN/PUK functionality. 


If the ‘Enable resend PIN/PUK’ checkbox is enabled, users of this enterprise will have the option to receive their PIN/PUK values again via email, SMS, or both, depending on the mechanism selected during the creation of the Certification Profile.


Note: If the operator has configured ‘None’ as the mechanism for sharing PIN and PUK values, the ‘Resend PIN / Resend PUK’ button will be hidden in the Token Information section of the Web Portal, even if the resend PIN/PUK permission is enabled in the user’s role permission.


For more details about 'how to configure mechanisms' view the Certification Profiles section. 


Enable view PUK


This setting allows the enterprise owner to control the visibility of PUK in the user portal.


If the ‘Enable view PUK’ checkbox is selected, the system will display the PUK in the Token Information section of a certificate. Alternatively, if this checkbox is disabled, the PUK information will not be displayed in the Token Information section. 



Second Factor Authentication on User Settings


This setting allows the enterprise owner to apply a second factor authentication check to two user actions available in the user portal: changing the password and updating the security question.


When this setting is enabled, any user belonging to the enterprise who attempts to change their password or security question in the user portal will be required to verify the action using a secondary authentication method.


Note: To choose the secondary authentication method, navigate to Roles > Login Authentications and select the required ‘Secondary Authentication Profile’. 



The enterprise owner can click the ‘User Settings’ dropdown and select the actions on which they want to apply the second factor authentication. 


Clicking the dropdown displays the following options:


  • Select All
  • Change Password 
  • Security Question



Select one or all options as required; the selected items will then appear in the dropdown field. 


Click ‘Save’ to apply the settings.



Digital Onboarding


Enable this option to require users to complete the digital onboarding process when signing up to Web RA.



When the ‘Enable digital onboarding when users sign up’ checkbox is selected, the system displays the following two fields.


Field

Description 

Connector

Select the Digital Onboarding connector to be used during the user sign-up process. Only active Digital Onboarding connectors configured in the Web RA system are available for selection.

Policy

Select the Digital Onboarding policy to be applied during the user sign-up process. Only active Digital Onboarding policies configured in the system are available for selection.


  1. Login Authentications 


The operator can configure primary authentication and secondary authentication for login process. 


(If Secondary Authentication is enabled in the service plan, it will also appear in the same section)


Field

Description

Primary Authentication Profiles

When primary authentication is configured as login authentication, it allows an enterprise RAO to login on ADSS Web RA User Portal through the authentication type that is configured in this profile. An operator can select from multiple primary authentication profiles here. 

Enable secondary authentication

Tick this check box to enable secondary authentication. 

Secondary Authentication Profiles 

When secondary authentication is configured as login authentication, it allows an Enterprise RAO to login to ADSS Web RA web portal through the authentication type that is configured in this profile.


Note: If secondary authentication is not configured in this section, the application will ignore the PIN/PUK policies that require secondary authentication

 


User Verification


The operator can enable or disable the below-given checkboxes if user mobile and email verification is required during registration.


  • Enable user mobile number verification
  • Enable user email verification



Certificate Details


The operator can control the Subject Distinguished Name (SDN) and Subject Alternative Name (SAN) extensions for certificate requests in the "Role" section under an Enterprise. This is based on the mechanism selected from the "Certificate Detail Provider" dropdown. 


The operator has the option to choose one of the three mechanisms available under the "Certificate Detail Provider" dropdown. These include:


  1. None
  2. Operator
  3. Authentication 


Field

Description 

None

If this option is selected from the dropdown, the users are required to fill the SDN values manually.

Operator 

If this option is selected, the operator can specify the values of SDNs.

 Authentication

If this option is selected from the drop down, the SDN values will be filled by the user login authentication mechanism. 


Currently, ADSS Web RA is supporting the following login mechanisms:


  • User name /Password
  • SAML
  • Active Directory
  • Azure Active Directory 


Note:

  • In authentication, the system will not allow an operator to control SAN values. 
  • If any information (Name, Job title, etc.) is not present in authentication then user will be able to add manually while creating a new certificate request.


Note: 

ADSS Web RA now supports the following additional Subject Alternative Name (SAN) fields:


  • Directory Name
  • Uniform Resource Identifier (URI)
  • EDI Party Name
  • Registered ID


When these SAN fields are configured in the ADSS Certification Profile, the corresponding fields are also supported in ADSS Web RA.


Furthermore, ADSS Web RA now supports additional encoding methods for the Directory Name and EDI Party Name SAN fields. The newly supported encoding methods are:


  • UTF8
  • Printable
  • Teletex
  • Universal
  • BMP


In case of None:


If the operator does not want to specify any SDN value in the certificate details and has selected the 'None' option, the user is required to provide the SDN value when creating a certificate request.



In case of Operator:


Select this option to specify the SDN and SAN values in the certificate details. These values will be used when the user creates a certificate request.



In case of Authentication:


Select this option to specify the SDN values in the certificate details. 


Values of Subject Distinguished Name (SDNs) which are present in user's authentication profile will be auto-filled from the selected authentication mechanism, if it exists while creating a certificate request.



When Primary Authentication profile is OIDC, Saml, Azure AD or Active Directory, and you select Authentication as the Certificate Detail Provider



Certificate Detail

Field

Description 

Claims

Enter a claim. You can set multiple claims based on different SDNs.

Subject Distinguished Name (SDN) 

Select a SDN from the list and then click the + button to confirm your entry.


Click Save. 


Default Role (User Registration- Citizen ID)


When a user is registered through citizen ID, an operator will perform the following configurations: 


  1. Registration form claim mapping.
  2. Enable auto-registration for Virtual ID and SigningHub. 


Enable auto-registration for Virtual ID and SigningHub


Expand Enterprises > Registered > Enterprise Name > Manage > Roles. 


Then click Edit against the Default Role.



Click the Certificate Management tab.


Select the profiles from the Key Stores. 


Then select  the Virtual ID checkbox.


Virtual ID 

Field

Description 

Profiles to create certificates for Virtual ID (Remote authorisation)

Select a profile from the list to create Virtual ID certificates. 

Certificate profile for user registration (Virtual ID)

Select a profile to create a Virtual ID user and to create a default Virtual ID certificate.



Select the SigningHub check box


SigningHub (NCSC in this example)

Field

Description 

Default certificate profile for SigningHub

Select None from this drop down.

Enable SigningHub Auto Registration

Select this check box to enable auto registration of SigningHub.



Then click Save. 


Registration form claim mapping


Click Login Authentications.


Select any third part authentication(SAML,AzurAD, Active directory and OIDC) as Primary Authentication Profile from the drop down. 


Certificate Details 

Field

Description 

Certificate Details Provider 

Select authentication from this drop down.


Claims

Claim 

Subject Distinguished Name (SDN) 

Select a claim against the SDN

Click + and select SDN from the list. These fields include 


These claims will appear in the Sign up form under the SDN section. 




Claims

Claim 

Registration Fields

Select a claim against the registration fields

Click + and select SDN from the list. These fields include Name, Job Title, Virtual ID, Citizen ID, Default Capacity (for Signing purposes while provisioning certificate in SigningHub), CSP User Name, Email Address and Mobile Number. 


These claims will appear in the Sign up form under the user registration section. 



Once you have completed all configurations, click Save.