Integration Tips

The Unified Identity Service authenticates consumer users (customers or members of a financial institution). It includes some shared architecture with Banno Online, Jack Henry’s digital banking product (and the reference implementation for the Consumer APIs contained in the Digital Toolkit.)

In order for consumer users to login through UIS, each user must first establish a username and password through an enrollment flow. Each product integrating with UIS is responsible for determining and enforcing that a user is eligible to be established within the product before redirecting the user to UIS enrollment. See “New User Enrollment” for examples and details.

Decisions / Need to Knows About Your Approach

1. Backend For Frontend (BFF) architecture is strongly recommended for everyone (and is required for all JH products to ensure no tokens can be extracted from the browser).
2. What scopes do you need, and how will they be enforced?
3. How will you determine and enforce user eligibility before redirecting users to Unified Identity enrollment?
4. What 2FA security levels are appropriate for users in your product? Is it the same for all users, or will you need a mechanism for FI’s to set different requirements for different users (based on user type, risk/exposure level, or some other criteria specific to your product)?
5. Products integrating with UIS will use Client Credentials flow to make requests to the UIS enrollment API.
6. Your product will likely need to store the unique identifer from UIS along with your product’s unique identifier for each user. Note that if one person has two separate users within your product, that person can choose to use a single username and password (i.e. a single identity) to authenticate for both users. Your product will need to expect and handle that a single UIS UUID could be associated to more than one user within your product (productUserId).

Topics in this section

• New User Enrollment