Go>Sign Desktop Certificates
This section explains how to create Go>Sign Desktop certificate requests in the Web RA application.
- Go>Sign Desktop Certificate Type
- Go>Sign Desktop Certificate Type with vetting
- Create a Go > Sign Desktop Certificate Using a Vetting Form with SDN/SAN Mappings
Following are a few things to remember with respect to SDNs, SANs and RDNs:
- When a user creates a new certificate request, the SDNs and SANs will be rendered as configured in the certification profile and its values will be auto-filled from the certificate details.
- A user will not be able to change the values of the RDNs if an operator has configured them in the certificate details.
- An operator will see the rendered values in a disabled form.
- If there is an RDN that is added in certification profile but has not been configured in the user's certificate details, it will be shown as editable in the request form and the user can update its value.
- If no RDN is configured in the user certificate details then the request will be generated.
- In case of an error, the user will not be allowed to move to the next step.
Second Factor Authentication
If second-factor authentication is enabled for certificate requests, the configured authentication mechanism operates accordingly. When the user clicks Generate, an authentication window appears. After the selected method is successfully verified, the certificate is generated.
The authentication mechanism can be one of the following:
- SMS OTP Authentication
- Email OTP Authentication
- Email & SMS Authentication
- SAML Authentication
- Active Directory Authentication
- Azure Active Directory Authentication
- OIDC Authentication
Request Notes
If an operator has added a customized Request Note to certificate requests for a specific enterprise, it will appear in all types of certificates requests -- issued, rekey, revoked, renewed and reissued. The Request Notes appear only on the screens against which the operator has customised them.
An operator can configure Request Notes from the Enterprise Request Notes section in the Admin portal.
Following are the steps to create a token certificate request for Go>Sign Desktop profile.
Expand Certificate Center > Certificate Requests to navigate to the Certificate Requests listing screen.

Click the + button to create a new certificate request. The system will display the create request screen.
On this screen, select the ‘Certificate Type’ from the dropdown, and click ‘Create’.

The Subject Distinguished Name (SDN) screen will appear. Here, enter the required details in the respective fields, then click Next.
Country, State, Locality and Postal Code in a Certificate Request
When you create a certificate request, you may need to enter the certificate holder's Country, State, Locality (city) and Postal Code. Depending on how the certificate type is set up, these fields appear on the Subject Distinguished Name (SDN) screen.
|
Field |
Description |
|
Country |
Select the country. Only the countries allowed by your administrator are displayed. The country field will be pre-selected according to the country selected under the Enterprise > Profile > Organisation Information. |
|
State |
Select the state or province from the list. Only the states or provinces associated with the selected country are displayed. |
|
Locality |
Select the city from the list. This field is available only after a state or province has been selected. You can type in the field to search for a city. |
|
Postal Code |
Enter the postal code in the format required by the selected country. If the entered postal code does not match the required format, an error message is displayed. For example: "The postal code does not match the format of the selected country. It must be 5 characters." |
Note:
- On this screen the field names always stay the same. For example, State is still called State even if the country uses provinces.
- If you change the country, the State and Locality are cleared and you need to select them again.
- Ensure that the CSR uploaded with the certificate request contains the correct country, state or province, and locality details.

The 'Certificate Validity' screen will appear. Enter the required validity period and click ‘Generate’.

Once you click generate, a dialog titled ‘Go Sign Reset Token’ will appear. This dialog will display the auto-generated value of PIN in disabled form. The user can view and save the value from the respective icons.
The ‘Mechanism’ box will appear as disabled. It will display the platform where the new value of PIN will be shared.

|
|
Note: The dialog for resetting PIN or PUK values will only appear if the reset PIN/PUK setting is enabled in the certification profile. If the operator has enabled the setting to reset both PIN and PUK values, both PIN and PUK sections will appear in the 'Go Sign Reset Token' dialog. However, if the setting is enabled for only PIN or PUK, the sections in the dialog will appear accordingly. |
The mechanism for sharing the new values of PIN or PUK is selected during the creation of the certification profile. The setting for mechanism can be changed from certification profile.
Click ‘Ok’ to proceed.
The system will generate the CSR, create the certificate and share the value of PIN with the user via email.
|
|
Note: Make sure that the PIN/PUK character length configured in the Enterprise > Policies section matches the length set in the 'PIN/PUK Quality' settings of the "SafeNet Authentication Client" utility. If the values do not match, the system will not reset the PIN value. |
|
|
Note: If the token password previously generated by the ADSS Web RA system has been changed through the 'SafeNet Authentication Client', the system will display the 'Go Sign Update PIN' dialog when you attempt to generate a new certificate request from the same token. |
You will be required to enter the updated token PIN to proceed.

|
|
Note: Each token is assigned to a single user. If a token is used to create a certificate request for a user it is not assigned to, the system will display an error stating that the token does not belong to the user. |
Following are the steps to create a token certificate request for Go>Sign Desktop profile with Vetting enabled.
Expand Certificate Center > Certificate Requests to navigate to the Certificate Requests listing screen.

Click the + button to create a new certificate request. The system will display the create request screen.
On this screen, select the ‘Certificate Type’ from the dropdown, and click ‘Create’.

