<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div>
<blockquote type="cite" class="">
<div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Nate
- you said you had reservations about JWT. Can you share your thinking? It can be out of band if you'd rather.</span></div>
</blockquote>
</div>
<br class="">
<div class="">This is not deeply uninformed, but I've gone down in writing with worse.</div>
<div class=""><br class="">
</div>
<div class="">Things I don't like:</div>
<div class=""><br class="">
</div>
<div class="">A) 3-character fields in the tokens themselves</div>
<div class="">B) Base 64 encoding with a special character delimiter(the period . ) and fixed "A.B.C" without any indication about what A, B, or C is, or any way to change it</div>
<div class=""><br class="">
</div>
<div class=""><a href="https://scotch.io/tutorials/the-anatomy-of-a-json-web-token" class="">https://scotch.io/tutorials/the-anatomy-of-a-json-web-token</a></div>
<div class=""><br class="">
</div>
<div class="">C) If you're using OAuth, why not just use the built-in bearer tokens?</div>
</body>
</html>