<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Authentication on Claes Jonsson</title>
    <link>/categories/authentication/</link>
    <description>Recent content in Authentication on Claes Jonsson</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 24 Feb 2017 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="/categories/authentication/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Trust between Event Driven Microservices using JWT</title>
      <link>/blog/trust-between-event-driven-microservices-using-jwt/</link>
      <pubDate>Fri, 24 Feb 2017 00:00:00 +0000</pubDate>
      
      <guid>/blog/trust-between-event-driven-microservices-using-jwt/</guid>
      <description>&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;
&lt;p&gt;In the &lt;a href=&#34;../../blog/establishing-trust-between-microservices/&#34;&gt;previous post&lt;/a&gt; in this &lt;a href=&#34;../../categories/jwt&#34;&gt;series of posts&lt;/a&gt; about JWTs, I presented an example of how JWTs can be used to establish trust between microservices. In this post I will show an example how this can also be used in an event driven microservice system.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Establishing Trust between Microservices using JWT</title>
      <link>/blog/establishing-trust-between-microservices/</link>
      <pubDate>Wed, 15 Feb 2017 00:00:00 +0000</pubDate>
      
      <guid>/blog/establishing-trust-between-microservices/</guid>
      <description>&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;
&lt;p&gt;In case you are unfamiliar with JWT (JSON Web Tokens) you can think of them as credentials you can use whenever a proxy or stand-in need to represent a user of any kind; human, another microservice or another system altogether. Besides the token itself, they can contain additional information that is cryptographically verifiable, meaning the information, whether is authorization claim, service request data or any other information, is secure against tampering.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Introduction To JWT</title>
      <link>/blog/introduction-to-jwt/</link>
      <pubDate>Tue, 07 Feb 2017 00:00:00 +0000</pubDate>
      
      <guid>/blog/introduction-to-jwt/</guid>
      <description>&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;
&lt;p&gt;&lt;em&gt;From the introduction at 

    
        
    

    &lt;a href=&#34;https://jwt.io/&#34; target=&#39;_blank&#39;&gt;jwt.io&lt;/a&gt;

:&lt;/em&gt;&lt;br&gt;
&amp;ldquo;&lt;strong&gt;JSON Web Token (JWT)&lt;/strong&gt; is an open standard 

    
        
    

    &lt;a href=&#34;https://tools.ietf.org/html/rfc7519&#34; target=&#39;_blank&#39;&gt;(RFC 7519)&lt;/a&gt;

 that defines a compact and self-contained way for securely transmitting information between parties as a JSON object. This information can be verified and trusted because it is digitally signed. JWTs can be signed using a secret (with the HMAC algorithm) or a public/private key pair using RSA.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;So what is it really and how can you benefit from them?&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>