The Subject Distinguished Name (SDN) screen will appear. Here, enter the required details in the respective fields, then click Next.

The 'Certificate Validity' screen will appear. Enter the required validity period and click ‘Next’.

The 'Vetting Form' screen will appear. Add the required details in this screen and click 'Submit'.

Once you click submit, a dialog titled ‘Go Sign Reset Token’ will appear. This dialog will display the auto-generated value of PIN in disabled form. The user can view and save the value from the respective icons.
The ‘Mechanism’ box will appear as disabled. It will display the platform where the new values of PIN will be shared.

|
|
Note: The dialog for resetting PIN or PUK values will only appear if the reset PIN/PUK setting is enabled in the certification profile. If the operator has enabled the setting to reset both PIN and PUK values, both PIN and PUK sections will appear in the 'Go Sign Reset Token' dialog. However, if the setting is enabled for only PIN or PUK, the sections in the dialog will appear accordingly. |
The mechanism for sharing the new values of PIN or PUK is selected during the creation of the certification profile. The setting for mechanism can be changed from certification profile.
Click ‘Ok’ to proceed.
The system will generate the CSR, and submit the request to be approved by the administrator.
|
|
Note: Make sure that the PIN/PUK character length configured in the Enterprise > Policies section matches the length set in the 'PIN/PUK Quality' settings of the "SafeNet Authentication Client" utility. If the values do not match, the system will not reset the PIN value. |
|
|
Note: If the token password previously generated by the ADSS Web RA system has been changed through the 'SafeNet Authentication Client', the system will display the 'Go Sign Update PIN' dialog when you attempt to generate a new certificate request from the same token. |
You will be required to enter the updated token PIN to proceed.

|
|
Note: Each token is linked to one specific user. The system does not allow a certificate to be created for any user who is not linked to that token. |
|
|
Note: If the certificate is being created for a user who does not exist in the system, a new account will be created for the user along with the certificate. If the user already has a registered account in the WebRA system, only the certificate will be created. The user will be notified via email about the certificate generation. Meanwhile, if the user exists in the system but is not part of the enterprise where the certificate is being created, the system will send an invitation for the user to join that enterprise and will generate the certificate as well. |
If 'Dual Control' for request section or 'Special Permissions' setting is enabled in the certification profile of Smartcard/Token in ADSS Web RA, the 'Go Sign Token' dialog will also display a 'None' option in the dropdown.

If you select the 'None' option from the dropdown and submit the request, the certificate request will be submitted without creating CSR. However, if you select a token from the dropdown, the system will first create a CSR and then submit the certificate request.
|
|
Note: If the token password previously generated by the ADSS Web RA system has been changed through the 'SafeNet Authentication Client', the system will display the 'Go Sign Update PIN' dialog when you attempt to generate a new certificate request from the same token. |
You will be required to enter the updated token PIN to proceed.

|
|
Note: If the setting for Digital Onboarding is enabled in the Certification Profile, clicking the 'Generate' button displays a dialog containing the providers configured in the selected Digital Onboarding connector. |
Select the required provider from the given options.

The system then displays a QR code. Scan the QR code using the Digital Onboarding mobile application.

After scanning the QR code, complete the identity verification process by providing the required documents as configured in the Digital Onboarding policy.
Once the identity verification process is completed successfully, the QR code will disappear and the certificate request will be generated.
Create a Go > Sign Desktop Certificate Using a Vetting Form with SDN/SAN Mappings
In the web portal, navigate to Certificate Center > Certificate Requests from the left menu tree.

Click on the ‘+’ plus button in the listing header to create a new certificate request. The system will display the ‘Create Request’ screen.

On this screen, select the certification profile from the ‘Certificate Type’ dropdown and click ‘Create’.
The system displays the certificate request, where you can enter the required information in different sections according to your requirements.
If any fields in the vetting form are mapped to Subject Distinguished Name (SDN) or Subject Alternative Name (SAN) fields, the vetting form appears as the first step in the certificate request. The user must enter the details in the vetting form before proceeding to the remaining sections of the certificate request. The values entered in the vetting form are used to populate the corresponding mapped SDN/SAN fields.
|
|
Note:
|

After entering the information in the Vetting Form fields, click the next ‘>’ button to proceed to the Subject Distinguished Name (SDN) screen.

|
|
Note:
|
If an SDN field is not mapped to a Vetting Form field and is not configured as fixed in the ADSS Certification Profile, the field remains enabled, allowing you to enter a value according to your requirements.
After reviewing and entering the required values, click the next ‘>’ button to navigate to the Subject Alternative Name (SAN) screen.
|
|
Note: ADSS Web RA now supports the following additional Subject Alternative Name (SAN) fields:
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:
|

|
|
Note:
|
If a SAN field is not mapped to a Vetting Form field and is not configured as fixed in the ADSS Certification Profile, the field remains enabled, allowing you to enter a value according to your requirements.
After reviewing and entering the required values, click the Submit button to submit the request for approval by the operator.
The system will display the ‘Enter PIN for Token: (Token Name)’ dialog. Enter the PIN and click ‘Ok’.

The system will generate the CSR and submit the request for approval from the operator.

