[TASK] Refactor Socketmap, LMTP, and Authentication Logic for Reusability

[Aravinda-HWK]

What needs to be done?

Description:

Currently, there are multiple implementations of similar logic across the socketmap service, LMTP handling, and authentication-related components—especially around group member validation and caching. This results in code duplication and inconsistent usage patterns.

Problem:

• Group member checks are implemented in multiple places.
• Caching mechanisms are not shared and are handled separately.
• Some logic overlaps between socketmap, LMTP, and authentication flows.

Proposed Improvement:

-Refactor shared logic into reusable functions/modules.

• Introduce a common caching mechanism that can be used across all components.
• Standardize group member validation logic to avoid duplication.
• Ensure consistent behavior across socketmap, LMTP, and authentication flows.

Tasks:

• Identify duplicated logic across socketmap, LMTP, and authentication.
• Extract common functions into shared modules.
• Implement a unified caching strategy.
• Refactor existing code to use the shared implementations.
• Test all affected flows to ensure no regressions.

Goal:

Improve maintainability, reduce duplication, and ensure consistent behavior across all related components.