This is the follow up article of “First Steps to deploy WSO2 API Manager in Kubernetes”
In this article I am going to describe the Kubernetes artifacts which we used to deploy in the previous article and it can be found in the following git reprository.
At this point I have already explained some of the related artifacts in “Persisting Custom Implementations on WSO2 Products in Kubernetes Deployments”
Here I have described what are the config maps and volume mounts in order to persist data in Kubernetes. …
In this story, Um going to discuss on the usage of the custom implementations like jar files, patches and any other format of a file and how to persist them.
There can be multiple occations where it is necessary to add sum custom files to the WSO2 APIM distribution. For an example let’s say there is a pre QA patch given in order to confirm the suggested fix.
As you may already know that the files that we are adding/copying to containers will not be persisted and will be lost when the container/pod rollout. Most of the time WSO2 APIM server restart is necessary in order to reflect the changes. …
In this article I am going to explain how we can deploy WSO2 API Manager in Kubernetes with the basic configurations.
Kubernetes (K8s) is an open-source system for automating deployment, scaling, and management of containerized applications.
Note: It is not necessary to have any prior knowledge in Kubernetes in order to create this deployment if you can follow the below steps.
First we need an Kubernetes cluster in order to create the deployment. So I am going to use the Google Cloud Kubernetes engine with a free trial account.
Open a web browser and navigate to the following link create a free trial Google cloud account with your gmail. …
A public key certificate (digital certificate or identity certificate) is an electronic document used to prove the ownership of a public key in cryptography. The certificate includes information about the key, information about the identity of its owner (called the subject), and the digital signature of an entity that has verified the certificate’s contents (called the issuer). If the signature is valid, and the software examining the certificate trusts the issuer, then it can use that key to communicate securely with the certificate’s subject. …
In this article The fundamentals of the JWT and symmetric and asymmetric encryption levels of a JWT are discussed.
What is JWT?
A json web token is an important way of ensuring trust and security in a application during the communication calls. JWT allow claims, such as user data, to be represented in a secure manner.A Json web token is just a json object that is defined as safe way to represent information between two parties. This defined json object has a 3 components as header, payload, signature.
So when we are creating JWT, we have to create those 3 components seperately as signature of the JWT is depending on the header and the payload. So in order to create the signature first we have to create the header and the payload. …