We are building a CUBA app, and we have the following request. The app will be accessible through an existing portal using an iFrame. Based on that, the users will login into the company’s portal and from an available menu, a new web page will be displayed - this page will include an iFrame component that will responsible for the loading of the CUBA app. At this stage, when the application will be loaded, the login screen of the CUBA app should not be required again since the user will be already logged in through the portal. So, I would like to ask you how we could prevent the login screen from being displayed and providing the user’s credentials through another channel - possibly included in the URL string?
There are two ways of how you can log in CUBA application using URL.
The first way is using parameters in URL navigation. For instance, let’s say that
the token “e63cacd4-646b-4232-bd72-36ddff780bbf” is generated only for user “admin”.
So we can add the following code to the LoginWidow: