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.
If you are developing using a Jack Henry test environment, you will not have access to Banno People. In this case, Jack Henry is the acting administrator of the financial institution and you will have to contact us for any Banno People operations.
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
) are what you’ll use to authenticate with Banno using OAuth/OpenID Connect. See the Authentication topic for more details.
External Application is what you’ll use when configuring your plugin.
It is possible to add more than one
. However, the order is important.
Redirect URIthat handles your initial authentication flow for your
pluginneeds to appear 1st in the
Redirect URIlist. Banno’s Dashboard UI expects to call the 1st
Redirect URIto render the
plugin’s card face.
- The order is not important for any other
Redirect URIsin the list.
Redirect URI is matched using exact string matching. If the
Redirect URI does not match, then the authorization flow will not be valid.
Redirect URImatching 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 URIformats are not allowed so https://*.example.com is NOT valid.
See the Restrictions page for more details.