GlobalSign Support

The following table has been created for the purpose of detailing our Vetting position. As we progress, we will need to consider a) Vetting capability with Q certs for Signature and eSeal and b) around Q4 2019, and introduction of Q Timestamping and QWAC.

Due to changes in Apple and Google Root Store Policies, as of September 1, 2020, newly issued SSL/TLS Certificates with a validity period greater than 13 months (397 days) are prohibited by policy and will not be trusted. Therefore, as of August 31, 2020, GlobalSign will stop issuing 2-year publicly trusted SSL/TLS Certificates.

This support article is about the technical documentation and additional resources for GlobalSign's Digital Signing Service (DSS).

In this article, we will provide some useful tools and commands that you can use to test connectivity from your AEG server to your database server. Testing connectivity to your database server is crucial in the following scenarios: You are working on a Proof of Concept (POC) stage with our Engineers and want to make sure that connectivity is working appropriately. You are working on implementing the AEG in your production environment and want to make sure that connectivity is working adequately. You believe the AEG server is not synchronizing with the database server, it is not showing the settings and features in the AEG Portal, or you find error logs in the Windows Event Viewer that are related to database connectivity.

As a GlobalSign customer, sometimes, you will encounter issues with Certificate deployment and installation through the AEG. One that is recurrent is when a Certificate cannot be installed because a computer receives it outside the Certificate validity period. This happens because the start validity date is in the future compared to the time the computer reads from its local source or its NTP source. As a result, the computer does not validate the Certificate correctly and denies its installation. In this article, we will discuss the main reasons around clock/time skew issues when you are making use of our AEG solution.

This article provides step-by-step instructions for ordering a new Client Certificate, such as a Code Signing, PersonalSign, or Document Signing Certificate. If this is not the solution you are looking for, please search for your solution in the search bar above.

When viewing the TLS Certificate hierarchy for sites secured with a GlobalSign TLS Certificate under our Root R3, some users may observe a 4-level certificate chain back to the SHA-1 GlobalSign Root R1. This article discusses how this happens, why it’s not a security risk that the TLS Certificate appears to be issued under the SHA-1 GlobalSign Root R1, and how to temporarily resolve the misleading certificate chain displayed by the Microsoft Certificate Viewer.

Frequently Asked Questions

In the past, Customers signing software or drivers that were to be executed in Windows Kernel Mode, could use any GlobalSign Code Signing Certificate along with the Microsoft Cross Certificate linking back to the GlobalSign Root R1. This Cross Certificate will expire on April 2021 and Microsoft will not be issuing trusted Cross Certificates for this purpose anymore.