Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
Answered
Event Driven Validation (EDV) Adapter

Question about the new Event Driven Validation (EDV) Adapter feature. We currently use Patrol to montior certian high-risk actions in Online Banking if the session is deemed suspect only or require a SAC regardless if the login is deemed either non-suspect or suspect.

  1. How does this work with how the login is classified? Can you choose to only require EDV if the login is deemed suspect?
  2. Can this be used with existing extensions that were developed by Q2? For instance, if we want to require step-auth for Member to Member transfers. Can I create an EDV extension with this new freature to require a SAC for that particular audit action?

Thanks
Bradley

Votes Newest

Answers


Hi Bradley,

EDV will be sent regardless to the extension, but one of the properties is is_suspect. You can do with that what you will, either terminate the session, perform step up, or move on. There are of course several other fields passed in with that object for you to action on.

In terms of adding EDV in front of existing extensions, it's possible to configure an SSO to do this in newer version of UUX, but it's just the system's built in step up, not necessarily a custom built thing provided by you.

Brian

Posted one year ago
Brian Mego
227 × 1 Administrator
134 Views
1 Answer
one year ago
one year ago