Banking Core Connectivity Guide
Last updated
Last updated
Glyue integrates across your technology stack, including on-prem systems. The most common type of on-prem system is a core, and often, its associated middleware.
An on-premises system is a system that is on its own, internal network, and is not accessible by systems that are not on that network.
Below are the steps outlining how Glyue establishes connectivity with an on-prem core. Some details may differ depending on the specifics of a core/middleware, but the high level steps remain the same.
At a high level, there are three steps:
Establish a VPN between Glyue’s servers and your bank’s internal network
Configure middleware for Glyue API access
Create a service account for Glyue on the core
Let’s explore each step in detail below.
A VPN (Virtual Private Network) is a private “tunnel” between systems, in this case, Glyue servers and your on-prem core. Glyue uses a VPN to communicate with your core to keep the information secure and private. Setting up a VPN will require coordination between your IT team and Glyue’s network engineers.
Once the VPN is set up, your IT team will expose certain systems to the VPN so they can be accessed by Glyue. This can be your core and middleware, a database, or other systems running on your internal network.
Some cores may not be hosted on-prem, but instead as a managed service in a 3rd-party datacenter, such as one managed by the core’s vendor. For these setups, Glyue does not require a VPN to your network, and will instead work with you and the vendor to establish access to your core via the managed datacenter.
Most cores have an associated system called a “middleware” that sits between the core and external systems, governing access to the core. Glyue will need to be configured as an application in the middleware, along with the permissions necessary to execute your use cases.
Sandbox staff will work with you to determine the correct set of permissions for your specific needs.
If you do not have a middleware instance set up, you will need to work with your core vendor to install/license one before Glyue can integrate with your core.
Once Glyue is configured in the middleware, it needs an account on the core in order to read data and make changes. This is called a “service account”, to indicate that it’s being used by a service (Glyue) instead of a regular employee of the bank.
Glyue’s service account will also need the appropriate permissions to execute its intended use cases. These will be similar to, but may not exactly mirror, the permissions set earlier in the middleware configuration step.
If you are building multiple integrations with separate purposes, it may be appropriate to create separate service accounts for each integration. Consult with your Sandbox Banking engineers to determine the best approach.
Once a VPN, middleware configuration, and core service account are set up, you will have the necessary information to set up the access credentials within Glyue. This can be done via the configuration wizard on Glyue’s Build page.
