External Applications

Plugin Framework > Architecture > External Applications

Plugins require a set of credentials to be configured as an External Application in the Banno People app. The back office administrator at your financial institution can do this for you in the External applications section of Banno People.

Understanding Your Development Experience
Are you a financial institution?

If you are a financial institution or working directly with a financial institution, you should work with the back office administrator at your institution to get appropriate access to Banno People.

Are you a fintech or independent developer?

If you are a fintech or other developer working without a financial institution, you are likely using the JackHenry.Dev developer portal. In this case, you will not have access to Banno People, however you will still have the ability to create and configure many aspects of your external application and plugin.

For more information on this, see our troubleshooting page.

Plugin - Setup a new external application

First, the administrator must select Custom name as the type of external application. They will need to enter a name for these credentials.

Next, the administrator must select a Link type of PluginCard. They will need to enter a name for the Link title.

Finally, the administrator must enter your Redirect URI and click the save button. The Redirect URI (and the auto-generated Client ID and Client Secret) are what you’ll use to authenticate with Banno using OAuth/OpenID Connect. See the Authentication topic for more details.

The External Application is what you’ll use when configuring your plugin.

Order of Redirect URIs

It is possible to add more than one Redirect URI. However, the order is important.

  • The Redirect URI that handles your initial authentication flow for your plugin needs to appear 1st in the Redirect URI list. Banno’s Dashboard UI expects to call the 1st Redirect URI to render the plugin’s card face.
  • The order is not important for any other Redirect URIs in the list.
Exact String Matching of Redirect URIs

Each Redirect URI is matched using exact string matching. If the Redirect URI does not match, then the authorization flow will not be valid.

  • Redirect URI matching is case-sensitive and path-inclusive so http://localhost:8080/dynamic is NOT the same as http://localhost:8080/Dynamic and NOT the same as http://localhost:8080/dynamic/.
  • ‘Wild card’ Redirect URI formats are not allowed so https://*.example.com is NOT valid.
Dynamically Updating Content Security Policy (CSP) with Redirect URIs
See the Restrictions page for more details.

Have a Question?
Have a how-to question? Seeing a weird error? Get help on StackOverflow.
Register for the Digital Toolkit Meetup where we answer technical Q&A from the audience.
Last updated Mon Dec 5 2022