Unified Certificate Requests
This page provides information about managing certificate requests generated using a Unified Certification Profile. It explains how to create and view certificate requests and perform certificate lifecycle operations, including downloading, revoking, renewing, reissuing, and rekeying certificates associated with a request.
- How to Create a Certificate Request
- How to Generate a Token-based Certificate Request
- How to Revoke a Certificate
- How to Reissue a Certificate
- How to Rekey a Certificate
- How to Renew a Certificate
How to Create a Certificate Request
To create certificate requests using the Unified Certification Profile, expand Requests > Certificate Requests from the left-tree menu in the Admin portal.
Then click the ‘+’ button from the grid header.

The system displays the ‘Create Request’ screen. Select your ‘Enterprise’ from the ‘Enterprise Name’ drop down, and select the Unified Certification Profile from the ‘Certificate Type’ dropdown.

The system displays all the certification profiles selected under the Unified Certification Profile, along with their Key Store and Validity Period details.
|
|
Note: If you want to generate a certificate request from the Admin Portal using a Unified Certification Profile, you can generate certificates only for MSCAPI-type or Token-based profiles. The system does not allow certificate generation for ‘Server-side Keys & Certificates’ profiles from the Admin Portal. |
|
|
Note: Go Sign Desktop version 8.4.2.1 is required to generate certificates from a Unified Certification Profile containing Token-based or MSCAPI-type certification profiles. |
|
|
Note: A checkbox titled ‘Generate a certificate on behalf of the user’ will appear on this screen if the "Allow operators to create certificates on behalf of the user and facilitate automatic assignment" policy is enabled in the Enterprise > Policies > Requests section. If you enable this checkbox, you will be asked to provide information about the user for whom the certificate is being generated at the end of the certificate request creation process. |

Click the ‘Create’ button to proceed.
The Subject Distinguished Name (SDN) screen appears on the screen.

|
|
Note: The system combines the SDN fields configured in all the certification profiles selected in the Unified Certification Profile and displays them on the ‘Subject Distinguished Name (SDN)’ screen. If the same SDN field is configured in multiple certification profiles, that field is displayed only once on the SDN screen during certification request creation. For example, if the Common Name SDN is configured in two certification profiles, the ‘Common Name’ field will appear only once on the SDN screen. The SDN fields displayed on the SDN screen are not included in all the certificates generated using the Unified Certification Profile. Each certificate will contain only the SDN fields configured in its respective certification profile. For example, if the Common Name SDN is configured in one certification profile but not in another, the ‘Common Name’ field will be displayed on the SDN screen, but the certificate generated using the certification profile without the Common Name configuration will not contain the Common Name attribute. Enter the information in the SDN fields as per your requirement and click the next ‘>’ button to proceed to the Subject Alternative Name (SAN) screen. |

|
|
Note: The system combines the SAN fields configured in all the certification profiles selected in the Unified Certification Profile and displays them on the ‘Subject Alternative Name (SAN)’ screen. If the same SAN field is configured in multiple certification profiles, that field is displayed only once on the SAN screen during certification request creation. For example, if the Domain Names (DNS) field is configured in two certification profiles, the ‘Domain Names (DNS)’ field will appear only once on the SAN screen. The SAN fields displayed on the SAN screen are not included in all the certificates generated using the Unified Certification Profile. Each certificate will contain only the SAN fields configured in its respective certification profile. For example, if the Domain Names (DNS) field is configured in one certification profile but not in another, the ‘Domain Names (DNS)’ field will be displayed on the SAN screen, but the certificate generated using the certification profile without the Domain Names (DNS) configuration will not contain the Domain Names (DNS) attribute. Enter the details in the SDN fields as per your requirement and click the next ‘>’ button to proceed to the Certificate Validity screen. |

The validity period of each certification profile is displayed on this screen. The ‘Validity Period’ field appears enabled or disabled according to the configuration of each certification profile.
Click the ‘Generate’ button to generate the certificate requests.
|
|
Note: If a Subscriber Agreement is configured in any or all of the profiles, each agreement is displayed on the screen one by one. You must agree to all the agreements to generate the certificates. |

Click ‘I Agree’ to proceed. The system will take some time to process the certificate requests. Once the processing is complete, the certificate will be generated and appear in the Certificate Requests and Issued Certificates listing screen.
The certificate will be generated and a success alert will appear on the screen.

The generated certificate will appear on the Certificate Requests listing. The certificates generated using a Unified Certification Profile are grouped under a single main request number in the ‘Certificate Requests’ listing.

A ‘+’ button appears next to the main request number. Click the ‘+’ button to expand the request and view the list of all certificates generated under the Unified Certification Profile. Each certificate in the list has its own request number.

|
|
Note: If the ‘Generate a certificate on behalf of the user’ checkbox is enabled, the system will display an additional screen titled ‘User Information’ next to the Certificate Validity screen. |

On this screen, you are required to enter or select the Name, Email, Citizen ID, Mobile Number, and Role of the user for whom the certificate is being generated.
After entering the required details, click ‘Generate’. The system creates the account and generates the certificate based on the user's existing account and enterprise membership status. The user receives an email regarding the account and certificate generation and, where applicable, is prompted to activate their account.
- If the certificate is being created for a user who does not exist in the system, the system creates a new account for the user along with the certificate.
- If the user already has a registered account in the Web RA system, only the certificate is created. The user is notified by email about the certificate generation.
- If the user exists in the system but is not part of the enterprise where the certificate is being created, the system sends an invitation for the user to join that enterprise and generates the certificate.
|
|
Note: If an issue occurs while generating one or more certificates in a Unified Certification Profile, the certificates that can be generated successfully are issued, while the certificates affected by the issue are not generated. For example, if a Unified Certification Profile contains two certification profiles and the enterprise licence limit has been reached for one of them, the system generates the other certificate and displays a success alert indicating that 1 out of 2 certificates were generated. An error alert also appears, describing the issue that prevented the second certificate from being generated. The same behaviour applies to other issues that prevent certificate generation. The ‘Generate’ button remains available for the certificate request. Resolve the issue indicated in the error alert and click ‘Generate’ again to generate the remaining certificate(s). |

The Unified Certificate Request appears in the "Certificate Requests" listing. When the request is expanded, the certificates that were generated successfully display the ‘Approved’ status, while the certificate(s) that could not be generated display the ‘Draft’ status. The Unified Certificate Request moves to the "Issued Certificates" listing only after all certificates associated with the request have been generated successfully and approved.

Expand Requests > Certificate Requests from the left-tree menu in the Admin Portal. The Certificate Requests listing screen will appear.
The certificates generated using a Unified Certification Profile are grouped under a single main request number in the ‘Certificate Requests’ listing.
A ‘+’ button appears next to the main request number. Click the ‘+’ button to expand the request and view the list of all certificates generated under the Unified Certification Profile. Each certificate in the list has its own request number.

To revoke one or more certificates generated using a Unified Certification Profile, click the three-dot
button next to the main request number and select ‘View Request’.
The system opens the certificate request. Click on the ‘More Actions’ button.

A dialog titled ‘Certificate Action’ appears on the screen.

Select ‘Revoke Certificate’ option from the ‘Action’ dropdown.
From the ‘Certificate Type’ dropdown, you can either select any one certificate from the list to revoke it, or select the ‘All’ option to revoke all certificates, depending on your requirement.

Select the revocation reason from the ‘Certificate Revocation Reason’ dropdown, and select the ‘I have reviewed and verified the revocation request’ checkbox.
You can also add an optional message related to the certificate revocation in the ‘Message’ box.
After that, click ‘Revoke’ to revoke the certificate. The selected certificate will be revoked and a success alert will appear on the screen.

The revoked certificate will appear in the ‘Revocation Requests’ listing.

How to Reissue a Revoked Certificate
Expand Requests > Revocation Requests from the left-tree menu in the Admin Portal. The Certificate Requests listing screen will appear.
To reissue a certificate that has been revoked from a group of certificates issued using a Unified Certification Profile, click the three-dot
button next to the main request entry and select ‘View Request’.

The system opens the Certificate Request. Click on the ‘More Actions’ button and a dialog titled ‘Certificate Action’ appears on the screen.

Select the ‘Reissue Certificate’ option from the ‘Action’ dropdown. Then, select the certificate that you want to reissue from the ‘Certificate Type’ dropdown.
|
|
Note: If all certificates generated under the Unified Certification Profile have been revoked, the ‘Certificate Type’ dropdown also displays the ‘All’ option. This option can be used to reissue all revoked certificates at once. If only selected certificates were revoked, the ‘Certificate Type’ dropdown displays only those certificates. |
After selecting the certificate(s), select the ‘Are you sure…’ checkbox and click ‘View Request’. The system opens the certificate request in Edit mode.

You can change the information in all sections as per your requirement. You can navigate to the next sections by clicking the ‘>’ button.
On the last section of the certificate request the system displays the ‘Reissue’ button.
|
|
Note: If the ‘All’ option is selected in the ‘Certificate Type’ dropdown, the ‘Certificate Validity’ screen displays all certificates along with their respective validity periods. |

Click the button to reissue the certificate(s). The system displays the ‘Certificate Action’ dialog on the screen. If required, enter an optional message in the ‘Message’ box, and then click ‘Reissue’.

The certificate(s) will be reissued, and a ‘Certificate Reissued’ alert will appear on the screen. The newly issued certificate will appear in the ‘Certificates’ listing in the Admin Portal.
Expand Requests > Certificate Requests from the left-tree menu in the Admin Portal. The Certificate Requests listing screen will appear.
The certificates generated using a Unified Certification Profile are grouped under a single main request number in the ‘Certificate Requests’ listing.
A ‘+’ button appears next to the main request number. Click the ‘+’ button to expand the request and view the list of all certificates generated under the Unified Certification Profile. Each certificate in the list has its own request number.

To rekey one or more certificates generated using a Unified Certification Profile, click the three-dot
button next to the main request number and select ‘View Request’.
The system opens the certificate request. Click on the ‘More Actions’ button.

A dialog titled ‘Certificate Action’ appears on the screen.

Select ‘Rekey Certificate’ option from the ‘Action’ dropdown. Then, select the certificate that you want to rekey from the ‘Certificate Type’ dropdown. You can either select an individual certificate from the dropdown to rekey or select the ‘All’ option to rekey all certificates in the list.
After that, select the ‘Are you sure you want to rekey the selected certificate(s)?’ checkbox and click the ‘View Request’ button.

The system will open the certificate in View mode. Navigate to the last section of the request by clicking the next ‘>’ button. The rekey button will appear.

Click the ‘Rekey’ button. The system will display the ‘Certificate Rekey’ dialog on the screen. If required, enter an optional message in the ‘Message’ box, and then click ‘Rekey’.

The certificate(s) will be rekeyed, and a ‘Certificate Rekeyed’ alert will appear on the screen. The rekeyed certificate will appear in the ‘Certificates’ listing in the Admin Portal.
To renew a certificate before its expiration, you need to first open the certificate request generated from the Web RA system.
To do this, expand Requests > Certificate Requests from the left-tree menu in the Admin portal.
The certificates generated using a Unified Certification Profile are grouped under a single main request number in the Issued Certificates listing. A ‘+’ button appears next to the main request number. Click the ‘+’ button to expand the request and view the list of all certificates generated under the Unified Certification Profile. Each certificate in the list has its own request number.

To renew one or more certificates generated using a Unified Certification Profile, click the three-dot
button next to the main request number and select ‘Renew Certificate’.
The system opens the certificate request. Click on the ‘More Actions’ button.

A dialog titled ‘Certificate Action’ appears on the screen.

Select ‘Renew Certificate’ option from the ‘Action’ dropdown. Then, select the certificate that you want to rekey from the ‘Certificate Type’ dropdown. You can either select an individual certificate from the dropdown to renew or select the ‘All’ option to renew all certificates in the list.
After that, select the ‘I have reviewed and verified the renewal request’ checkbox and click the ‘Renew’ button.
The certificate will be renewed, and the system will display a 'Certificate Renewed' alert on the screen.
How to Generate a Token-based Certificate
To create token-based certificate request using the Unified Certification Profile, expand Requests > Certificate Requests from the left-tree menu in the Admin portal. Then click the ‘+’ button from the grid header.

The system displays the ‘Create Request’ screen. Select your ‘Enterprise’ from the ‘Enterprise Name’ drop down, and select the Unified Certification Profile from the ‘Certificate Type’ dropdown.

The system displays all the certification profiles selected under the Unified Certification Profile, along with their Key Store and Validity Period details.
|
|
Note: If you want to generate a certificate request from the Admin Portal using a Unified Certification Profile, you can generate certificates only for MSCAPI-type or Token-based profiles. The system does not allow certificate generation for ‘Server-side Keys & Certificates’ profiles from the Admin Portal. |
|
|
Note: Go Sign Desktop version 8.4.2.1 is required to generate certificates from a Unified Certification Profile containing Token-based or MSCAPI-type certification profiles. |
|
|
Note: A checkbox titled ‘Generate a certificate on behalf of the user’ will appear on this screen if the "Allow operators to create certificates on behalf of the user and facilitate automatic assignment" policy is enabled in the Enterprise > Policies > Requests section. If you enable this checkbox, you will be asked to provide information about the user for whom the certificate is being generated at the end of the certificate request creation process. |

Click the ‘Create’ button to proceed.
The Subject Distinguished Name (SDN) screen appears on the screen.

|
|
Note: The system combines the SDN fields configured in all the certification profiles selected in the Unified Certification Profile and displays them on the ‘Subject Distinguished Name (SDN)’ screen. If the same SDN field is configured in multiple certification profiles, that field is displayed only once on the SDN screen during certification request creation. For example, if the Common Name SDN is configured in two certification profiles, the ‘Common Name’ field will appear only once on the SDN screen. The SDN fields displayed on the SDN screen are not included in all the certificates generated using the Unified Certification Profile. Each certificate will contain only the SDN fields configured in its respective certification profile. For example, if the Common Name SDN is configured in one certification profile but not in another, the ‘Common Name’ field will be displayed on the SDN screen, but the certificate generated using the certification profile without the Common Name configuration will not contain the Common Name attribute. Enter the information in the SDN fields as per your requirement and click the next ‘>’ button to proceed to the Subject Alternative Name (SAN) screen. |

|
|
Note: The system combines the SAN fields configured in all the certification profiles selected in the Unified Certification Profile and displays them on the ‘Subject Alternative Name (SAN)’ screen. If the same SAN field is configured in multiple certification profiles, that field is displayed only once on the SAN screen during certification request creation. For example, if the Domain Names (DNS) field is configured in two certification profiles, the ‘Domain Names (DNS)’ field will appear only once on the SAN screen. The SAN fields displayed on the SAN screen are not included in all the certificates generated using the Unified Certification Profile. Each certificate will contain only the SAN fields configured in its respective certification profile. For example, if the Domain Names (DNS) field is configured in one certification profile but not in another, the ‘Domain Names (DNS)’ field will be displayed on the SAN screen, but the certificate generated using the certification profile without the Domain Names (DNS) configuration will not contain the Domain Names (DNS) attribute. Enter the details in the SDN fields as per your requirement and click the next ‘>’ button to proceed to the Certificate Validity screen. |

The validity period of each certification profile is displayed on this screen. The ‘Validity Period’ field appears enabled or disabled according to the configuration of each certification profile.Click the '>' button to proceed to the 'Vetting Form' screen.

The Vetting Form screen only appears if 'Manual Vetting' configuration is selected in the certification profile. Enter the details required by the vetting form and click the '>' button to proceed to the "User Information' screen.
|
|
Note: The ‘User Information’ screen appears only if the ‘Generate a certificate on behalf of the user’ checkbox is enabled after the selection of Enterprise and Certificate Type. |

On this screen, you are required to enter or select the Name, Email, Citizen ID, Mobile Number, and Role of the user for whom the certificate is being generated.
After entering the required details, click ‘Generate’. The system displays a 'Go Sign Token' dialog on the screen.

By default, the token attached to your computer appears in the ‘Token’ dropdown. If more than one token is attached to your computer, all the attached tokens appear in the dropdown. In this case, you can select the required token from the ‘Token’ dropdown.
Once you have selected the required token, click ‘OK’. The system generates the certificate and displays the 'Certificate imported into Token' success alert on the screen.
When the certificate is generated on behalf of a user, the system handles the user's account based on their existing account and enterprise membership status. The user receives an email confirming the certificate generation and, where applicable, an email to activate their account. The system also resets the PIN and sends the newly generated PIN to the user by email.
- If the certificate is being created for a user who does not exist in the system, the system creates a new account for the user along with the certificate. The user receives an account activation email.
- If the user already has a registered account in the Web RA system, only the certificate is created. The user is notified by email about the certificate generation.
- If the user exists in the system but is not part of the enterprise where the certificate is being created, the system sends an invitation for the user to join that enterprise and generates the certificate.

To view the details of the toke, click the 'Token Information' button. You can also view the details of the token from the "Token Management' section in the Admin portal.
|
|
Note: If ‘Dual Control’ is enabled for the ‘Requests’ section, the certificate request is submitted to the Dual Control Operator for approval. Before approving the request, the Dual Control Operator is required to select the token from the ‘Go Sign Token’ dialog. |
Dual Control
If Dual Control is enabled for the 'Requests' module, then the certificate request will be submitted to the Dual Control operator for approval.
In case of Dual Control, the system displays 'Approve' button in place of 'Generate' during the certificate request creation, as displayed in the image below:

Click the 'Approve' button to proceed.
|
|
Note: If a Subscriber Agreement is configured in any or all of the profiles, each agreement is displayed on the screen one by one. You must agree to all the agreements to generate the certificates. |

The system displays a dialog titled 'Approve Request' on the screen. Select the 'I have reviewed and verified the following details" checkbox and click 'Ok'.

The system displays a 'Go Sign Token' dialog on the screen.

By default, the token attached to your computer appears in the ‘Token’ dropdown. If more than one token is attached to your computer, all the attached tokens appear in the dropdown. In this case, you can select the required token from the ‘Token’ dropdown.
Once you have selected the required token, click ‘OK’. The certificate request will be submitted for approval from the dual control operator.
Navigate to the Dual Controls > Requests module from the left-tree menu in the Admin portal.
Click the three-dot button next to the certificate request that requires approval and select 'View Request'. The system opens the certificate request in read-only mode.

To approve the certificate request, click the next '>' button to navigate to the last tab of request. Click 'Approve'.

The system displays a dialog titled 'Approve Request' on the screen. Select the 'I have reviewed and verified the following details" checkbox and click 'Ok'.

The system displays a 'Go Sign Token' dialog on the screen.

By default, the token attached to your computer appears in the ‘Token’ dropdown. If more than one token is attached to your computer, all the attached tokens appear in the dropdown. In this case, you can select the required token from the ‘Token’ dropdown.
Once you have selected the required token, click ‘OK’. The system generates the CSR, resets the PIN, and displays the 'Certificate imported into Token' success alert on the screen.
