Forum Discussion
Brandon
Cirrostratus
CirrostratusAPM add 2 different types of RSA on the same policy
I would like to have one Policy but give our customer a choice on what type of RSA authentication they use.
Both are RSA one is Radius and one is Okta. I want only one login page .
I created a login page and tried to use the button or drop down list. I would like for the cutsomer to be able to choose on the drop down box and then enter there password .
Hi Brandon,
You have to configure some things for your requirement:
1. When you define the button to select the type of authentication that you want to use, you have to define the name for this variable, in my case I used login:
2. In the same page go to Branch Rules
3. give click in Add Branch Rule.
4.Set a name to the new rule and click in Change.
5.In the tab Advanced copy the nest expression
expr {[mcget {session.logon.last.login}] == "okta"}
Repeat the steps 3 to 5 to add another branch rule for
expr {[mcget {session.logon.last.login}] == "radius"}
6.click Save.
7. Now you can configure all the elements to allow authentication with radius and okta in differents flows, in my case for the lab I used AD and local DB.
Hope it´s works.
If Okta path
If okta path
Radius Path
This is one Auth password field but gives customer a choice of what on
Field 3 “Radio” values added to tbe Branch Rules this is the or statement is done on the Branch Rule
Branch Rules on the “Selection for Authorization” Expression are the values from Row 3
You will notice that the variable is .pw for both okta and rsa auth are the same. The radio is what chooses the path.
Okta Path
Line item is .pw
Important line item is .ad
Radius path
important item .pw
Important item is .ad
End Result
Hi Brandon,
You have to configure some things for your requirement:
1. When you define the button to select the type of authentication that you want to use, you have to define the name for this variable, in my case I used login:
2. In the same page go to Branch Rules
3. give click in Add Branch Rule.
4.Set a name to the new rule and click in Change.
5.In the tab Advanced copy the nest expression
expr {[mcget {session.logon.last.login}] == "okta"}
Repeat the steps 3 to 5 to add another branch rule for
expr {[mcget {session.logon.last.login}] == "radius"}
6.click Save.
7. Now you can configure all the elements to allow authentication with radius and okta in differents flows, in my case for the lab I used AD and local DB.
Hope it´s works.
BrandonFYI just posting info to help someone else out.
Thank you so much. We tested two versions. One with two auth fields and one with one auth field. Given the cutsomer the choice to choose which type of auth to use by the drown box or button.
Policy 1 with two fields
- Brandon
If Okta path
If okta path
Radius Path
- Brandon
This is one Auth password field but gives customer a choice of what on
Field 3 “Radio” values added to tbe Branch Rules this is the or statement is done on the Branch Rule
Branch Rules on the “Selection for Authorization” Expression are the values from Row 3
You will notice that the variable is .pw for both okta and rsa auth are the same. The radio is what chooses the path.
Okta Path
Line item is .pw
Important line item is .ad
Radius path
important item .pw
Important item is .ad
End Result
