Last changed
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
Request trialWSO2 Identity Server is a powerful, modern identity and access management solution for your on-premises or cloud environment
Chainguard Containers are regularly-updated, secure-by-default container images.
For those with access, this container image is available on cgr.dev
:
Be sure to replace the ORGANIZATION
placeholder with the name used for your organization's private repository within the Chainguard Registry.
This image is comparable to the wso2is/wso2is image available from Docker Hub. Switching to the Chainguard image should not require any changes to your existing setup.
There are several ways to deploy the WSO2 Identity Server (IS) but in this example we will be using the official WSO2 IS Helm chart to deploy it on Kubernetes. The Helm chart is available in the wso2is Helm repository.
To get started, create the values.yaml
file with the following content:
Then, install the WSO2 IS Helm chart using the following command:
This will deploy the WSO2 Identity Server with the Chainguard container image. Access will depend on how ingress is configured in your cluster. Here's a quick example to validate the service's web UI via port forwarding:
You can then access the WSO2 IS dashboard at https://localhost:9443
.
You can learn more about the API management capabilities of WSO2 IS in the WSO2 IS documentation.
Chainguard Containers are minimal container images that are secure by default.
In many cases, the Chainguard Containers tagged as :latest
contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a more secure software supply chain.
The main features of Chainguard Containers include:
For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a -dev
variant.
Although the -dev
container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev
variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.
To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.
In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.
This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.
Chainguard container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:
Apache-2.0
BSD-3-Clause
Bitstream-Vera
CC-PDDC
FTL
GCC-exception-3.1
GPL-2.0-only
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreement