Create central vendor area per institution for storing account credentials for inserting into central resource URLs

This is something we have discussed over the years, but I wanted to make an official request see if this would be feasible.

Currently, institutional credentials, such as EBSCO Cust ID and ProQuest ID are stored in an institution's allocations. This means we are having to maintain it over a hundred times per institution. For example, when a new private K-12 is onboarded, all 100+ of their EBSCO allocations have to be updated to contain their Cust ID. We then reference this value using the {VAR:url_dbsuid} variable which looks for the user id field in the allocation.

Example for Academic Search Complete (EBSCO):

https://search.ebscohost.com/login.aspx?authtype=ip&custid={VAR:url_dbsuid}&profile=ehost&defaultdb=a9h

We also keep this value under the EDS tab in the Cust ID field:

Here's another example for Research Library (ProQuest): https://www.proquest.com/pqrl/embedded/{VAR:url_dbsuid}?accountid={VAR:url_dbspwd}

For ProQuest, we actually keep the account ID and auth token in each ProQuest research allocation.

Would it be possible have a vendor's area for each institution which contains their account credentials that are used for generating resource access links? Then we could insert this information into resource links whenever we need it using variables.

It would save a lot of time when setting up new institutions of setting up a ProQuest/EBSCO resource for institutions.