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.
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
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.