Skip to main content

Part-1 VueJS JWT Auth Cookie - Access Token Usage

In this article, we will implement Vue3 application authentication with the JWT auth cookie. So in this portion, we mainly target access token utilization.

To know about Jwt authentication in vuejs like managing token using browser storage then check below mentioned articles.
Part2 Refresh Token In Vue3

HTTP Only JWT Cookie:

The HTTP only cookie is only accessible by the server application. Client apps like javascript-based apps can't access the HTTP-only cookie. So if we use authentication with HTTP only JWT cookie then we no need to implement custom logic like adding authorization header or storing token data, etc at our client application. Because once the user authenticated, that auth cookie will be automatically sent to the server by the browser on every API call.

Authentication API:

To implement JWT cookie authentication we need to set up an API. For that, I had created a mock authentication API(Using the NestJS Server framework). So download the Git repo mentioned below.
                                              NestJS Mock Auth API Repo
Now install the NestJS CLI into our system. Run the below command.
Command To Install NestJS CLI:

npm i -g @nestjs/cli
After downloading the Git repo, go to the root folder and run the following command to install packages
Install Packages:

npm install
Now run the below command to run our Authentication API.
Command To Run NestJS API:
npm run start:dev
We need to register our client domain in the NestJs API inside of cors settings.
src/main.ts:

Create A Vue3.0 Sample Application:

Let's begin our journey by creating a sample Vue3.0 application.
Vue CLI:
npm run -g @vue/cli
Command To Create Vue App:
vue create your_application_name

Install Required NPM Package:

Let's install the vue routing package
Vue Route Library:
npm install vue-router@4
Install vue store package
Vue Store Library:
npm install vuex@next --save
Install Axios package
Axios Library:
npm install axios

Configure Page Components And Routes:

To apply CSS let's use the bootstrap styling, so let's add the bootstrap CSS file reference on index.html in the 'public' folder.
public/index.html:(add at the end of head tag)
<link href="https://cdn.jsdelivr.net/npm/bootstrap@5.0.0-beta3/dist/css/bootstrap.min.css" rel="stylesheet" integrity="sha384-eOJMYsd53ii+scO/bJGFsiCZc+5NDVN2yr8+0RDqr0Ql0h+rP48ckxlpbzKgwra6" crossorigin="anonymous">
For our sample let's create page vue components like 'Login.vue' and 'Dashboard.vue'.

In 'Login.vue' vue component, let's add a form for user authentication.
src/components/Login.vue:(Html Part)
<template>
  <div>
    <h4>Login Form</h4>
    <form>
      <div class="mb-3">
        <label for="txtEmail" class="form-label">Email</label>
        <input
          type="text"
          class="form-control"
          id="txtEmail"
          aria-describedby="emailHelp"
          v-model="email"
        />
      </div>
      <div class="mb-3">
        <label for="txtPassword" class="form-label">Password</label>
        <input
          type="password"
          class="form-control"
          id="txtPassword"
          v-model="password"
        />
      </div>
      <button type="button" class="btn btn-primary" @click="login()">
        Submit
      </button>
    </form>
  </div>
</template>
  • Here created user authentication form. Enabled vue 2way binding using the 'v-model' attribute.
src/components/Login.vue:(Script Part)
<script>
export default {
  data() {
    return {
      email: "",
      password: "",
    };
  },
  methods: {
    login() {
      console.log(this.email, this.password);
    },
  },
};
</script>
  • Here added vue data-bind properties and also registered 'login' method.
In 'Dashboard.vue' component just add basic vue component skeleton code.
src/components/Dashboard.vue:(Html Part)
<template>
    <div>
        <h4>Dashboard Page</h4>
    </div>
</template>
src/components/Dashboard.vue:(Script Part)
<script>
export default {};
</script>
Our 'App.vue' will be our master layout where we can specify the common features like 'Menu', 'footer', etc.
src/App.vue:(Html Part)
<template>
  <div>
    <nav class="navbar navbar-expand-lg navbar-light bg-primary bg-gradient">
      <div class="container-fluid">
        
        <div class="collapse navbar-collapse" id="navbarSupportedContent">
          <ul class="navbar-nav me-auto mb-2 mb-lg-0">
            <li class="nav-item">
              <router-link to="/login" class="nav-link">Login</router-link>
            </li>
            <li>
              <router-link to="/dashboard" class="nav-link">Dashboard</router-link>
            </li>
          </ul>
        </div>
      </div>
    </nav>
    <router-view></router-view>
  </div>
</template>
  • Added bootstrap nav menu.
  • Used 'router-link' vue component for navigation links
  • The 'router-view' vue component, where our page vue components like 'Login.vue', 'Dashboard.vue' will be rendered.
src/App.vue:(Script Part)
<script>
export default {
  name: "App",
};
</script>
To configure routing let's add a new file like 'appRouter.js'.
src/appRouter.js:
import Login from "./components/Login.vue";
import Dashboard from "./components/Dashboard.vue";
import { createRouter, createWebHistory } from "vue-router";

const routes = [
  { path: "/", component: Login },
  { path: "/login", component: Login },
  { path: "/dashboard", component: Dashboard },
];

export const routeConfig = createRouter({
    history: createWebHistory(),
    routes: routes
});
  • To instantiate the vue router we need to use 'createRouter' method loads from the 'vue-router' library.
Now inject the route into our vue instance.
src/main.js:
import { createApp } from 'vue'
import App from './App.vue'
import * as appRouter from './appRouter'

const app = createApp(App)
app.use(appRouter.routeConfig);
app.mount('#app')

Basic Vuex Store Setup:

In the vue application best area for data, communication is the vuex store. So let's setup the vuex store for our sample as well.

So let's create a folder like 'store'. Inside 'store' create a new folder like 'modules'. Now 'modules' folder let's add our authentication store module file like 'auth.js'.
src/store/modules/auth.js:
const state = () => ({
  loginApiStatus: "",
});

const getters = {};

const actions = {};

const mutations = {};

export default {
  namespaced: true,
  state,
  getters,
  actions,
  mutations,
};
  • Here is our basic structure of auth module store. Here 'loginApiStatus' property added as state property.
Now create the root module store inside of the 'store' folder, then register our 'auth' store module in root store module.
src/store/index.js:
import { createStore } from "vuex";
import authModule from './modules/auth';

const store = createStore({
    modules:{
        auth: authModule
    }
});

export default store;
  • Initializes store using 'createStore' method that loads from 'vuex'. One key thing to remember is that the property name used to register the child store module, needs to be used as a namespace while invoking the child module store in our vue components.
Now inject the vuex store into our application vue instance.
src/main.js:
import { createApp } from 'vue'
import App from './App.vue'
import * as appRouter from './appRouter'
import store from './store/index'

const app = createApp(App)
app.use(appRouter.routeConfig);
app.use(store);
app.mount('#app')

Login API:

The endpoint of our user authentication looks like this:
http://localhost:3000/auth/login

Payload:
{
    "email":"naveen@techseeker.com",
    "password":"12345"
}
  • Since the authentication project is mocked, so please use the credentials mentioned above.

Logic To Invoking Login API:

To update the value in the 'loginApiStatus' state property let's create a mutation method.
src/store/modules/auth.js:
const mutations = {
  setLoginApiStatus(state, data) {
    state.loginApiStatus = data;
  },
};
Create a new store action method for invoking our login API.
src/store/modules/auth.js:
import axios from "axios";

const actions = {
  async loginApi({ commit }, payload) {
    const response = await axios
      .post("http://localhost:3000/auth/login", 
	  payload,{withCredentials: true, credentials: 'include'})
      .catch((err) => {
        console.log(err);
      });

    if (response && response.data) {
      commit("setLoginApiStatus", "success");
    } else {
      commit("setLoginApiStatus", "failed");
    }
  },
};
  • (Line: 4) The 'loginApi' method has 2 parameters. The first parameter is the 'commit' command and the next parameter is user payload(login credentials).
  • (Line: 7) On invoking the login API, we also sending additional data like 'withCredentials'. The 'withCredentials' must be used for cross-origin requests to add the endpoint cookies as headers.
  • (Line: 12-16) Invoking the mutation method like 'setLoginApiStatus'.
