Securing JAX-RS

1) Introduction
|-Types of Security Levels/mechanisms
|-1) Authentication
|-2) Authorization
|-3) Data protection (Encryption)
|-4) Integrity (Digital Signature)
|-5) Transport Level Security (TLS)

|-Authentication
|-1) HTTP Basic Authentication
|-Working Mechanism
|-Problem with this Approach and Solution
|-Configuration
|-2) Form Based Authentication
|-Working Mechanism
|-Advantage
|-Limitations and Disadvantages:
|-Configuration
|-Enforcing SSL
|-3) HTTP Digest Authentication
|-Working Mechanism
|-Advantage
|-Disadvantage
|-Configuration
|-4) HTTPS Client Authentication
|-Working Mechanism
|-SSL and TLS authentication
|-X.509 client-certificates
|-Advantage
|-Disadvantage
2) Working Authentication, Authorization & Encryption in JAX-RS
|-Ways of Securing our JAX-RS
|-1. Configuration Approach
|-Configuring the Realms and Roles
|-Guidence to configure Security
|-2. Programatic Approach
|-Use case: Banking Application:
|-3. Annotation Driven Approach
|-Advantages to using annotations over config based Security
|-Disadvantages of annotations over config based Security

3. Client Security
4. OAuth 2.0

Wrapping Up