OAuth (New - 2.1) Authorization server

This repository full documentation can be found at m-thirumal.github.io/oauth-authorization-server/

Pre-requists

Run Eureka Server

What is Authentication and Authorization?

Authentication - "Who you are?", is the process of ascertaining that somebody really is who they claim to be.

Authorization refers to rules that determine who is allowed to do what. E.g. Thirumal may be authorized to create and delete databases, while Jesicca is only authorized to read.

There are many ways of authentication, few of which are worth discussing here:

1. Knowledge-based authentication: The username password combination is a type of knowledge-based authentication. The idea is to verify the user based on the knowledge of the user for example answer to security questions, passwords, something which only the user should know.

2. Possession based authentication: This type of authentication is based on verifying something which a user possesses. For example, when an application sends you One Time Passwords (OTPs) or a text message.

Modern authentication practices use a combination of both types, also known as Multi-Factor authentication.

OAuth2 grant types

OAuth2 supports several grant types for different use cases. The most common grant types are:

Grant Type	Usage
Authorization Code	Used for web applications that run on a server and need to access resources on behalf of a user.
Implicit	Used for single-page applications that run in a web browser and need access to resources without the need for a server.
Resource Owner Password Credentials	Used for trusted applications that require direct access to a user’s resources.
Client Credentials	Used for applications that need to access their own resources.

Features:

Configuration Parameter	EndPoints
issuer (Base URL)	http://localhost:9000
authorization_endpoint	http://localhost:9000/oauth2/authorize
Access Token	http://localhost:9000/oauth2/token
Refresh Token	http://localhost:9000/oauth2/token
Revoke Token	http://localhost:9000/oauth2/revoke
jwks_uri	http://localhost:9000/oauth2/jwks
userinfo_endpoint	http://localhost:9000/userinfo
Introspect Token	http://localhost:9000/oauth2/introspect
EndPoints	http://localhost:9000/.well-known/openid-configuration
Customize Token Content	-
DDL SQL for PostgreSQL	DDL for PostgreSQL
Data Dictionary of Model	DB

Prerequisites:

1. Eureka (Optional)
2. PostgreSQL

Set UP

Documentation to set up can be found here

• Definition

sequenceDiagram
  actor O AS  Resource Owner
  participant C AS Client
  participant A AS Authorization Server
  participant R AS Resource Server
  autonumber
  O->>C: Login URL
  C->>A: http://localhost:9000/auth?client_id=resource-server-1&response_type=code&scope=openid profile&redirect_url=http://localhost:9001/login-callback&state=sEdgkiEkpvnsj
  Note right of A: code_challenge & method query param is required for PKCE
  A->>O: Present user with Login page
  O->>A: User logs in
  A->>O: Present Consent page
  O->>A: User authorize client to access the resource server
  A->>C: Authorization Code (Redirect to http://localhost:9001/callback?code=12ddassa-jk12nm32...)
  C->>A: Exchange authorization code for an Access Token (http post/token + code + clientId + Client Secret)
  C->>R: Request data with (Bearer `token`)
  A->>R: Validate Token
  R->>C: Resource

Loading

Database model

FAQ

1. Where do I find all end points. Invoke http://localhost:9000/.well-known/openid-configuration

{
    "issuer": "http://localhost:9000",
    "authorization_endpoint": "http://localhost:9000/oauth2/authorize",
    "token_endpoint": "http://localhost:9000/oauth2/token",
    "token_endpoint_auth_methods_supported": [
        "client_secret_basic",
        "client_secret_post",
        "client_secret_jwt",
        "private_key_jwt"
    ],
    "jwks_uri": "http://localhost:9000/oauth2/jwks",
    "userinfo_endpoint": "http://localhost:9000/userinfo",
    "response_types_supported": [
        "code"
    ],
    "grant_types_supported": [
        "authorization_code",
        "client_credentials",
        "refresh_token"
    ],
    "revocation_endpoint": "http://localhost:9000/oauth2/revoke",
    "revocation_endpoint_auth_methods_supported": [
        "client_secret_basic",
        "client_secret_post",
        "client_secret_jwt",
        "private_key_jwt"
    ],
    "introspection_endpoint": "http://localhost:9000/oauth2/introspect",
    "introspection_endpoint_auth_methods_supported": [
        "client_secret_basic",
        "client_secret_post",
        "client_secret_jwt",
        "private_key_jwt"
    ],
    "subject_types_supported": [
        "public"
    ],
    "id_token_signing_alg_values_supported": [
        "RS256"
    ],
    "scopes_supported": [
        "openid"
    ]
}

Login

Recovery Code

Multi factor authentication

• Authentication App

• Text message (SMS)

• Security Key

• Recovery Code When the use lost the phone / authenticator app mobile