Certificate
A digital certificate is a digitally signed credential that binds an identity to a public key and supports authentication or secure communication.
Real-World Cryptography
A digital certificate is a signed data structure that binds an identity or domain name to a public key.
- How it is used
- Authenticates website identities during TLS handshakes through the web PKI.
- How deep it goes
- Explains issuance, trust chains, certificate contents, encodings, inspection, and CA failure risks without implementation-level validation details.
- Examples
- Uses Google’s certificate chain, Chrome’s Certificate Viewer, OpenSSL output, domain-validation files, and PEM-encoded certificate data.
- What you can do after
- Evaluate/understand how browsers authenticate domains and inspect certificate chains, fields, formats, and trust relationships.
ASP.NET Core in Action, 3e
An HTTPS certificate is a digital certificate used to authenticate a server and enable encrypted HTTPS communication.
- How it is used
- Supports HTTPS traffic protection and browser trust for local ASP.NET Core development and production deployment.
- How deep it goes
- Explains key pairs and certificate chains, then configures development and production certificates; leaves provider-specific issuance steps to provider documentation.
- Examples
- Uses a local certificate trust command, a browser warning, and JSON configuration for a Kestrel .pfx certificate.
- What you can do after
- Operate/configure HTTPS certificates for local development and direct Kestrel deployment, while recognizing when a reverse proxy can handle them.
Acing the Certified Kubernetes Administrator Exam, Second Edition
A certificate is a digitally signed credential used to establish identity and support authenticated communication.
- How it is used
- Authenticates kubectl users and cluster components communicating with the Kubernetes API.
- How deep it goes
- Explains CA trust and client/server roles, then traces certificate files and user issuance through a CSR; it does not develop cryptographic internals.
- Examples
- Uses kubelet and API server certificate files, plus a user CSR whose issued certificate is tested through kubectl.
- What you can do after
- Build it from scratch with OpenSSL and a Kubernetes CSR, add the issued client certificate to kubeconfig, and test access.
Read how Acing the Certified Kubernetes Administrator Exam, Second Edition explains certificate →
Building Web APIs with ASP.NET Core
A TLS certificate is a digitally signed credential that binds an identity to a public key for authenticated encrypted connections.
- How it is used
- Secures the visitor-to-CDN and CDN-to-origin connections for a deployed web API.
- How deep it goes
- Distinguishes automatic edge certificates from manually installed origin certificates, but stops short of certificate-generation steps.
- Examples
- Uses Cloudflare’s two certificates and a Windows VM returning a 522 error before its web server is configured.
- What you can do after
- Operate/configure it by placing an origin certificate on the web server while relying on Cloudflare’s automatic edge certificate.
Read how Building Web APIs with ASP.NET Core explains certificate →
Build Python Web Apps with Streamlit
A digital certificate is a digitally signed document that binds a domain or other identity to a public key for authentication and encrypted communication.
- How it is used
- Secures a deployed Elastic Beanstalk app by enabling HTTPS without browser warnings.
- How deep it goes
- Explains website identity, domain validation, certificate requests, and listener configuration, but defers single-instance HTTPS setup.
- Examples
- Uses www.factfrenzyapp.com, DNS CNAME validation, AWS Certificate Manager, and a port-443 load-balancer listener.
- What you can do after
- Operate/configure AWS Certificate Manager and Elastic Beanstalk to issue and attach a certificate for HTTPS.
Read how Build Python Web Apps with Streamlit explains certificate →
Hacking Cryptography
A digital certificate is a signed data structure that binds a public key to an identified subject and related metadata.
- How it is used
- Solves scalable digital identity by extending browser trust from known root keys to website keys.
- How deep it goes
- Explains issuer–subject structure, signed metadata, trust anchors, and certificate chains without detailing certificate formats or validation procedures.
- Examples
- Uses bank.com, Alice-and-Bob trust delegation, browser root keys, and website signature chains.
- What you can do after
- Evaluate how a trusted root can establish identity for a website through signed public-key attestations.
WordPress Power Toolkit: Harness AI to build next-level websites
A certificate is a credential issued to recognize completion of a course or fulfillment of specified learning requirements.
- How it is used
- Uses certificates to recognize learning completion or secure online commerce and customer information.
- How deep it goes
- Distinguishes completion credentials from SSL security benefits, but stops short of explaining certificate installation or issuance procedures.
- Examples
- Uses Coursera completion certificates, browser padlocks, secure online stores, and fraudulent copied websites as examples.
- What you can do after
- Evaluate whether a certificate represents learning completion or website security, and recognize its practical purpose.
Read how WordPress Power Toolkit: Harness AI to build next-level websites explains certificate →
100 SQL Server Mistakes and How to Avoid Them
A certificate is a cryptographic object containing a public key and identity information that can support encryption or authentication.
- How it is used
- Protects symmetric keys for encrypted data and identifies the encryption material used for SQL Server backups.
- How deep it goes
- Explains certificate placement and operational handling, then demonstrates creation, backup, and use without developing cryptographic theory.
- Examples
- Uses backup encryption and employee-salary column encryption as concrete certificate applications.
- What you can do after
- Operate/configure SQL Server encryption by creating, backing up, and assigning certificates to backup or data-encryption workflows.
Read how 100 SQL Server Mistakes and How to Avoid Them explains certificate →
Data Pipelines with Apache Airflow, Second Edition
A digital certificate is a signed data structure that binds an identity to a public key and includes information for validating that binding.
- How it is used
- Secures Airflow's public API endpoint by enabling HTTPS and helping browsers validate the server.
- How deep it goes
- Explains public keys, HTTPS handshakes, self-signing, trust warnings, and configuration, but not certificate-authority internals.
- Examples
- Uses browser locks and warnings, localhost:8080, an OpenSSL command, and Airflow SSL environment variables.
- What you can do after
- Operate/configure Airflow HTTPS with certificate and private-key files, generate a self-signed certificate, and recognize trust warnings.
Read how Data Pipelines with Apache Airflow, Second Edition explains certificate →
Logs and Telemetry
A digital certificate is a signed credential that binds an identity to a public key for authenticated communication.
- How it is used
- Secures Fluent Bit network inputs so transmitted sensitive log data is protected.
- How deep it goes
- Explains TLS flags, certificate paths, CA verification, self-signed certificates, and lifecycle concerns without detailing certificate generation.
- Examples
- Uses a Fluent Bit HTTPS input with certificate, key, CA path, and tls.verify settings.
- What you can do after
- Operate a TLS-enabled Fluent Bit HTTP input and select appropriate CA verification settings.
Kubernetes for Developers
A TLS certificate is a digital certificate that authenticates a network endpoint and supports Transport Layer Security connections.
- How it is used
- Provides HTTPS endpoints while allowing an Ingress to handle TLS instead of configuring certificates inside applications.
- How deep it goes
- Explains certificate and key storage, Secret references, termination choices, and self-signed testing, but not certificate-authority procedures in detail.
- Examples
- Uses OpenSSL-generated self-signed files, kubectl Secret creation, and an Ingress hostname configuration.
- What you can do after
- Operate/configure an Ingress HTTPS endpoint by creating a TLS Secret and referencing it from an Ingress.
Learn Docker in a Month of Lunches, Second Edition
A digital certificate binds a domain identity to a cryptographic public key for authenticating a network endpoint.
- How it is used
- Terminates SSL centrally in a reverse proxy serving containerized applications over HTTPS.
- How deep it goes
- Explains generation, mounting, configuration, and redirection, but defers detailed protocol and cipher choices.
- Examples
- Uses image-gallery.local, Docker certificate generation, Nginx configuration, HTTP redirection, and a browser trust warning.
- What you can do after
- Operate a local HTTPS endpoint by generating a self-signed certificate and configuring Nginx to serve it.
Read how Learn Docker in a Month of Lunches, Second Edition explains certificate →
Google Anthos in Action
A certificate is a digitally signed credential that binds an identity to a public key or other authenticated information.
- How it is used
- Secures service-to-service communication by authenticating workloads and supporting a zero-trust posture.
- How deep it goes
- Defines certificate ownership and trust, then explains root, delegated, and configurable CA deployment options.
- Examples
- Uses Istio’s self-signed default root and enterprise configurations with existing root or delegated CA certificates.
- What you can do after
- Operate/configure Istio certificate authorities to provision identities for workloads and integrate organizational trust.
.NET in Action, Second Edition
A certificate is a digitally signed credential that binds an identity to a public key for establishing authenticated secure connections.
- How it is used
- Secures HTTP traffic by enabling authenticated HTTPS connections for development and publicly exposed services.
- How deep it goes
- Explains trust requirements, development installation, and HTTPS redirection, but does not detail certificate internals.
- Examples
- Uses `dotnet dev-certs https --trust`, `app.UseHttpsRedirection()`, and a 307 redirect with an HTTPS location.
- What you can do after
- Operate/configure HTTPS in ASP.NET Core using development certificates, trusted production certificates, and redirection middleware.
Read how .NET in Action, Second Edition explains certificate →
Authorization in Action
A digital certificate is a signed data record that binds an identity or domain name to a public key.
- How it is used
- Authenticates websites and applications to preserve trust in client-server relationships.
- How deep it goes
- Explains domain binding, public-key use, trusted issuers, browser verification, and common failure modes.
- Examples
- Uses the browser lock, a legitimate website connection, and the deceptive domain twitter.com.info as examples.
- What you can do after
- Evaluate website authenticity by inspecting certificate trust and the requested domain together.
Related concepts
- certification authorityproduced by · A certification authority is a trusted entity that verifies identities and issues digitally signed certificates binding public keys to identities or domains.
- public keyhas part · A public key is the openly distributable component of an asymmetric cryptographic key pair, used for encryption, authentication, or signature verification.
- self-signed certificateincludes · A self-signed certificate is a digital certificate whose signature is created by the same entity and key identified by the certificate rather than by a certificate authority.
- TLSused by · Transport Layer Security (TLS) is a cryptographic protocol that protects network communications through confidentiality, integrity, and authentication of communicating endpoints.
- mutual TLSused by · Mutual TLS is a Transport Layer Security configuration in which both communicating endpoints authenticate each other using digital certificates.
- public-key infrastructureused by · Public-key infrastructure is a framework of authorities, certificates, keys, policies, and procedures for establishing and managing public-key trust and digital identities.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.