Hasura Auth API + Postman collection

By



In my previous post, I had mentioned that Hasura platform provides Data API as well as Auth API. I used Data API to insert and retrieve data into tables of my database schema. Check out my previous post about Hasura Data API


Auth service

Hasura Auth provides services for user authentication & authorization, user management, session management and table permissions. In a typical app, we require to
  1. Register a new user.
  2. Login an existing user and maintain his/her session.
  3. Logout the user and terminate his/her session.
  4. Reset password for a user.
Table for user information is already there in Auth service.

Roles

There are three roles in the auth service
  • admin
  • user
  • anonymous
A user of user table can have more then one role, and each role have its permission and access restrictions. The admin role can do CRUD queries to all the tables. Permissions for other roles is need to be defined in each table.
When we register a new user, it assigned least user role. If no one is logged in, that is given to role anonymous.
A logged in user is identified using the session tokens assigned to them.

API Request using Postman

As I told in my previous post about Hasura Data API where I was using Postman to query data from data service. Same in here I am using to contact Auth API on different endpoints for different purposes.
Auth API URL : http://auth.c100.hasura.me/
All request made to the Auth service must be POST, and data need to be send in application/json format.

User signup

For signup request, append signup in auth url. Body of request must be in raw and JSON format. Data need to be with the request is a username and a password (must be 8 characters). Put these information in the request body and send the request to Data API.

Signup request

If the Data service is running appropriately and the data sent with request then we get the response from Auth API, which is the information of newly signed up user.


A new user is added in Auth user table and it is assigned an id also a role user. This newly registered user is logged in and assigned a session token, which is in the response named as auth_token .

User Login

Login request made on the endpoint auth_url/login. Data need to be send on login is same as of signup, but a little change in the response recieved which is the string hasura_roles is not present in that.

User Logout

For logging out a user we need to request on the endpoint auth_url/user/logout. In this request we do not need to send any data. Response for logout is as


And the user is logged out of Auth service.

What's Next?

Next post is about integrating my app’s first screen’s UI with backend.

Comments

Post a Comment

Popular posts from this blog

User Feedback & Testing of White Board

By
Image
As in my previous posts, I’ve described about all screens of my app  White Board.  You can check here — App Screen 1 (UI + Backend Integration) If you are familiar with my previous post and app idea then you know what I did before, otherwise just check my app… medium.com App Screen 2 (UI + Backend Integration) Task 5.1 Hasura Internship. Week 5 task medium.com App Screen 3 (UI + Backend Integration) Task 6.1 Hasura Internship Week 6 Task medium.com This one is for user feedback about my app and testing of the app for any bug. When I completed my app with required functionality as I described in MVP in my first blog post at the beginning of my journey. Idea for an APP | First step to internship This article is about my brainstorming for an idea which can be used an MVP. medium.com Testing and fixing bugs is one of the important part in order to build a successful application. Anyhow a person can’t do this all alone, so it is a better way to get feedback from others as w
Read more

Idea for an app | First step to internship

By
Image
It all started when I joined IMAD (Introduction to Modern Application Developement), an MOOC provided by NPTEL in association with Hasura. I completed the assignments and appeared in the final test, scoring an overall of 84%, which, much to my delight, landed me an internship with Hasura. First week task The task in the first week was to come up with an idea for an app that can be demonstrated and used as a Minimum Viable Product (MVP) with just 3 screens. I discussed this task with a few of my friends and researched the internet for viable ideas. After long sessions of discussion and surfing the internet, I finally settled on the idea for an app for a  Collaborative   White Board . The idea   The idea of the app is pretty simple, to create an online platform for collaborative brainstorming by a group/team of people from across the globe. This sort of brainstorming is usually required for startup ideas, projects or the onset of any form of development in a group.
Read more

Playing with the Octo-Cat

By
Image
After I done with setting-up dev environment, next task of Hasura Internship was to learn git basics. https://octodex.github.com/images/dojocat.jpg Git is not a programming language or an IDE About Git Git is the most commonly used  distributed version control system . Git is a mature, actively maintained open source project originally developed in 2005 by Linus Torvalds, the famous creator of the Linux operating system kernel.  GitHub  is a company that provides a platform to do version controlling Git allows a team of people to work together, all using the same files. And it helps the team cope with the confusion that tends to happen when multiple people are editing the same files. Version control in simple terms is nothing but making flags/check points as significant changes are made to your code/work so that you can always go back to whichever version was last working properly or whichever version you want to use at the moment. Why Git and Github? Version contr
Read more