Bonnes Pratiques Web & Cloud

Getting a certificate for a lower environment could be difficult due to the costing factors, but there is a way by which you can get a wildcard certificate and configure it with your website.

You can implement a PKI solution by using the AD CS Windows Server role. 

PKI (Public Key Infrastructure) is the combination of software, encryption technologies, processes, and services that enables an organization to secure its data, communications, and business transactions. PKI relies on the exchange of digital certificates between authenticated users and trusted resources. You use certificates to secure data and to manage identification credentials from users and computers both within and outside of your organization.

AD CS Windows Server role enables scenarios such as secure wireless network, virtual private network, internet protocol security, network access protection, and encrypting file system.

Today we are going to see how to generate a wildcard certificate. There are two ways: one way is to generate it by using IIS with Internal CA, and another way is to create a wildcard certificate by using MMC with internal CA.  

Comme le certificat « Let’s encrypt » est installé par défaut, votre site web hébergé chez OVH existe désormais en http mais aussi en HTTPS.
Pourquoi ces deux versions de votre site posent-elles un problème ?

Les moteurs de recherche associent le fait d’avoir le même contenu sur plusieurs URL distinctes à une volonté d’améliorer son référencement naturel. La duplication de contenu, ou duplicate content est de ce fait pénalisée par les moteurs de recherche.
Vos efforts pour bien positionner votre site web sur Google risquent de ne plus payer !
Votre site en HTTP ne s’affiche pas correctement. Vous avez peut-être un problème de mixed content. Certains de vos éléments sont encore sur une url en http et de ce fait les navigateurs comme Google Chrome ou Mozilla Firefox ne les chargent pas.

Looking at a dataset of 350 million ssl connections inspires some initial questions:

L'autorité de certification Let's Encrypt annonce que le très populaire server HTTP Apache supportera bientôt le protocole ACME.

PKI : Infrastructure à clés publiques

It has long been a dream of ours for there to be a standardized protocol for certificate issuance and management. That dream has become a reality now that the IETF has standardized the ACME protocol as RFC 8555. I’d like to thank everyone involved in that effort, including Let’s Encrypt staff and other IETF contributors.

Having a standardized protocol for certificate issuance and management is important for two reasons. First, it improves the quality of the software ecosystem because developers can focus on developing great software for a single protocol, instead of having many pieces of less well maintained software for bespoke APIs.