To access the 'loginApiStatus' state property, create a store getter method.
src/store/modules/auth.js:
const getters = {
  getLoginApiStatus(state) {
    return state.loginApiStatus;
  },
};
Now update our 'Login.vue' component to invoke the login API.
src/components/Login.vue:(Script Part)
<script>
import { mapActions, mapGetters } from "vuex";
export default {
  data() {
    return {
      email: "",
      password: "",
    };
  },
  computed: {
    ...mapGetters("auth", {
      getLoginApiStatus: "getLoginApiStatus",
    }),
  },
  methods: {
    ...mapActions("auth", {
      actionLoginApi: "loginApi",
    }),
    async login() {
      console.log(this.email, this.password);
      const payload = {
        email: this.email,
        password: this.password,
      };
      await this.actionLoginApi(payload);
      if(this.getLoginApiStatus == "success"){
        this.$router.push("/dashboard");
      }else{
        alert("failed")
      }
    },
  },
};
</script>
  • (Line: 2) Import 'mapGetters' and 'mapActions' from 'vuex' library.
  • (Line: 10-14) The best place to initialize 'mapGetters' is the vue computed property. Because computed props always watch for the latest changes.
  • (Line: 19-31) Calling the login API, and then checking for the status. On successful login navigating the user to the dashboard page.

Endpoint To Fetch Authenticated User Information:

In the API project, we have an endpoint to deliver the authenticated user information. NestJS API reads the auth cookie and extracts the jwt token and makes our client application request authenticated. So our user profile endpoint looks like below.
http://localhost:3000/user-profile

Consume User Profile Into The Vue Application:

Now after successful login of our user, we need to fetch some user information and we have to bind it to our application UI. Since we are using HttpOnly cookie jwt authentication, we must get the user information from the secured endpoint. This user information needs to be stored in our application in such a way it needs to access on every page easily.

Let's create some store state to save the user information.
src/store/modules/auth.js:
const state = () => ({
  loginApiStatus: "",
  userProfile:{
    id:0,
    lastName:"",
    firstName:"",
    email:"",
    phone:"",
  }
});
Let's create a mutation method to update the user information state.
src/store/modules/auth.js:
setUserProfile(state, data){
const userProfile = {
  id:data.id,
  lastName: data.lastName,
  firstName: data.firstName,
  email: data.email,
  phone: data.phone,
};
state.userProfile = userProfile
}
Let's create an action method to invoke the user profile API.
src/store/modules/auth.js:
async userProfile({commit}){
  const response = await axios
  .get("http://localhost:3000/user-profile",{withCredentials: true, credentials: 'include'})
  .catch((err) => {
	console.log(err);
  });

  if(response && response.data){
	commit("setUserProfile", response.data)
  }
}
Let's create a getter method to fetch user profile data.
src/store/modules/auth.js:
const getters = {
  // code hiden for display purpose
  getUserProfile(state){
    return state.userProfile;
  }
};
Now let's bind some user information to our application UI and also hide&show the menus based on user authentication as well.
src/App.vue:(Html Part)
<template>
  <div>
    <nav class="navbar navbar-expand-lg navbar-light bg-primary bg-gradient">
      <div class="container-fluid">
        <div class="collapse navbar-collapse" id="navbarSupportedContent">
          <ul
            class="navbar-nav me-auto mb-2 mb-lg-0"
            v-if="getUserProfile.id == 0"
          >
            <li class="nav-item">
              <router-link to="/login" class="nav-link">Login</router-link>
            </li>
          </ul>
          <ul
            class="navbar-nav me-auto mb-2 mb-lg-0"
            v-if="getUserProfile.id !== 0"
          >
            <li>
              <h5>
                <span class="badge bg-primary">{{ getUserProfile.email }}</span>
              </h5>
            </li>
            <li class="nav-item">
              <router-link to="/dashboard" class="nav-link"
                >Dashboard</router-link
              >
            </li>
            <li>
              <!-- <span @click="">Logout</span> -->
            </li>
          </ul>
        </div>
      </div>
    </nav>
    <router-view></router-view>
  </div>
</template>
  • (Line: 6-13) The menu shows when the user not authenticated. To determine this we will check the 'id' value from the user record.
  • (Line: 15-31) The menu shows after the user logged in.
src/App.vue:(Script Part)
<script>
import { mapGetters } from "vuex";
export default {
  name: "App",
  computed: {
    ...mapGetters("auth", {
      getUserProfile: "getUserProfile",
    }),
  }
};
</script>
  • Using store 'mapGetters' fetching the user profile data.
Now update the 'Dashboard.vue' component with the user name.
src/components/Dashboard.vue:
<template>
  <div>
    <h4>Welcome to your dashboard page {{getUserProfile.firstName}} {{getUserProfile.lastName}}!</h4>
  </div>
</template>
<script>
import { mapGetters } from "vuex";
export default {
  computed: {
    ...mapGetters("auth", {
      getUserProfile: "getUserProfile",
    }),
  }
};
</script>
Now we need to invoke the user profile API before entering into any page vue component after the user logged in. So this logic will be implemented in  'appRouter.js'.
src/appRouter.js:
import Login from "./components/Login.vue";
import Dashboard from "./components/Dashboard.vue";
import { createRouter, createWebHistory } from "vue-router";
import store from "./store/index";

const routes = [
  { path: "/", component: Login, meta: { requiredAuth: true } },
  { path: "/login", component: Login, meta: { requiredAuth: false } },
  { path: "/dashboard", component: Dashboard, meta: { requiredAuth: true } },
];

export const routeConfig = createRouter({
  history: createWebHistory(),
  routes: routes,
});

routeConfig.beforeEach(async (to, from, next) => {
  if (to.meta.requiredAuth) {
    var userProfile = store.getters["auth/getUserProfile"];
    if (userProfile.id === 0) {
      await store.dispatch("auth/userProfile");
      userProfile = store.getters["auth/getUserProfile"];
      if (userProfile.id === 0) {
        return next({ path: "/login" });
      } else {
        return next();
      }
    }
  }
  return next();
});
  • In vuejs routing, each route can be configured with an object like 'meta'. This 'meta' object can have any kind of props. Here I'm defining my custom property like 'requiredAuth' that is to identify whether the route requires user authentication or not.
  • The 'BeforeEach' method gets executed before entering into the vue component on every navigation. So here we will check the user information loaded or not. If no user information exists in our store, then we will invoke the user profile API.

Logout Endpoint:

At the server, logout means it clears our auth cookie. So our logout API looks as below
http://localhost:3000/logout

Implement Logout Logic Into Our Vue App:

Now let's add a new store state property regarding the logout.
src/store/module/auth.js:
const state = () => ({
  // code hidden for display purpose
  logOut:false
});
create mutation method to update the logout state.
src/store/module/auth.js:
setLogout(state, payload){
 state.logOut = payload;
}
create an action method to invoke the logout API.
src/store/modules/auth.js:
async userLogout({commit}){
 const response = await axios
  .get("http://localhost:3000/logout",{withCredentials: true, credentials: 'include'})
  .catch((err) => {
	console.log(err);
  });

  if(response && response.data){
	commit("setLogout", true)
  }
  else{
	commit("setLogout", false)
  }
}
create a getter method to fetch the 'logOut' state property.
src/store/modules/auth.js:
getLogout(state){
    return state.logOut;
}
In 'App.vue' component add the new menu item for logout next to the 'Dashboard' menu item.
src/App.vue:(Html Part)
<!-- code hidden for display purpose -->
<li>
 <span @click="logout()">Logout</span>
</li>
src/App.vue:(Script Part)
<script>
import { mapGetters, mapActions, mapMutations } from "vuex";
export default {
  name: "App",
  computed: {
    ...mapGetters("auth", {
      getUserProfile: "getUserProfile",
      getLogout: "getLogout",
    }),
  },
  methods: {
    ...mapActions("auth", {
      userLogout: "userLogout",
    }),
    ...mapMutations("auth", {
      setLogout: "setLogout",
      setUserProfile: "setUserProfile",
    }),
    async logout() {
      await this.userLogout();
      if (this.getLogout) {
        const resetUser = {
          id: 0,
          lastName: "",
          firstName: "",
          email: "",
          phone: "",
        };
        this.setUserProfile(resetUser);
        this.setLogout(false);
        this.$router.push("/login");
      }
    },
  },
};
</script>
  • (Line: 8) Registered 'getLogout' getter.
  • (Line: 15-18) Registered the 'mapMutations' like 'setLogout' and 'setUserProfile'.
  • (LIne: 19-31) The 'logout' method invokes the logout endpoint and changes the state of the 'logOut' property and reset the user profile information.
So that all about the user login and logout using the HttpOnly JWT cookie. In the second article, we will implement more about routing guards and refresh tokens(refresh tokens also stored in cookies).

Video Session:

 

Support Me!
Buy Me A Coffee PayPal Me

Wrapping Up:

Hopefully, I think this article delivered some useful information on user authentication with HttpOnly Jwt Cookie. I love to have your feedback, suggestions, and better techniques in the comment section below.

Refer:

Follow Me:

Comments

Popular posts from this blog

Blazor WebAssembly Custom Authentication From Scratch

In this article, we are going to explore and implement custom authentication from the scratch. In this sample, we will use JWT authentication for user authentication. Main Building Blocks Of Blazor WebAssembly Authentication: The core concepts of blazor webassembly authentication are: AuthenticationStateProvider Service AuthorizeView Component Task<AuthenticationState> Cascading Property CascadingAuthenticationState Component AuthorizeRouteView Component AuthenticationStateProvider Service - this provider holds the authentication information about the login user. The 'GetAuthenticationStateAsync()' method in the Authentication state provider returns user AuthenticationState. The 'NotifyAuthenticationStateChaged()' to notify the latest user information within the components which using this AuthenticationStateProvider. AuthorizeView Component - displays different content depending on the user authorization state. This component uses the AuthenticationStateProvider

How Response Caching Works In Asp.Net Core

What Is Response Caching?: Response Caching means storing of response output and using stored response until it's under it's the expiration time. Response Caching approach cuts down some requests to the server and also reduces some workload on the server. Response Caching Headers: Response Caching carried out by the few Http based headers information between client and server. Main Response Caching Headers are like below Cache-Control Pragma Vary Cache-Control Header: Cache-Control header is the main header type for the response caching. Cache-Control will be decorated with the following directives. public - this directive indicates any cache may store the response. private - this directive allows to store response with respect to a single user and can't be stored with shared cache stores. max-age - this directive represents a time to hold a response in the cache. no-cache - this directive represents no storing of response and always fetch the fr

Endpoint Routing In Asp.Net Core

How Routing Works In  Core 2.1 And Below Versions?: In Asp.Net Core routing is configured using app.UseRouter() or app.UseMvc() middleware. app.UseMvc(routes => { routes.MapRoute( name: "default", template: "{controller=Home}/{action=Index}/{id?}"); }); Here in Dotnet Core version 2.1 or below versions on the execution of route middleware request will be navigated appropriate controller matched to the route. An operation or functionality which is dependent on route URL or route values and that need to be implemented before the execution of route middleware can be done by accessing the route path from the current request context as below app.Use(async (context, next) => { if(context.Request.Path.Value.IndexOf("oldvehicle") != -1) { context.Response.Redirect("vehicle"); } else { await next(); } }); app.UseMvc(routes => { routes.MapRoute( name: "vehicleRoute", template: "vehicle", defaul

Asp.Net Core MVC Form Validation Techniques

Introduction: Form validations in any applications are like assures that a valid data is storing on servers. All programing frameworks have their own individual implementations for form validations. In Dotnet Core MVC application server-side validations carried on by the models with the help of Data Annotations and the client-side validations carried by the plugin jQuery Unobtrusive Validation. jQuery Unobtrusive Validation is a custom library developed by Microsoft based on the popular library  jQuery Validate . In this article, we are going to learn how the model validation and client-side validation works in Asp.Net Core MVC Application with sample examples. Getting Started: Let's create an Asp.Net Core MVC application project using preferred editors like Microsoft Visual Studio or Microsoft Visual Studio Code. Here I'm using Visual Studio. Let's create an MVC controller and name it as 'PersonController.cs' and add an action method as bel

.Net5 Web API Redis Cache Using StackExchange.Redis.Extensions.AspNetCore Library

In this article, we are going to explore the integration of Redis cache in .Net5 Web API application using the 'StackExchange.Redis.Exntensions' library. Note:- Microsoft has introduced an 'IDistributedCache' interface in dotnet core which supports different cache stores like In-Memory, Redis, NCache, etc. It is simple and easy to work with  'IDistributedCache', for the Redis store with limited features but if we want more features of the Redis store we can choose to use 'StackExchange.Redis.Extensions'.  Click here for Redis Cache Integration Using IDistributedCache Interface . Overview On StackExchange.Redis.Extnesions Library: The 'StackExchange.Redis.Extension' library extended from the main library 'StackExchange.Redis'. Some of the key features of this library like: Default serialization and deserialization. Easy to save and fetch complex objects. Search key. Multiple Database Access Setup Redis Docker Instance: For this sampl

.NET Core MVC Application File Upload To Physical Location With Buffered Technique

Buffering Technique In File Upload: The server will use its Memory(RAM) or Disk Storage to save the files on receiving a file upload request from the client.  Usage of Memory(RAM) or Disk depends on the number of file requests and the size of the file.  Any single buffered file exceeding 64KB is moved from Memory to a temp file on disk.  If an application receives heavy traffic of uploading files there might be a chance of out of Disk or RAM memory which leads to crash application. So this Buffer technique used for small files uploading. In the following article, we create a sample for the file uploading using .NET Core MVC application. Create The .NET Core MVC Project: Let's create a .NET Core MVC project, here for this sample I'm using Visual Studio Code as below.   Check the link to use the Visual Studio Code for .NET Core Application . IFormFile: Microsoft.AspNetCore.Http.IFormFile used for file upload with buffered technique. On uploading files f

.Net5 Web API Managing Files Using Azure Blob Storage

In this article, we are going to understand the different file operations like uploading, reading, downloading, and deleting in .Net5 Web API application using Azure Blob Storage. Azure Blob Storage: Azure blob storage is Microsoft cloud storage. Blob storage can store a massive amount of file data as unstructured data. The unstructured data means not belong to any specific type, which means text or binary data. So something like images or pdf or videos to store in the cloud, then the most recommended is to use the blob store. The key component to creating azure blob storage resource: Storage Account:- A Storage account gives a unique namespace in Azure for all the data we will save. Every object that we store in Azure Storage has an address. The address is nothing but the unique name of our Storage Account name. The combination of the account name and the Azure Storage blob endpoint forms the base address for each object in our Storage account. For example, if our Storage Account is n

Ionic Picker Sample Code In Angular

Introduction: Ionic Picker(ion-picker) is a popup slides up from the bottom of the device screen, which contains rows with selectable column separated items. The main building block of ion-picker as follows: PickerController PickerOptions PickerController: PickerController object helps in creating an ion-picker overlay. create(opts?: Opts): Promise<Overlay> PickerController create method helps in create the picker overlay with the picker options PickerOptions: PickerOptions is a configuration object used by PickerController to display ion-picker. Single Column Ionic Picker: single.item.picker.ts: import { Component } from "@angular/core"; import { PickerController } from "@ionic/angular"; import { PickerOptions } from "@ionic/core"; @Component({ selector: "single-column-picker", templateUrl:"single.item.picker.html" }) export class SingleItemPicker { animals: string[] = ["Tiger&quo

.Net Core HttpClient JSON Extension Methods Using System.Net.Http.Json Package

.Net Core 3.0 onwards Microsoft brought up a new package called System.Net.Http.Json. This new package provides JSON extension methods for HttpClient. These JSON extension methods will have a prebuild mechanism for serializing or deserializing response data or payload of HttpClient call. System.Net.Http.Json extension methods that are provided to HttpClient, few of them are mentioned below. GetFromJsonAsync PostAsJsonAsync PutAsJsonAsync ReadFromJsonAsync In this article, we understand System.Net.Http.Json package by implementing the HttpClient samples by with and without JSON extension methods and compare them. Create A .Net Core Web API Sample Application: Let's create a .Net Core sample Web API application, from this application we will consume another Web API by implementing HttpClient calls. We can create a Web API sample application using IDE like Visual Studio 2019(Supports .Net Core 3.0 plus) or  Visual Studio Code . Create A Typed Client: In .Net Core using the Http

GraphQL API Integration In Asp.Net Core Application

Introduction: GraphQL is a query language for your API and a server-side runtime for executing queries by using a type system you define for your data. GraphQL can be integrated into any framework like ASP.NET, Java, NestJs, etc and it isn't tied to any specific database or storage engine and is instead backed by your existing code and data. How GraphQL API Different From Rest API: GraphQL exposes a single end-point or route for the entire application, regardless of its responses or actions. HTTP-POST is the only Http verb recommended by the GraphQL. The client applications (consumers of API) can give instructions to GraphQL API about what type of properties to be returned in the response. Building Blocks Of GraphQL API: The main building blocks of GraphQL API is Schemas and Types.  A 'Schema' in GrpahQL API describes the functionality available to the clients connect to API. Schema mostly consists of GraphQL Object Types, Queries, Mutations, etc. T