Skip to main content

OAuth 2.0 vs JWT

JWT replaces the cookie and makes APIs / Web stateless

JWT Token can easily be decoded

JWT has No true logout

Always use: Authorization: Bearer <TOKEN>

Bearer authentication scheme prevents CSRF attacks

sample JWT token includes the following elements.

Header : Algorithm and token type

{
 “alg”: “HS256”,
 “typ”: “JWT”
}

Payload : data

{
  “sub”: “1234567890”,
 “name”: “John Doe”,
 “admin”: true
}

Verify signature:

HMACSHA256(
  base64UrlEncode(header) + "." +
  base64UrlEncode(payload),
  secret  
)

Final output:

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9
     .     eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWV9
     .
TJVA95OrM7E2cBab30RMHrHDcEfxjoYZgeFONFh7HgQ

Using JWT.IO we can easily decode, verify and generate JWT tokens.

OAuth 2.0:

Authorization Framework:

Support APIs, Web, etc.

OAuth 2.0 Key Components

  1. Authorization Server (Token Factory, e.g. GitHub)
  2. Resource Server (API / Microservice, e.g. GitHub API)
  3. Client  (UI / Mobile / API / Microservice e.g. Login with GitHub )
  4. User (Resource Owner)
  5. User Agent (Device/Browser)
OAuth 2.0 Grant Types
  1. Authorization Code 
    1. Used for User Authorization by Web / Mobile
    2. (e.g. Login with Github UI button -> GitHub for Authorization -> Token to access GitHub APIs on behalf of the user)
    3. Requires Web/Mobile client to register with GitHub and have a client-secret to make token validation, refresh calls
    4. The browser only sees a temp code. The client takes the temp code along with client-secret to get access-token
    5. The client should register the Authorization Server have the client-id/client-secret with it
  2. Client Credentials
    1. Machine-Machine communication
    2.  (Go to GitHub and generate Client ID/Client Secret to access GitHub APIs)
PKCE for single page Apps
https://www.oauth.com/oauth2-servers/single-page-apps/

https://www.oauth.com/


SAML
Single Sign-on Across Sites

2008 had only SAML & Login Forms / cookies
** No way to support Mobile Apps Login
** No way to support Delegated Authorization

OpenID Connect is for Authentication
OAuth 2.0 is for Authorization

What does OpenID Connect add?
  1. ID Token
  2. UserInfo endpoint for getting more user info
  3. A standard set of scopes
  4. Standardized implementation
When to Use OpenID Connect?
  • Form login
  • Single sign-on across sites
  • Mobile App login
  • Delegated authorization (OAuth 2.0)

When using OpenID Connect

Login with Google will go with an extra scope: openid
and will return with extra /userinfo endpoint and openid token for requesting more user profile info






Comments

Post a Comment

Popular posts from this blog

JPA 2 new feature @ElementCollection explained

@ElementCollection is new annotation introduced in JPA 2.0, This will help us get rid of One-Many and Many-One shitty syntax. Example 1: Stores list of Strings in an Entity @Entity public class Users implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @ElementCollection     private List<String> certifications = new ArrayList <String> ();     public Long getId() {         return id;     }     public void setId(Long id) {         this.id = id;     }     public List <String> getCertifications() {         return certifications;     }     public void setCertifications(List <String> certifications) {         this.certifications = certifications;     } .. }         Users u = new Users();         u.getCertifications().add("Sun Certified Java Programmer");         em.persist(u); Generated Tables    Users    Co
21 comments
Read more

Reuse JPA Entities as DTO

Note : Major design advantages of JPA Entities are they can detached and used across tiers and networks and later can by merged. Checkout this new way of querying entities in JPA 2.0 String ql = " SELECT new prepclass2.Employee (e.firstname, e.lastname) FROM Employee e "; List<Employee> dtos = em.createQuery(ql).getResultList(); The above query loads all Employee entities but with subset of data i.e. firstname, lastname. Employee entity looks like this. @Entity @Table(name="emp") public class Employee implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @Column     private String firstname;     @Column     private String lastname;     @Column     private String username;     @Column     private String street;     @Column     private String city;     @Column     private String state;     @Column     private String zipc
11 comments
Read more

Validating CSV Files

What is CsvValidator ?   A Java framework which validates any CSV files something similar to XML validation using XSD. Why should I use this ?   You don't have to use this and in fact its easy to write something your own and also checkout its source code for reference. Why did I write this ?   Some of our projects integrate with third party application which exchanges information in CSV files so I thought of writing a generic validator which can be hooked in multiple projects or can be used by QA for integration testing. What is the license clause ?   GNU GPL v2 Are there any JUnit test cases for me checkout ?  Yes,  source How to integrate in my existing project ? Just add the Jar which can be downloaded from here  CsvValidator.jar  and you are good. Instantiate  CsvValidator c onstructor which takes these 3 arguements          // filename is the the file to be validated and here is a  sample         // list - defines all the fields in the above csv file ( a
7 comments
Read more