OpenAnywhere Overview

Deploying OpenAnywhere for an FI requires coordination across multiple teams; NT Account Opening/Support, Banno TechOps, Banno Infrastructure, and OpenAnywhere developers. This document is intended to provide the steps necessary for each team that participates in the process.

Onboarding

Requirements

The domain the FI is using for the applicant channel cannot be the zone apex or root domain, they must provide a sub-domain. For example it cannot be domain.com, but must instead be xyz.domain.com. This applies even if they want to use a domain different than their main domain.

DNS

Do we host their DNS?

This should be established before contacting the customer and confirmed on the kick-off call.
From a Mac; open a terminal and run dig +noall +answer domain.com NS with their domain name; do not lookup using the sub.domain.com from the applicant channel.
From Windows; Google provides a DNS toolbox to lookup the domain.

If the results include one of the entries below then it’s very likely we host their DNS. Treat * as a wildcard match for any number.

ns-*.awsdns-*.net  
ns-*.awsdns-*.org  
ns-*.awsdns-*.co.uk  
ns-*.awsdns-*.com  
*.profitstars.com  
*.profitstars.bank  
*.bancinternetgroup.com  
*.goldleaf.com  
*.jackhenry.com  
*.jackhenry.bank

Email Verification

To send an email verification email to a client, you may use the Jenkins job.

Note: if this is your first time logging into Jenkins, or if you’ve been logged out, you will be asked to sign in through GitHub. After signing in, if you see a page like , click the link to the job again. The page you want looks like this:

Click “Run” at the top left of the page.
Enter the address you would like to send the verification email to in the popup box, then click “Run” to start the job.
After starting the job, you can either click the pop-up at the bottom right of the screen to see the results, or click the most recent job in the list.

Note: if the list doesn’t automatically populate, try refreshing your page.

If the output looks similar to the snippet below, the email has been sent successfully.

...
{
		"MessageId": "xxxxxxxxxxxxxxxx-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-xxxxxx"
}
Notifying upstream projects of job completion
Finished: SUCCESS

Confirming email verification

Similar to the steps above in [Email Verification](#Email Verification), a separate Jenkins job has been created to assist with confirming whether or not the FI has clicked through to verify their domain in a timely manner.

If the domain has been verified, you will see a similar message to the below snippet in the job logs:

...
"Verification for identity email@bank.com success"
Notifying upstream projects of job completion
Finished: SUCCESS

I can’t see the Jenkins job linked above

Make sure you’re in the openanywhere-installation GitHub team. If you’re not, ping the @oa-banno-hosting-ff team on slack, and ask them to add you to it.

NT Implementation

Tracks the deploy process through launch. They’ll be gathering all the information used to deploy the FI’s instance of the application. This information will be entered into a GitHub issue for the Banno TechOps team do the next steps of configuration and release.

GitHub Issue

Create a new issue for Banno/TechOps with all fields and values populated.

The ATM logo/image can be attached as a comment in the issue.

TechOps

An engineer will assign themselves to the issue. If JHA hosts the client’s DNS then we will reach out to the appropriate internal teams to assist. Once we have verified all of the data is present we’ll queue up the implementation script and run it as part of our release cycle. Once this is done the GitHub issue will be closed out.

Testing

DNS

Part of this process involves either the FI or JHA teams (if we host DNS) creating a DNS record for the sub-domain being used for the applicant channel. The record should point to either openanywhere.banno.com or if a .bank domain then to openanywhere.jackhenry.bank. To validate if this is completed;

From a Mac; open a terminal and run dig +noall +answer accounts.domain.com CNAME
From Windows; Google provides a DNS toolbox to lookup the domain.