Plum Fuse Multi-Login Configuration
Purpose:
This knowledge-base article is intended to empower you to be able to create multi-login access for our Fuse customers, and to be familiar with the different variations of the “multi-login” URL (particularly what each is used for within our infrastructure).
URL Variations and Intended Usage:
The first and most powerful URL to familiarize yourself with is: https://multilogin.vxml.sharpencx.com/#/plum_admin/
This item, bearing the “plum_admin” designation, is the root “super user” end-point. By logging into this location, you can generate a customer-specific “admin” user account and tie it to a specific operational org/Fuse environment.
The second URL that site-admins should be aware of, is the following: https://multilogin.vxml.sharpencx.com/#/admin
This URL is what a customer contact (who has been granted admin permissions) would use to administer over other user multi-login accounts that have been built out for an org/Fuse environment.
It is NOT what gets the customer into the Fuse application (where they would make call-flow or config changes). This URL is specifically for resetting passwords, adding/deleting other multi-login accounts, etc.
The final URL to be aware of is the following: https://multilogin.vxml.sharpencx.com/#/login
This is the basic URL that a customer would leverage with their multi-login creds, to actually get into the Fuse environment that their account has been mapped to.
Adding Multi-login accounts for a Customer:
To add multi-login accounts to a customer org/Fuse environment for a customer, you’ll want to be accessing the super user “plum_admin” URL and logging in with the following account in 1Pass:
This will allow you to hit the “add user” button at the top of the page, and generate a new entry:
By tying the login information to a specific “targetID”, that controls what Fuse environment the account is being mapped against.
Enabling Self-Sufficient Customers:
When a multi-login account has the “is admin” flag set to “true” (by checking the “is admin” box under the add user menu), this enables them to login to the “admin” URL (variation #2 above)
Unlike the scope of visibility with the “plum_admin” admin URL (that can see all accounts across all orgs), this “admin” end-point allows users that have been configured with the “admin” flag for their Fuse org to see all other multi-login accounts tied to that same customer environment.
This is what a multi-login admin would use to administer changes, update passwords, or remove access for other accounts that have been tied to their specific org.
Getting into the App with Multi-Login:
To actually get into the Fuse environment that a multi-login account has been generated for, both an “admin” and generic-level user would both want to make sure they’re navigating to the login URL.
Upon entering their multi-login credentials, the user should be redirected to something like the following screen:
This represents the configuration, applications, etc that have been configured against the “targetID” account that a set of multi-login credentials have been mapped to.
Gotchas/Known Issues:
If you’re trying to access the Fuse application with the login URL, but are getting the following “invalid target tool error, there was a mapping that didn’t get set properly when you were adding an account under the “plum_admin” end-point:
This specific error is returned when the “tool” field isn’t set in the account creation menu:
NOTE: Because of database write/update conflicts that currently exist with this tool, you can’t “go back” and set this value after the account has been created.
While the webpage might make it look like a fuse/hosting “tool” value has been set, reloading the page will still show a blank value. You have to fully delete that account and start from scratch, in order to generate a multi-login account that can actually access the application.