Improve (saml) login and subsequent portal load performance Depending on the system a UMC server can handle a constant load of tow (or even less) logins and subsequent portal loads per second. This is becoming worrisome in large school environments, there this is a common workflow to see all portal links of which some might be only visible for logged in users.
As briefly discussed with Alexander: 1. most important from my point of view is to do tests with several hosts providing the same portal and SAML login to ensure that we scale well. Based on that, a well configured Loadbalancing should be able to serve even large environments. 2. we should fix Bug #51402 / Bug #50583 which might be part of the problem and re-do these tests afterwards
We need more explicit goals here. The main objective is to handle environments with 100k user accounts which make use of the portal on a daily base. This is currently possible with a loadbalancer, but we should have automated tests and a performance analysis to ensure that the performance is on this level in future releases.
(In reply to Ingo Steuwer from comment #4) > This is currently possible with a loadbalancer, but we should have automated > tests and a performance analysis to ensure that the performance is on this > level in future releases. The main limit which existed in the past was fixed with Bug #51729
This issue has been filed against an older version of UCS. With further development of our products affected components may have vastly changed while the corresponding use cases might have changed. Thus, this issue is now being closed. If there still is a need for this feature, please use "Clone this bug" or reopen this issue. In this case please provide information on how this issue would benefit you.