c11lv (c11lv) asked a question.
According to the following article: https://support.okta.com/help/s/article/What-is-the-Undefined-Value-in-an-Okta-attribute?language=en_US you can actually have three values for a boolean: true, false, and undefined
This is great, and I use this for controlling specific aspects of my user experience, however, I can't seem to figure out how to create a routing rule that can work with undefined when it's in a user attribute.
Basically, I need a routing rule that checks if the value is "not true", and there isn't an option for "not equals" in the matches section (the only options are Starts With, Equals, Contains, Matches Regex) , so I am attempting a regex pattern, something like (false|undefined) so I can route people to a specific IDP when they are not true. Maybe I am making it more complex than needed, so please guide me if there is already a proper solution for this. False works well, but someone with undefined skips this check and continues down my default rules.
Any help is greatly appreciated!
Hello, William
This is a normal behavior, so you can create 2 rules.
One for false and the other for undefined, and select the action you would like them to accomplish.
As well, you can add an idea to the OktaIdeas portal asking for the "not equal" option to be added.
Vicente-Okta
But what permutation? Doing "Equals" undefined does not work either in a rule, hence why I switched to using Regex. Are you suggesting using the "Matches Regex" two times, one per rule and putting false in one, then undefined in another?
I can do both now, and respond with results because I think I've already attempted this and failed. Let me try again.
I attempted the following permutations with no success:
Hello, @c11lv (c11lv)
Just confirmed that undefined will not work for a routing rule.
You can use only tru or false, in this case you might need to add a diferent atribute so you can get the rule working.
As well you can request an enhacement on our OktaIdeas portal.
Vicente
Okta, Inc