There are multiple internal web applications use a common log-in page. Can we separate login and application navigation into two separate adapters? We would like the login adapter to be reuse by another internal web application. Is the solution approach possible? Or what is the best practice to build a re-useable common log-in component?
@FrancisH9625This is possible. The Universal Web Application (UWA) will attach to any MSEdge or Chrome process, even those not started by your Application (formerly called Adapter). You could potentially create a separate UWA where you have interrogated the “login page” and have created all of your login-related logic. As long as this is set to MonitorAll and you start it on the start of the project, anytime you navigated to the login page in any Chrome (or Edge depending on which browser your Application is setup to use) window, it will match. Once you login, the remaining pages you have interrogated will match in their respective Applications.
Best practice would be to use the Assisted Sign On built-into the Application, however in this case with multiple Applications sharing the same login controls, you probably should need to create a single one to handle them all.