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
Permissions for SSO iframe

We are developing an ATM locator extension that loads an external web application in iframe using the recommended SSO Extension approach.
So far, so good, but we have run into 3 questions we need help with so far:

  1. Permissions for the SSO iFrame
    When we normally load this web app into an iframe, we are able to set a mission-critical attribute for the iframe to allow geolocation permissions so that GPS/Browser Geolocation search will work in our Javascript. This is normally done either explicitly in an HTML iframe tag, or by creating an iframe tag with javascript and adding attributes. E.G. frame.setAttribute("allow", "geolocation");

How can we add this geolocation permission to the SSO iframe?

  1. Title for Overpanel
    When our external web app URL is loaded in an overpanel (by setting RENDER_IN_NEW_WINDOW = False) there is a large whitespace along the top of the overpanel (inline with the X close window button) that is presumably missing content. This seems like the right place to put formatted title text, E.G. "Branch & ATM Locator".

What is the recommended way to assign and style that title content? I haven't been able to find any documentation about that.

  1. Boolean FI Config Inputs for RENDER_IN_NEW_WINDOW
    Rather than hard code RENDER_IN_NEW_WINDOW = False, we would like to leave it up to each FI as an input parameter during installation so they can choose to show our locator in an overpanel or in a new tab using the VENDOR_CONFIGS array. This seems to work as an input, but I think we are probably getting it as a string input instead of a boolean.

What is the correct way to get a Boolean input from the installing FI for VENDOR_CONFIGS and then how can we properly assign that value to set the SSO to open in an overpanel or a new tab based on the supplied True or False value?

Thanks for any help!

Posted 3 years ago
Votes Newest

Answers 2


Regarding #3, it's probably just easiest with the way the product is set up to request the render in new window true/false at deploy time for an FI. The variable in the extension hints to the installer whether to set a database flag as true or not on installation, as you pointed out. But we have the ability to flip that database flag at any time. So while it's listed in the extension for convenience as a way for the dev to message to the one installing the extension later (who might also be you in a sandbox stack, for instance), they can be controlled separately.

The VENDOR_CONFIGS are a great way to have things stored in the database passed to the extension at runtime, but it's a bit of a chicken and egg usecase here. Can't seed the database with things from the database. If you just list this in extra data or whatever that field is called on your deployment ticket, we'll make sure to get it set up correctly when installed.

Posted 3 years ago
Brian Mego
227 × 1 Administrator
0

Thanks Brian! So, are you suggesting that we just set the RENDER_IN_NEW_WINDOW value to our default and then tell you what the value should be on a case by case basis when individual FIs are implementing?

— Jason Green   3 years ago

Hi Jason regarding question #1, geolocation and camera permission are enabled already as default for extensions, do you have any issues with that ? you can just open a sdk ticket so we can track it down.
And regarding question #2, do you use openURL capability to open your external web app with showInOverpanel: true ? we provode setTitle capability so people can set own title on own extension but if it's an external app, we don't support it yet but you can still request a new feature by opening sdk ticket.

Thanks
Alex

Posted 3 years ago
Alex Jeong
60 × 1 Administrator
0

Thanks Alex!

Regarding #1 - the SSO Extensions open in an iframe. The iframe does not have geolocation permissions set by default, and I'm not sure how to set them in the context of the SSO Extension. I'll go ahead an submit a SDK ticket as suggested.
Regarding #2 - in the SSO Extensions, the HTML for the extension is defined by a jinja2 HTML template which is loaded into an iframe and then displayed in either a new tab or an overpanel. In both cases, the source of the iframe is then redirected to the external URL using javascript window.location={
} in the page load event.

— Jason Green   3 years ago
0

The decision of overpanel vs. new tab is controlled only by the RENDER_IN_NEW_WINDOW variable in the extension.py of the SSO Extension.

— Jason Green   3 years ago
132 Views
2 Answers
3 years ago
3 years ago