WSO2 Identity Server as a Service

Implementation Overview

WSO2 Identity Server (IS) 5.0.0 is provided as a service on WSO2 Private PaaS 4.1.0. This is implemented by creating the following:

Template module

The template module configures the product in runtime, with a set of key value pairs known as the configuration parameters.
Cartridge agent plugin

The cartridge agent plugin, sets the runtime configuration parameters such as hostnames, IP addresses of dependent clusters, dynamic proxy ports and many more.
Docker image
The Docker image is built by packaging the following components:
- Cartridge agent
- Product distribution
- Template module
- Configurator
- Java runtime
Puppet module

The puppet module includes the same set of component as in the Docker image. In the puppet image the template module is used to configure automation.

Deploying WSO2 IS as a Service

Deploy WSO2 IS as a service using one of the following methods.

Make sure that you note the points given below when running WSO2 Identity Server as a Key Manager:

Use the pre packaged Identity Server pack that is specifically designed to run as the Key Manager. Do not use the default IS pack.
- Download the pre packaged WSO2 Identity Server.
- For more informations, see how to configuring the pre-packaged Identity Server.
Rename the patch0012 kernal patch to patch9999 if you are applying the WSO2 Identity Server Service Pack for 5.0.0. This is done to support Private PaaS membership schema which comes from then kernal patch 12.

Deployment Architecture

The diagram illustrates the deployment architecture of WSO2 IS on Private PaaS. In the deployment, a Private PaaS cluster will be created for the IS manager.