Using OAuth 2.0 and OpenID Connect with Caché
Contents
[Home]  [Next]
InterSystems: The power behind what matters   
Class Reference   
Search:    

Preface : 
 
 
Chapter 1: 
 
1.1 Basics
1.2 Roles
1.3 Access Tokens
       1.3.1 Forms of Access Tokens
       1.3.2 Claims
       1.3.3 JWTs and JWKSs
1.4 Grant Types and Flows
1.5 Scopes
1.6 Endpoints in an Authorization Server
1.7 See Also
Chapter 2: 
 
2.1 Supported Scenarios
2.2 Caché Support for OAuth 2.0 and OpenID Connect
2.3 Standards Supported in Caché
Chapter 3: 
 
3.1 Prerequisites for the Caché Client
3.2 Configuration Requirements
3.3 Outline of Code Requirements
3.4 Obtaining Tokens
       3.4.1 Method Details
3.5 Examining the Token(s)
3.6 Adding an Access Token to an HTTP Request
3.7 Optionally Defining Delegated Authentication for the Web Client
3.8 Variations
3.9 Revoking Access Tokens
3.10 Rotating Keys Used for JWTs
3.11 Getting a New Public JWKS from the Authorization Server
Chapter 4: 
 
4.1 Prerequisites for the Caché Resource Server
4.2 Configuration Requirements
4.3 Code Requirements
4.4 Variations
Chapter 5: 
 
5.1 Configuration Requirements for the Caché Authorization Server
5.2 Code Customization Options and Overall Flow
5.3 Implementing the Custom Methods for the Caché Authorization Server
5.4 Details for the %OAuth2.Server.Properties Object
5.5 Locations of the Authorization Server Endpoints
5.6 Creating Client Definitions on a Caché OAuth 2.0 Authorization Server
5.7 Rotating Keys Used for JWTs
5.8 Getting a New Public JWKS from a Client
 
Appendix A: 
 
A.1 Creating the Client Configuration Items Programmatically
A.2 Creating the Server Configuration Items Programmatically
Appendix B: 
 
Appendix C: 
 
C.1 Using Certificates for an OAuth 2.0 Client
C.2 Using Certificates for an OAuth 2.0 Resource Server
C.3 Using Certificates for an OAuth 2.0 Authorization Server