You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: implement MFA enhancements and agent authentication improvements
- Added MFA (Multi-Factor Authentication) support to the authentication process, requiring verification via TOTP (Time-based One-Time Password).
- Introduced a challenge mechanism for MFA, allowing users to complete authentication with an OTP code.
- Enhanced the agent controller to sanitize payloads and include MFA requirements for sensitive operations.
- Updated the authentication service to handle MFA challenges and verify OTP codes, improving security during login.
- Implemented additional checks for agent states and IP validation to ensure only authorized access.
- Refactored various controllers to enforce MFA on critical actions, enhancing overall application security.
'clientIp = valeur utilisée par Nest (auth, audits). Ce n’est pas forcément « votre PC » si la connexion TCP passe par un relai (tunnel, port forward, Docker/Nitro).';
99
-
100
-
if(xffEchoesPeer&&!hasTrustedForward){
101
-
hintFr+=
102
-
' Ici X-Forwarded-For ne fait que répéter l’IP du pair TCP (relai) : il est ignoré pour la résolution. Sans X-Real-IP / CF-Connecting-IP / premier hop X-Forwarded-For fiable, Nest ne peut pas inventer votre IP LAN. Solution : reverse-proxy (nginx, Traefik…) qui transmet le client, puis SESAME_TRUST_PROXY=1 sur l’API.';
103
-
}
104
92
105
93
return{
106
94
clientIp,
@@ -115,6 +103,5 @@ export function buildClientIpDebugPayload(req: Request): Record<string, unknown>
0 commit comments