Forum Discussion
Advanced AD Query
John - If I understand correctly you looking to use the advanced tab of branch rule to determine how to route a user. This is an example of a check for the existence of a value from a LDAP query. You would need to use a AD session variable instead of the ldap session variable but the basic structure of the check to see if a value exists is like this:
expr { [mcget {session.ldap.last.attr.unixHomeDirectory}] != "" }
I've never tried or thought of using the check on a branch rule of the query item itself, but I would think it would work (and I might start using it if it does). I tend to do the branch selection with an item following the query itself mostly to keep operations broken out so I remember what everything does.
- John_T__Morgan_May 08, 2015
Nimbostratus
Thanks for the reply. Waht I am actually looking for is whether or not there is a value in the attribute "extensionAttribute15". I am using this: expr { [mcget {session.ad.last.attr.extensionAttribute15}] != "" } But I get the following error "Rule evaluation failed with error: syntax error in expression " [mcget {session.ad.last.attr.extensionAttribute15}] = "" ": extra tokens at end of expression" So, I'm not sure if I actually have an extra token or if I just have a syntax error in the formation of the variable name. -John But i get an error - Chris_17748May 08, 2015
Nimbostratus
Are you getting the error when you try to save the the expression or when it evaluates? I'm wondering if the data stored in that attribute is a data type that has to be handled differently.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com