eric_haupt1
Apr 03, 2019Nimbostratus
APM LDAP Query Failure - not using fallback
I running an LDAP query in a policy that is performing
return [mcget {session.ldap.last.attr.userPrincipalName}]
I know this is working for known UPNs, but I'm not catching the exceptions and taking the fallback path.
I've noticed that even upon query failure the policy is not using the fallback path even when the last.errmsg is "No such object" and the query result is "0" - the policy continues to the variable assign, which it should only perform when a UPN is matched.
Any suggestions?