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
 
Unanswered
← Guidance on creating SSO extension using an SSO API

Hello Vivian,

This is dependent on whether you want it inan iframe or as a new tab. If it is as a new tab then definitely an SSO extension. If you want it as an iframe in online banking then here is documentation on that: https://docs.q2developer.com/guides/frontend_development/enhanced_sso.html

For either of them you control the security, so you are required to do your own due diligence. During code review one of the things Q2 looks for is security so we will look at that also and try and check for any holes. From what I can tell this looks like a secure way of doing it just make sure the api calls are done with the Python code and that the user only gets what is absolutely necessary to perform the operation.

Thank you,
Trey Teter

Posted 2 years ago
Trey Teter
124 × 2 Administrator
0

Thank you, Trey!

— Vivian Gomez   2 years ago
17 Views
0 Answers
2 years ago
2 years ago