Using OAuth 2.0 and OpenID Connect with Caché
How Caché Supports OAuth 2.0 and OpenID Connect
This chapter introduces Caché support for OAuth 2.0 and OpenID Connect.
With Caché support for OAuth 2.0 and OpenID connect, you can do any or all of the following:
Use a Caché web application as a client
Use a Caché web application as a resource server
Use a Caché instance as an authorization server
For example, you can use a Caché web application as a client of an authorization server that uses third-party technology. Or you can use third-party clients with an authorization server that is built on Caché. The resource server or resource servers could be implemented in Caché or in a different technology.
In all cases, the authorization server is the most complex element and is generally created first. You create clients later. When you create a client, it is generally necessary to understand the capabilities and requirements of the authorization server, such as the scopes it supports.
The Caché support for OAuth 2.0 and OpenID Connect consists of the following elements:
Configuration pages in the Management Portal.
Classes in the %SYS.OAuth2
package. These classes are the client API. If you define a Caché web application as an OAuth 2.0 client, your client uses methods in these classes.
Classes in the %OAuth2
package. If you use a Caché instance as an OAuth 2.0 authorization server, you customize the server by subclassing one or more of the classes in the package %OAuth2.Server
. Other classes in %OAuth2
provide utility methods for your code to call.
Classes in the OAuth2
package (in the CACHESYS
database). These include persistent classes for internal use by Caché, and you can ignore most of them. However, if you want to create configuration items programmatically, you would use a subset of the classes in this package.
The following subsections provide an overview of the configuration items.
Within a Caché instance that is acting as an OAuth 2.0 client, it is necessary to define two connected configuration items for a given client application: a server description
(which describes the authorization server) and a client configuration
(which configures the client). A given Caché instance can have any number of server descriptions. Each server description has multiple client configurations, as shown in the following figure, which also indicates some of the information stored in these configuration items:
This architecture intended to simplify configuration, because it enables you to define multiple client configurations that use the same authorization server without needing to repeat the details of the authorization server.
Within a Caché instance that is acting as an OAuth 2.0 authorization server, it is necessary to define a server configuration
(which configures the authorization server) and a number of client descriptions
. The following figure indicates some of the information stored in these configuration items.
A given Caché instance can have at most one server configuration and can have many client descriptions. One client description is necessary for each client application. A client description is also necessary for each resource server that uses any endpoints of the authorization server. If a resource server does not use any endpoints of the authorization server, there is no need to create a client description for it.
This section lists the standards that Caché supports for OAuth 2.0 and Open ID Connect: