Integration and Configuration

Below we list several scenarios which partners may wish to present to end users, along with the correct configuration settings for each situation.

Scenario	Settings
Answer MFA for a specific member	Set the `current_member_guid` to a member whose `connection_status` is CHALLENGED. Connect will load the MFA view so the end user can respond to the MFA challenge.
Disable search when loading a specific institution	Set `disable_institution_search` option to true and set the `current_institution_code` or `current_member_guid` option. Connect will load the login view for the specified institution, but will not allow the end user to navigate to the search view.
Resolve a member’s error(s)	Set the `current_member_guid` option to a member in an error state. Connect will load in the error view so the end user can resolve the error.
Run aggregation but exclude transactions	Set the `include_transactions` option to false when creating or updating a member. Connect will not automatically aggregate transaction data. Future manual or background aggregations will not be affected.
Run aggregation with a specific institution	Set the `current_institution_code` option to the desired institution’s code, but do not set the mode option. Connect will load the login view for that institution.
Run verification with a specific institution	Set the `current_institution_code` option to the desired institution’s code, and set the mode option to verification. Connect will load the login view for that institution.
Update a member’s credentials	Set the `current_member_guid` to the desired member’s GUID, and set the update_credentials option to true. Connect will load the update credentials view for the member. This option should be used sparingly. It is best practice to only use `current_member_guid` and let the widget take care of things.

Example Integration

EpicBank wants to use a SAML login process to load widgets within their online banking. Their client_id has been set to epic and they send the following configuration information to MX. Once MX has received and confirmed this configuration, Epic Bank changes their online banking to embed an iFrame on their landing page like the Identity Provider Certificate example that follows. When this iFrame loads in the user’s browser it sends a GET request to Epic Bank’s identity provider service asking to send the user to MX. The identity service verifies that the user has an active session and then renders a page which sends a POST request to https://int-app.moneydesktop.com/login/epic. When MX receives the POST request, the widgets service decrypts the SAMLResponse and uses the nameid attribute to start a session for the user and load the widget in the iFrame.

Identify Provider Certificate

Certificate fingerprint

603c36feb6a512ec64418fbe776edc2aee7ec3e9a2fcd07d04192ac1d277bb06

Digest algorithm

http://www.w3.org/2001/04/xmldsig-more#rsa-sha256
<iframe width="850" height="550" border="0" frame="0" frameborder="0" allowtransparency="true" src="https://www.epicbank.com/idp?sp=mx" marginheight="0" marginwidth="0"></iframe>

​Configuration Scenarios for the Connect Widget

​Example Integration

​Identify Provider Certificate

​Certificate fingerprint

​Digest algorithm

Configuration Scenarios for the Connect Widget

Example Integration

Identify Provider Certificate

Certificate fingerprint

Digest algorithm