The UX Component can include integrated login/logout functionality. This means you don't have to use a separate Login Component, or (AppLauncher with login turned on) to authenticate users in your application.
- Customize login failure messages
You can customize the various messages that the security framework displays when login errors occur.
- Has integrated login functionality
To turn on the integrated login feature, go to the Properties pane on the UX Builder and check the 'Has integrated login functionality' property, as shown in the image below:
- Logout does a full page reload
When the user logs out, do you want this UX component to reload? If you check this option, the component's layout is re-computed on the server (and controls on the UX for which membership in security groups are required are hidden).
- Password control
You must specify which controls on the UX component are used for entering the password. Your UX component will therefore need to have two controls (likely textbox controls) where the password is entered.
- Placeholder for login errors
You must put a placeholder control on the UX (see [Placeholder] in the Other Controls section of the UX Builder toolbox) to indicate where login errors should be shown. Use this property to specify the name of the placeholder.
- User name control
You must specify which controls on the UX component are used for entering the username. Your UX component will therefore need to have two controls (likely textbox controls) where the username is entered.
The primary use case for integrated login in the UX component is for mobile applications where the application is typically built using a UX component.
However, another use case for the integrated login in the UX is to build a custom login dialog to replace the built-in Login component.
In the video below, we show how an authentication layer has been added to a mobile application.