<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
<channel>

<title>Understanding the &#39;cnf&#39; Field in JWT</title><link>http://ods-qa.openlinksw.com:443/weblog/imitko/?id=27</link><description>Understanding the &#39;cnf&#39; Field in JWT
The &#39;cnf&#39; (confirmation) field in a JWT (JSON Web Token) is used to bind the token to a specific key, ensuring that the token can only be used by the party possessing the corresponding private key. This enhances the security of the token.
The &#39;cnf&#39; field typically contains one or more of the following claims:


  x5t: The thumbprint of an X.509 certificate.

  jkt: The thumbprint of a JWK (JSON Web Key).

Here is an example of a &#39;cnf&#39; field:
{
  &amp;quot;cnf&amp;quot;: {
    &amp;quot;x5t&amp;quot;: &amp;quot;9G7d4I4cPbTDnYrqFhJDBpDeQHw&amp;quot;,
    &amp;quot;jkt&amp;quot;: &amp;quot;SWV4YjhZZlZGUVM1bzV5L0wzd3BtNHdNcnpBPQ&amp;quot;
  }
}
In this example, the &#39;cnf&#39; field includes both an X.509 certificate thumbprint and a JWK thumbprint, binding the token to the corresponding keys.</description><pubDate>Fri, 12 Jul 2024 17:57:54 GMT</pubDate><generator>Virtuoso Universal Server 08.03.3334</generator><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mitko Iliev</dc:creator><image><title>Understanding the &#39;cnf&#39; Field in JWT</title><url>http://ods-qa.openlinksw.com:443/weblog/public/images/vbloglogo.gif</url><link>http://ods-qa.openlinksw.com:443/weblog/imitko/?id=27</link><description /><width>88</width><height>31</height></image>
<!-- ERROR SQLState: VECSL SQLMessage: VECSL: Internal error, ssl referenced before set, please report query to support -->
</channel>
</rss>
