Part 1 turns a client certificate into a Kong consumer, with limits and access per tier and the caller’s identity passed to your backend. Part 2 covers the other direction: Kong presenting its own certificate to an upstream that only accepts mTLS. Both use the same companion repository, kong-mtls.

A personal series. Views are my own; this is not official Kong documentation.