Rollout Considerations

The high-level process for enabling a single financial institution to use Jack Henry Identity for a product includes:

Steps and configurations by the Jack Henry Identity implementation team

• Complete one-time configurations for each new product using Jack Henry Identity for the first time.
• Create each financial institution if one doesn’t already exist.
• Provision access for initial back office administrator for each financial institution.

Steps and configurations completed by the financial institution

• Configure an OAuth client (external application) for the product.
• Provision additional FI users.

Steps and configurations completed by the integrating product development team

• Any configurations needed within the integrating product (.e.g clientId).
• Upon request from an FI, product development teams may assist with the configuration of the OAuth client (external application.) The back office administrator from the FI would need to temporarily grant the necessary permissions through the Users & Group application in Banno Admin.

Recommendations

• Develop a method of enabling Jack Henry Identity authentication per-financial institution, rather than planning for environment-level cutover only. This ensures that there’s an option to migrate customers in waves or batches.
• It’s a good idea to create specific instructions for FI’s to follow when configuring the external application(s) for your product so you can include your product-specific values (e.g. Redirect URIs, Scopes) that are not in our generic examples.
• Jack Henry product teams should connect with Developer Relations early in the process to learn more about internal operational readiness activities.