Thursday, 27 May 2021

OAAM 11gR2PS3 Post Authentication Checkpoint

Post Authn Checkpoint

Post authn checkpoint is a really important step in checkpoints flow. How this need to be configured & what could be the different outcomes of this checkpoint are explained in below video.




Hope this helps :-)

Enjoy :-)

OAAM 11gR2PS3 Checkpoints - Basic Understanding

OAAM Checkpoints Part-1

With help of checkpoints, one enforces policies that are to be executed on each check made by a checkpoint in OAAM.

They are fix in number but what you can do & enforce is completely configurable as part of OAAM Admin.

Kindly watch the below video for better understanding of OAAM checkpoints & this topic is divided into 3 parts that are;


Hope this helps :-)

Enjoy :-)

OAAM 11gR2PS3 Checkpoints - How are they executed

How Checkpoints are executed in OAAM

Checkpoints in OAAM are like barriers that one need to cross to move ahead, and once you are been verified fully only than you are allowed to pass.

Basically in OAAM we have different kind of checkpoints available that helps the system to know about the user in a better way.

I have explained the entire flow of these checkpoints in below video, kindly watch & share your comments.



Hope this helps :-)

Enjoy :-)

OAAM 11gR2PS3 Conditions Types

OAAM Conditions Types

With each condition defined in OAAM, there is a type associated with it. These types define the behavior of a condition. And based on this we ca actually use a condition with a rule.

Condition Types are explained in below video, kindly watch & please share your comments.



Hope this helps :-)

Enjoy :-)

OAAM 11gR2PS3 Conditions & Conditions Types

OAAM Conditions

OAAM provides pre-packaged conditions that are to be used while defining rules. It's the very important part of any policy i.e. defined in OAAM.

Conditions can't be created by an admin, they are fixed & can only be modified only in terms of the output we want from that condition.

I have explained what conditions are in below shared video, watch & please share your comments.



Hope this helps :-)

Enjoy :-)


Saturday, 19 January 2019

Understanding Blue Green Deployment

What this blue-green all about?

This is a way of switching traffic from one deployment to another one. That means say you have a new version of software to roll out, which has been successfully tested in staging environment. Now you want that to go-live, so here in kubernetes you have this magic word blue-green deployment.

Definition: "A blue green deployment uses the service label selector to switch all traffic from one deployment to another."

If above stated definition is cryptic, than lets see an image view to understand it;



Here if you notice, we have app:hello version:1.0.0 is currently deployed. Now let's say we have a new version i.e. 2.0.0 of hello app;


First test you new deployment, i.e. version 2.0.0. Once you have verified it, it's time to switch live traffic to version 2.0.0 deployment.

Now let's get back to the definition, we discussed previously. It says use service label selector to switch traffic. Awesome we are on track understanding traffic switch.


Here we have successfully switched to new version 2.0.0 with help of "selectors & labels". That means if we want to get all this done, the mantra is to understand "labels & selectors".

Got it, now you must be asking where the heck is this labels & selectors discussion. Need not to worry we will soon see a video tutorial because that needs much attention.

Very well, we have made a basic understanding of blue-green deployment.

Enjoy :-)

Setting up NGINX Plus openid connect with IDCS on Google Cloud





This tutorial describes the nginx plus openid connect feature working with IDCS (also known as OICS) on google cloud platform.

It features the following:
a) Creating NGINX Plus VM Instance on google cloud.
b) Setting up nginx plus openid connect environment.
c) Configuring a client on IDCS.
d) Executing nginx plus configure script.
e) Execute 3 legged flow & Identify the bug with NGINX Plus.
f) Workaround for the identified bug.
g) Working Demo


Issues identified link updated:

  • https://github.com/nginxinc/nginx-openid-connect/issues 

Enjoy :-)