<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Bachi</title>
    <description>The latest articles on DEV Community by Bachi (@bachiauth0).</description>
    <link>https://dev.to/bachiauth0</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F155519%2F41d525e3-df1b-4708-b244-3f614041f5a4.png</url>
      <title>DEV Community: Bachi</title>
      <link>https://dev.to/bachiauth0</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/bachiauth0"/>
    <language>en</language>
    <item>
      <title>Node.js v14: What's New?</title>
      <dc:creator>Bachi</dc:creator>
      <pubDate>Tue, 05 May 2020 23:15:03 +0000</pubDate>
      <link>https://dev.to/auth0/node-js-v14-what-s-new-2nbm</link>
      <guid>https://dev.to/auth0/node-js-v14-what-s-new-2nbm</guid>
      <description>&lt;p&gt;That's right! Node.js version 14 is here! 🎉&lt;/p&gt;

&lt;p&gt;Whether you have upgraded your Node version already or are thinking about doing it soon, let's discuss some of the things that this new version gives us! We'll even chat about older versions and what to expect there in the coming months.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://auth0.com/blog/nodejs-v-14-whats-new/?utm_source=dev&amp;amp;utm_medium=sc&amp;amp;utm_campaign=nodejs_14" rel="noopener noreferrer"&gt;Read on 📖&lt;/a&gt;&lt;/p&gt;

</description>
      <category>node</category>
      <category>javascript</category>
    </item>
    <item>
      <title>Securing Single Page Applications with Refresh Token Rotation</title>
      <dc:creator>Bachi</dc:creator>
      <pubDate>Wed, 15 Apr 2020 20:15:31 +0000</pubDate>
      <link>https://dev.to/auth0/securing-single-page-applications-with-refresh-token-rotation-2amg</link>
      <guid>https://dev.to/auth0/securing-single-page-applications-with-refresh-token-rotation-2amg</guid>
      <description>&lt;p&gt;TL;DR&lt;br&gt;
The ability to maintain seamless experiences for end-users in Single Page Applications (SPAs) is often business-critical and can have an enormous impact on revenue.&lt;br&gt;
New browser privacy controls adversely impact the user experience in SPAs by preventing access to third-party cookies, which are used for silent authentication.&lt;br&gt;
Auth0 now offers an alternative--Refresh Token Rotation--that provides a secure method for using refresh tokens in SPAs while providing end-users with seamless access to resources without the disruption in UX caused by browser privacy technology like ITP.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://auth0.com/blog/securing-single-page-applications-with-refresh-token-rotation/?utm_source=dev&amp;amp;utm_medium=sc&amp;amp;utm_campaign=refresh_tokens" rel="noopener noreferrer"&gt;Read on 📖&lt;/a&gt;&lt;/p&gt;

</description>
      <category>tokens</category>
      <category>oauth2</category>
    </item>
    <item>
      <title>Technical Strategies for Migrating Users to Auth0</title>
      <dc:creator>Bachi</dc:creator>
      <pubDate>Wed, 15 Apr 2020 19:03:42 +0000</pubDate>
      <link>https://dev.to/auth0/technical-strategies-for-migrating-users-to-auth0-pcn</link>
      <guid>https://dev.to/auth0/technical-strategies-for-migrating-users-to-auth0-pcn</guid>
      <description>&lt;p&gt;TL;DR: This tutorial will walk you through options for migrating users into Auth0, focusing specifically on the challenges you may face when migrating from on-premises identity solutions.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://auth0.com/blog/technical-strategies-for-migrating-users-to-auth0/?utm_source=dev&amp;amp;utm_medium=sc&amp;amp;utm_campaign=migrating_users" rel="noopener noreferrer"&gt;Read on 📖&lt;/a&gt;&lt;/p&gt;

</description>
      <category>migration</category>
      <category>coding</category>
    </item>
    <item>
      <title>Build an Event Planner App with Vue.js, Firebase, and Auth0's Passwordless</title>
      <dc:creator>Bachi</dc:creator>
      <pubDate>Wed, 15 Apr 2020 18:59:51 +0000</pubDate>
      <link>https://dev.to/auth0/build-an-event-planner-app-with-vue-js-firebase-and-auth0-s-passwordless-2obp</link>
      <guid>https://dev.to/auth0/build-an-event-planner-app-with-vue-js-firebase-and-auth0-s-passwordless-2obp</guid>
      <description>&lt;p&gt;TL;DR: To date, passwords and passcodes remain the most used means of gaining access to our protected accounts on the online platforms we love. However, if you are like me with loads of accounts across various online platforms, remembering all passwords can quickly become a herculean task mentally especially when certain online platforms require you to provide strong passwords with special characters, capitalized words, and numbers like you're trying to gain access to Fort Knox. Wouldn't it be wonderful not to have to remember passwords when logging into an application? That is the type of application we will be building in this article.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://auth0.com/blog/build-an-event-planner-app-with-vuejs-firebase-and-auth0s-passwordless/?utm_source=dev&amp;amp;utm_medium=sc&amp;amp;utm_campaign=vuejs_passwordless" rel="noopener noreferrer"&gt;Read on 📖&lt;/a&gt;&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>vue</category>
      <category>firebase</category>
    </item>
    <item>
      <title>Build an API in Rust with JWT Authentication</title>
      <dc:creator>Bachi</dc:creator>
      <pubDate>Wed, 15 Apr 2020 16:32:54 +0000</pubDate>
      <link>https://dev.to/auth0/build-an-api-in-rust-with-jwt-authentication-1556</link>
      <guid>https://dev.to/auth0/build-an-api-in-rust-with-jwt-authentication-1556</guid>
      <description>&lt;p&gt;Rust has picked up a lot of momentum since we last looked at it in 2015. Companies like Amazon and Microsoft have adopted it for a growing number of use cases. Microsoft, for example, sponsors the Actix project on GitHub, which is a general purpose open-source actor framework based on Rust. The Actix project also maintains a RESTful API development framework, which is widely regarded as a fast and performant web framework. Although the project was temporarily on hold in early 2020, the project ownership has moved to a new maintainer, and development continues.&lt;/p&gt;

&lt;p&gt;In this article, we will explore the actix-web web framework by writing a small CRUD API using it. Our API will be backed by a Postgres database using Diesel. Finally, we will implement authentication for our API using Auth0&lt;/p&gt;

&lt;p&gt;&lt;a href="https://auth0.com/blog/build-an-api-in-rust-with-jwt-authentication-using-actix-web/?utm_source=dev&amp;amp;utm_medium=sc&amp;amp;utm_campaign=rust_jwt" rel="noopener noreferrer"&gt;Read on 📖&lt;/a&gt;&lt;/p&gt;

</description>
      <category>rust</category>
      <category>jwt</category>
      <category>api</category>
    </item>
    <item>
      <title>Using xUnit to Test your C# Code</title>
      <dc:creator>Bachi</dc:creator>
      <pubDate>Tue, 07 Apr 2020 17:30:21 +0000</pubDate>
      <link>https://dev.to/auth0/using-xunit-to-test-your-c-code-3ek5</link>
      <guid>https://dev.to/auth0/using-xunit-to-test-your-c-code-3ek5</guid>
      <description>&lt;p&gt;TL;DR: This article will guide you in creating automated tests with xUnit for your C# applications. You will learn the basics of automated tests and how to create unit and integration tests.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://auth0.com/blog/xunit-to-test-csharp-code/?utm_source=dev&amp;amp;utm_medium=sc&amp;amp;utm_campaign=xunit_test" rel="noopener noreferrer"&gt;Read on 📖&lt;/a&gt;&lt;/p&gt;

</description>
      <category>dotnetcore</category>
    </item>
    <item>
      <title>Getting Started with Vue 3: Composition API</title>
      <dc:creator>Bachi</dc:creator>
      <pubDate>Mon, 23 Mar 2020 13:26:29 +0000</pubDate>
      <link>https://dev.to/auth0/getting-started-with-vue-3-composition-api-29d2</link>
      <guid>https://dev.to/auth0/getting-started-with-vue-3-composition-api-29d2</guid>
      <description>&lt;p&gt;The long-awaited Vue.js 3 is scheduled for release in the 1st quarter of 2020. The announcement of a new API, the Composition API, resulted in some controversy in the Vue community. It has since simmered down, but what is the Composition API anyway?&lt;/p&gt;

&lt;p&gt;Although Vue 3, in its entirety, hasn't been released yet, the Composition API is already out and ready to use. In this article, we'll take a look at why the Composition API was introduced, how it works, and how it compares to the options-based API. At the end, we'll build two versions of the same component: one with the Composition API and one with the options-based API!&lt;br&gt;
&lt;a href="https://auth0.com/blog/amp/getting-started-with-vue-3-composition-api/?utm_source=dev&amp;amp;utm_medium=sc&amp;amp;utm_campaign=vue_compapi" rel="noopener noreferrer"&gt;Read on 📖&lt;/a&gt;&lt;/p&gt;

</description>
      <category>vue</category>
      <category>api</category>
      <category>javascript</category>
    </item>
    <item>
      <title>Build a JAMstack App with Gatsby Cloud, DatoCMS, and Netlify</title>
      <dc:creator>Bachi</dc:creator>
      <pubDate>Tue, 17 Mar 2020 21:52:08 +0000</pubDate>
      <link>https://dev.to/auth0/build-a-jamstack-app-with-gatsby-cloud-datocms-and-netlify-5c01</link>
      <guid>https://dev.to/auth0/build-a-jamstack-app-with-gatsby-cloud-datocms-and-netlify-5c01</guid>
      <description>&lt;p&gt;TL;DR: In today's article, we are going to be building a JAMstack application using Gatsby Cloud and Netlify. Using the power of these two, we will see just how easy it is to go from ground zero to a fully deployed website. We will also go over the idea of JAMstack and how it's changing the way we think of web development.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://auth0.com/blog/build-a-jamstack-app-with-gatsby-cloud-datocms-and-netlify/?utm_source=dev&amp;amp;utm_medium=sc&amp;amp;utm_campaign=jamstack_app" rel="noopener noreferrer"&gt;Read on 📖&lt;/a&gt;&lt;/p&gt;

</description>
      <category>gatsby</category>
      <category>netlify</category>
      <category>jamstack</category>
    </item>
    <item>
      <title>Angular 9's Best Hidden Feature: Strict Template Checking</title>
      <dc:creator>Bachi</dc:creator>
      <pubDate>Tue, 10 Mar 2020 16:05:41 +0000</pubDate>
      <link>https://dev.to/auth0/angular-9-s-best-hidden-feature-strict-template-checking-666</link>
      <guid>https://dev.to/auth0/angular-9-s-best-hidden-feature-strict-template-checking-666</guid>
      <description>&lt;p&gt;We have likely read about some of the benefits of the Ivy compiler and runtime. It's faster. It makes smaller bundle sizes. And it has many other great new features that are introduced in Angular 9. Yet one of the most compelling and useful features is one we don't hear as often.&lt;/p&gt;

&lt;p&gt;What if Angular could find bugs in our existing code? Hidden bugs that we may not notice. Subtle bugs that could cause problems? Angular 9 and the Ivy compiler do just that.&lt;/p&gt;

&lt;p&gt;The new feature is known as strict template checking. Angular has been checking expressions and bindings within the templates of our applications for years. But with Angular 9, it finds and reports more errors than ever. It is pretty cool that we could have bugs in our templates right now, and this new feature reports them to us so we can fix them.&lt;/p&gt;

&lt;p&gt;Seeing is believing, so let's see some examples. We'll kick things off using Angular 8, and we'll progress to Angular 9. We'll also adjust some compilation settings. These differences help us see where Angular 9 can detect additional errors that Angular 8 could not.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://auth0.com/blog/angular-9s-best-hidden-feature-strict-template-checking/?utm_source=dev&amp;amp;utm_medium=sc&amp;amp;utm_campaign=angular9_stc" rel="noopener noreferrer"&gt;Read on 📖&lt;/a&gt;&lt;/p&gt;

</description>
      <category>angular</category>
      <category>javascript</category>
    </item>
    <item>
      <title>Securing AWS HTTP APIs with JWT Authorizers</title>
      <dc:creator>Bachi</dc:creator>
      <pubDate>Wed, 04 Mar 2020 18:07:40 +0000</pubDate>
      <link>https://dev.to/auth0/securing-aws-http-apis-with-jwt-authorizers-35no</link>
      <guid>https://dev.to/auth0/securing-aws-http-apis-with-jwt-authorizers-35no</guid>
      <description>&lt;p&gt;TL;DR: HTTP APIs — a new solution in AWS for building low-cost APIs — support JSON Web Token (JWT)-based authorization, and they integrate with external identity providers such as Auth0 for easy, industry-standard authorization practices. This tutorial will walk you through building an HTTP API using Amazon API Gateway and integrating it with Auth0 to restrict write access to authorized users.&lt;/p&gt;

&lt;p&gt;Introduction&lt;br&gt;
Let’s start with an obvious statement: building a modern API isn’t exactly a straightforward process. The list of requirements seems to grow: it should be performant, easily scalable, highly available, secure — and that’s before you get to writing your actual business logic!&lt;/p&gt;

&lt;p&gt;Thankfully, there’s a constantly growing ecosystem of tools offering solutions for building, securing, and deploying APIs. The AWS API Gateway service provides several solutions for this exact problem, and their most recent offering, HTTP APIs, is a simple, low-cost, low-latency solution for API configuration and deployment.&lt;/p&gt;

&lt;p&gt;Now, if you’re building an API, you’ll likely need to restrict endpoint access to at least some of your endpoints eventually. Identity-as-a-Service (IaaS) solutions, like Auth0, can easily handle authentication and authorization for a variety of applications, but how can they be integrated with services like API Gateway? That answer comes in the form of a new HTTP API feature supporting industry-standard authorization: JWT Authorizers.&lt;/p&gt;

&lt;p&gt;&lt;a href="//auth0.com/blog/securing-aws-http-apis-with-jwt-authorizers/?utm_source=twitter&amp;amp;utm_medium=sc&amp;amp;utm_campaign=aws_jwt"&gt;Read on 📖&lt;/a&gt;&lt;/p&gt;

</description>
      <category>jwt</category>
      <category>aws</category>
    </item>
    <item>
      <title>Securing gRPC-based Microservices in .NET Core</title>
      <dc:creator>Bachi</dc:creator>
      <pubDate>Wed, 26 Feb 2020 20:48:18 +0000</pubDate>
      <link>https://dev.to/auth0/securing-grpc-based-microservices-in-net-core-d3a</link>
      <guid>https://dev.to/auth0/securing-grpc-based-microservices-in-net-core-d3a</guid>
      <description>&lt;p&gt;TL;DR: This tutorial will show you how to integrate authentication and authorization in a .NET Core microservice scenario based on gRPC. You will go through the process of protecting the server endpoints and will learn how to authorize a gRPC client to make requests to it. &lt;/p&gt;

&lt;p&gt;The gRPC Framework&lt;br&gt;
Lately, gRPC is becoming quite popular since it allows you to build high performance distributed systems. Initially designed by Google to optimize communication within their internal service infrastructure, it is now an open-source project available for most common programming languages: from Java to Python, to PHP, to C#. In a nutshell, gRPC is a Remote Procedure Call framework (RPC framework) based on the HTTP/2 protocol to transport binary messages and on the Protocol Buffers, also known as Protobuf, to define service contracts. A mandatory requirement for a gRPC service is to accept only secure gRPC connections, such as TLS connections.&lt;/p&gt;

&lt;p&gt;Starting from .NET Core 3.0, Microsoft supports gRPC natively, so .NET Core developers can leverage this framework to build efficient microservices. The tutorial Implementing Microservices with gRPC and .NET Core 3.0 introduces you to the basics of using this framework with .NET Core. It shows you how to create a simple microservice that evaluates whether a customer is entitled to receive credit for a given amount and a client that makes requests to it.&lt;/p&gt;

&lt;p&gt;In this tutorial, you will take that project and will secure the communication between the client and the server by using Auth0.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://auth0.com/blog/securing-grpc-microservices-dotnet-core/?utm_source=dev&amp;amp;utm_medium=sc&amp;amp;utm_campaign=securing_grpc" rel="noopener noreferrer"&gt;Read on 📖&lt;/a&gt;&lt;/p&gt;

</description>
      <category>dotnet</category>
      <category>grpc</category>
      <category>microservices</category>
    </item>
    <item>
      <title>How to Integrate Auth0 with Oracle CX Commerce</title>
      <dc:creator>Bachi</dc:creator>
      <pubDate>Tue, 18 Feb 2020 18:42:52 +0000</pubDate>
      <link>https://dev.to/auth0/how-to-integrate-auth0-with-oracle-cx-commerce-37nl</link>
      <guid>https://dev.to/auth0/how-to-integrate-auth0-with-oracle-cx-commerce-37nl</guid>
      <description>&lt;p&gt;TL;DR: In this article, we are going to discuss how Oracle CX Commerce and Auth0 can now be connected! We will walk through that process to see just how we can accomplish that!&lt;/p&gt;

&lt;p&gt;Auth0 + Oracle CX Commerce&lt;br&gt;
Auth0 and Oracle have partnered together to find a great opportunity that brings added value to our users. Oracle and Auth0 now empower customers to leverage the Auth0 platform to add identity and access management capabilities to commerce storefronts that are built and hosted on CX Commerce.&lt;/p&gt;

&lt;p&gt;Oracle CX Commerce&lt;br&gt;
Okay, but what is Oracle CX Commerce? CX Commerce is a leading enterprise SaaS commerce solution -- scalable, flexible, cloud-native, and built to support both B2B and B2C. Want to build an enterprise, highly customizable, feature-rich digital commerce business? CX Commerce’s solution provides for all of that!&lt;/p&gt;

&lt;p&gt;&lt;a href="https://auth0.com/blog/how-to-integrate-auth0-with-oracle-cx-commerce/?utm_source=twitter&amp;amp;utm_medium=sc&amp;amp;utm_campaign=auth0_oraclecx" rel="noopener noreferrer"&gt;Read on 📖&lt;/a&gt;&lt;/p&gt;

</description>
      <category>oraclecx</category>
      <category>webdev</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
