Oracle Identity Cloud Service Hosted login UI pages can be rebranded easily by adding custom HTML, altering CSS and by choosing the right translation language.
This method is fairly straightforward and steps are available in the service documentation.
But If you need full control, that is not just over the look and feel of the login UI but also the domain where it is hosted, creating your own custom login UI on top of the IDCS authentication API is what you need. The good thing that there is already a fully functional sample with a tutorial available and many customers have simply reused that and rebranded it. The sample provides instructions showing how easy it is to customize for rebranding.
In this post, I want to go a little further and walk you through the process of hosting the custom login widget on OCI.
There are multiple ways of hosting the widget on OCI
I want to elaborate on the first method in this post as it is the best way to automate scaling and managing future deployments.
I want to divide this post into 3 parts. This post is the first one in the series and is a short read to cover the overall process at a high level.
Part 2 will cover steps to dockerize the widget and part 3 will show steps to deploy the widget on Oracle Kubernetes Engine.
The next 2 parts will cover more details and exact steps.
Part 2 - Dockerize IDCS custom login Widget – This will cover how to create a docker image of the login widget and push it to OCIR
Part 3 - Deploying IDCS Login widget on OKE – This post will show the steps to use the widget image from OCIR and steps to deploy it on an OKE cluster and testing.
In this post, we looked at a high-level process of deploying the IDCS custom login widget on Oracle Kubernetes Engine. In the next parts of this post, I want to double click on each of the steps and provide more details to make it easy for the readers to try this on their own.