The Sign In action on the Kuika platform allows users to log in to the application securely. It starts the authentication process by verifying the user's credentials such as email address and password. Once the login process is successful, the user can access all functionalities within the application. Sign In action is supported in both web and mobile applications.
Technical Specifications
Authentication: Users are allowed to log in with their e-mail address and password.
Secure Login: A secure login is provided by verifying user information during the login process.
Web and Mobile Compatibility: Sign In action is compatible with both web and mobile platforms.
Dynamic Login Management: User information can be dynamically verified and appropriate roles and permissions can be assigned to the user.
Easy Integration: By integrating with different parts of the app, you can provide users with fast login.
Sign In Action Implementation Steps
Adding Sign In Action to the Project
Log in to the Kuika platform and open the project you are working on.
Open the Properties panel on the right panel in the UI Design module.
From the + ADD ACTION drop-down menu, select an appropriate trigger action (event) such as Initial Actions, OnClick, OnBlur respectively → Authorization → Sign In.
Configuring Sign In Parameters
In the fields below, you can configure the necessary parameters for the login process:
Username :
Necessity Yes
Description: The user's e-mail address or username must be entered. This field is the user's ID defined to log in to the system.
Type: String
Input Enter the username or e-mail address. Data can be imported into this field primarily from data sources such as Action Result. Other sources such as Method Input, Current, Screen Input, Fixed or Component can also be used. These categories can be defined by selecting them via Symbol Picker.
Password:
Necessity Yes.
Description: Enter the password the user will use to log in. This is required to authenticate the user.
Type: String
Input Enter the user's password. Data can be imported into this field primarily from data sources such as Action Result. Other sources such as Method Input, Current, Screen Input, Fixed or Component can also be used. These categories can be defined by selecting them via Symbol Picker.
Completing the Input Process
After configuring your parameters, click SAVE to save your changes. This will ensure that the Sign In action is successfully added.
Usage Scenario: User Signs In to the Application
On the login screen of the application, the user enters his/her e-mail and password and clicks on the “Login” button. With this action, the system validates the user's information and after successful login, the user gets access to the application.
Adding Sign In Action to Login Form
Log in to the Kuika platform.
Open the project you will work on from the Apps screen.
Switch to the UI Design module.
Drag and drop a Form and two Text Inputs (one for e-mail and one for password) from the Elements panel on the left side.
Add a Button under the Form and write “Login” in the Label.
Select this button and open the + ADD ACTION menu from the Properties panel on the right sidebar.
Select OnClick → Authorization → Sign In action.
Configuring the Sign In Action
In the action configuration window that opens, define the following fields:
Username: formData.email
Password: formData.password
Then click the SAVE button to complete the action.
What can be done after login (Optional)
If navigation is desired after the user logs in, the following can be added as a second action just below the Sign In action:
+ADD ACTION → Navigation → Navigate
To Screen: The main screen of the application (for example: “Dashboard”)
Open As: Current Page
This way, the user is redirected directly to the app home page after logging in.
With this scenario, users can securely log in to the app and access personalized content.
Sign In Action Advanced Customizations
Advanced Authentication: In addition to the Sign In action, additional layers of security can be integrated. For example, security measures such as two-factor authentication (2FA) or CAPTCHA can be used to make login more secure.
Dynamic User Routing: After the user logs in, routing can be done according to the user's role or authorizations. For example, users in the admin role can be directed to the admin panel, while normal users can be directed to the main screen. This type of dynamic redirection provides experiences that are customized according to the user's role.
Email and Password Verification: Before verifying user information, it is important to check the validity of the email address and the security of the password. This prevents users from logging in with false information and helps to ensure security.
Technical Risks and Precautions
Incorrect Email or Password: Email address and password must be verified correctly. Incorrect logins can be prevented by giving error messages to the user.
Account Security: Passwords should be stored according to strong security policies and password security should be ensured. For example, passwords can be hashed.
High Traffic: The system must be able to cope with a large number of login requests. Load balancing and caching strategies can be used.
The Sign In action allows users to securely log in to your application and manages all authentication processes. The Sign In action ensures that users can only access the system with valid credentials. The Sign In action, which works harmoniously on web and mobile platforms, improves the user experience and increases the security of the application. It is a powerful tool to effectively manage users' access control, ensuring that only authorized people can access different features of the application.
