Hello

this oml use customlogin

i hope it helps!

Hi @budang haba ,

In OutSystems, the built-in user authentication and session management are tightly coupled with the Users module and its associated entities. While it's not recommended to completely bypass this system, you can create a custom authentication solution that works alongside the built-in one. Here's a more detailed approach:

1. Custom Entity Approach: Create your own custom entity (e.g., 'Employee') with the necessary fields for authentication, including a unique identifier that can be linked to the Users entity.
2. Custom Authentication Logic: Implement your own authentication logic using your custom entity. This is where you can apply your desired encryption and authenticity checks.
3. Link to Users Entity: After successful authentication with your custom entity, you'll need to link it to the Users entity to properly create an OutSystems session.
4. Use System Actions: Instead of using the 'User_Login' action from the Users module, you can use the more low-level 'Login' action from the System module. This allows you to create a session without directly interacting with the Users entity.

Here's a step-by-step process:

1. Authenticate using your custom entity (e.g., 'Employee').
2. If authentication is successful, retrieve or create a corresponding UserId in the Users table.
3. Call the System.Login action with the UserId. This creates the necessary session.

Example pseudo-code:

// Your custom authentication logic

If AuthenticateEmployee(username, password) Then

    // Get or create a corresponding User

    userId = GetUserId(employeeId)

    // Create OutSystems session

    System.Login(userId)

    // Additional custom logic as needed

End If

This approach allows you to use your custom entity and encryption methods while still leveraging OutSystems' session management capabilities. Remember to handle user roles, permissions, and other session-related information that might typically be managed by the Users module.

Keep in mind that while this method works, it bypasses some of OutSystems' built-in security features. Ensure you implement proper security measures in your custom authentication logic.

For encryption, you can use OutSystems' built-in cryptographic functions or integrate with external encryption libraries if needed.

If you need more specific guidance on implementing encryption or any part of this process, feel free to ask!

// CustomUser Entity

// Attributes: Id (Identifier), Email (Text), Password (Text)

// RegisterUser Action

Input: Email (Text), Password (Text)

Output: OutputMessage (Text)

HashedPassword = CryptoAPI.HashPassword(Password)

UserRecord.Email = Email

UserRecord.Password = HashedPassword

CreateCustomUser(UserRecord)

OutputMessage = "User registered successfully"

// LoginUser Action

Input: Email (Text), Password (Text)

Output: OutputMessage (Text)

UserRecord = GetCustomUserByEmail(Email)

If (UserRecord != Null) {

    IsPasswordValid = CryptoAPI.VerifyHashedPassword(UserRecord.Password, Password)

    If (IsPasswordValid) {

        OutputMessage = "Login successful"

    } else {

        OutputMessage = "Invalid credentials"

    }

} else {

    Outp

utMessage = "User not found"

}