Plugins built using the Plugin Framework use the Authentication Framework to provide secure authentication.

See the Authentication Framework docs for details.


The Plugin Framework is implemented in Banno’s UI via iframes that render individual plugins.

Web browsers have become increasingly restrictive on cross-site cookie tracking and this affects how cookies can be used within a plugin.


When developing a plugin, you may want to set your browser settings as follows.


This is not a solution that will work for Production usage.

  • For Chromium-based browsers, you’ll have to configure the browser to allow 3rd party cookies.
  • For Firefox, you’ll have to enable 3rd party cookies.
  • For Safari, you’ll have to disable the “Prevent cross-site tracking” option.


When you are ready to use your plugin in Production:

If you need to write a cookie in the plugin, you’ll need to host your public-facing web server at a subdomain of the Banno Online domain name for your financial institution.

For example, assume you have the following URLs for your financial institution:

  • Main (marketing) website:
  • Banno Online website:

You could host the plugin at a subdomain named “plugin” which would give you:

  • Plugin domain:

In our browser testing, this subdomain setup is recognized by all browsers and the cookies are not treated as 3rd party cookies.

HTTPS, Certificates, and Certificate Authorities

You’ll have to take care to ensure that the Certificate Authority (CA) and intermediate certificates are configured correctly for your plugin server’s SSL certificate.

An incorrect configuration may result in your plugin’s content failing to display within Banno Online and Banno Mobile.

External Resources

If you want to learn more about handling cookies in your web browser, these external resources may be useful: