How does a UPA server handle duplicate login credentials from different servers?

bneway

We have a total of seven different UPA consumer applications each on a different server targeting a handful of different UPA servers. Until recently, we had five of these consumers all targeting the same UPA server (same IP/port configuration). Simply because it has worked historically, and because we did not want to break what was working, all of the consumer applications use identical credentials for the RSSL_DMT_LOGIN domain. These values, as listed in the ETA C Edition Refinitiv Domain Model Usage Guide Section 3.2, include user name, password, application ID, application name, instance id, etc. Our application currently uses the same values no matter what server it is on. When we recently added two new servers with UPA consumer applications, both targeting the same UPA server as the other applications, we briefly experienced a disconnect from the UPA server. This has caused us to wonder if perhaps there is a limit to identical credentials that we finally ran into. Do you know how a UPA server would handle logins with the same credentials all coming from different servers? Do you know if there are constraints on which values can be duplicated and which cannot? And finally, if the UPA server does not allow a certain amount of duplicate login credentials, do you know which ones we should update in our application so that the UPA server can see them as distinct? Thank you very much.

Jirapongse

@bneway

Thank you for reaching out to us.

You have mentioned UPA servers. Are they your own UPA Interactive Provider applications or ADS servers? Typically, the appliations or ADS servers will manage a number of mounts connected to themselves. If they are ADS servers, you need to check the ADS configurations or contact the ADS support team directly via MyAccount to verify the configurations.

To answer your questions, please let me know what UPA servers (RTDS, RTO, or Edge device) you are using.