The Encrypted Sign In action enables users to log in to the system securely in an encrypted manner. Username and password information is sent to the server in an encrypted format, thereby minimising the risk of credentials being intercepted by unauthorised individuals.

Technical Features

Secure Login: Credentials are transmitted in encrypted form, ensuring data security.
Data Protection Compliance: Provides a structure that complies with data protection laws such as KVKK and GDPR.
Web & Mobile Compatibility: The action works on both web and mobile applications.
Compatible with Standard Login: A token is created after login to initiate the session.

Encrypted Sign In Action Application Steps

1. Add the Encrypted Sign In Action

Log in to the Kuika platform.
Open the relevant project from the Apps screen.
Go to the UI Design module.
Select the button that will trigger the login process (e.g. ‘Log In’).

Select the button and add the Authorisation > Encrypted Sign In action from the + ADD ACTION menu according to the desired trigger event (Initial Actions, OnClick, OnBlur, etc.).

2. Configure the Parameters

User Name (String-Required): The username or email address used by the user to log in to the system.
Password (String-Required): The user's password.

Parameter values are typically retrieved from Form components, Screen Inputs, or Action Results. They can be easily linked using the Symbol Picker.

Use Case: Secure Session Start on Login Screen

A user wants to start an encrypted session by entering their username and password on the application's login screen. This process works as a more secure version of standard login.

Applying the Encrypted Sign In Action

Element: ‘Login’ button
Trigger: OnClick
Action: Authorisation → Encrypted Sign In
User Name: Current.email
Password: Current.password

With this configuration, the user logs into the system securely. The password and username are encrypted and sent to the server. If the verification is successful, the session is started and the user is redirected.

Encrypted Sign In Action Advanced Customisations

Redirect After Successful Login: By adding a Navigate action after the Encrypted Sign In action, the user can be redirected to the main screen or a role-based page.
Notification When Login Fails: If the password or username is incorrect, the Notify action can be triggered using If Then Else to alert the user.
Dynamic Data Storage: After a successful login, user information can be stored in Local Storage or Screen Input.
Token Usage: The JWT token created after a successful login can be used for authentication in API queries.

Technical Risks and Precautions

Incorrect Parameter Connection: Assigning incorrect components to the User Name and Password fields may cause the login process to fail.
Insecure Data Storage: Do not store the user's password on the client side (e.g. Local Storage).
Lack of Post-Login Verification: The authentication token must be used correctly to retrieve user data after login.
Open Redirect Threat: Ensure that the page to which the user is redirected after login is secure and defined.

The Encrypted Sign In action enables users to sign in securely and with encryption in Kuika applications. It is preferred especially in applications that require high security. The entire login process is carried out with encrypted communication. It can be combined with other actions such as redirection after successful login, notifications, and user data processing.