Mehul Patel
Hi, I'm Mehul Patel and I specialize in Information Technology and Services. I’m passionate about what I do. I am a Developer Tech by profession, an open source enthusiast, Linux geeky and a maker by heart. https://about.me/rowdymehul
Mehul Patel,@rowdymehul
Source: giphy.com
credits: DZone
credits: DZone
Focus on code, not servers
credits: auth0
Image credits: keycdn.com
Image source: Google
Image source: softwareengineeringdaily.com
All you need is code!
Run code with an HTTP call.
No provisioning. No deployment.
credits: auth0
Further, let's explain some concepts.
1. Information Exchange
2. Authorization
Below is an encoded JSON Web Token:
// Token structure
header.payload.signature
// A real world token
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWV9.TJVA95OrM7E2cBab30RMHrHDcEfxjoYZgeFONFh7HgQ
Image Source: StackOverflow
Image source: medium.com
Let's take one Example...
Image source: auth0/docs
An open standard for access delegation, commonly used as a way for Internet users to grant websites or applications access to their information on other websites but without giving them the passwords.
Resource Owner: the entity that can grant access to a protected resource. Typically this is the end-user.
Resource Server: the server hosting the protected resources. This is the API you want to access.
Client: the app requesting access to a protected resource on behalf of the Resource Owner.
Source: giphy.com
By Mehul Patel
Hi, I'm Mehul Patel and I specialize in Information Technology and Services. I’m passionate about what I do. I am a Developer Tech by profession, an open source enthusiast, Linux geeky and a maker by heart. https://about.me/rowdymehul