Skip to content

ntlm-authentication.md

Latest commit

 

History

History
268 lines (196 loc) · 5.75 KB

ntlm-authentication.md

File metadata and controls

268 lines (196 loc) · 5.75 KB
Raw

NTLM Authentication

RDPGW supports NTLM authentication for simple setup with Windows clients, particularly useful for small deployments with a limited number of users.

Advantages

  • Easy Setup: Simple configuration without external dependencies
  • Windows Client Support: Works with default Windows client mstsc
  • No External Services: Self-contained authentication mechanism
  • Quick Deployment: Ideal for small teams or testing environments

Security Warning

⚠️ Plain Text Storage: Passwords are currently stored in plain text to support the NTLM authentication protocol. Keep configuration files secure and avoid reusing passwords for other applications.

Configuration

1. Gateway Configuration

Configure RDPGW to use NTLM authentication:

Server:
  Authentication:
    - ntlm
Caps:
  TokenAuth: false

2. Authentication Helper Configuration

Create configuration file for rdpgw-auth with user credentials:

# /etc/rdpgw-auth.yaml
Users:
  - Username: "alice"
    Password: "secure_password_1"
  - Username: "bob"
    Password: "secure_password_2"
  - Username: "admin"
    Password: "admin_secure_password"

3. Start Authentication Helper

Run the rdpgw-auth helper with NTLM configuration:

./rdpgw-auth -c /etc/rdpgw-auth.yaml -s /tmp/rdpgw-auth.sock

Authentication Flow

  1. Client initiates NTLM handshake with gateway
  2. Gateway forwards NTLM messages to rdpgw-auth
  3. Helper validates credentials against configured user database
  4. Client connects directly on successful authentication

User Management

Adding Users

Edit the configuration file and restart the helper:

Users:
  - Username: "newuser"
    Password: "new_secure_password"
  - Username: "existing_user"
    Password: "existing_password"

Password Rotation

  1. Update passwords in configuration file
  2. Restart rdpgw-auth helper
  3. Notify users of password changes

User Removal

Remove user entries from configuration and restart helper.

Deployment Options

Systemd Service

Create /etc/systemd/system/rdpgw-auth.service:

[Unit]
Description=RDPGW NTLM Authentication Helper
After=network.target

[Service]
Type=simple
User=rdpgw
ExecStart=/usr/local/bin/rdpgw-auth -c /etc/rdpgw-auth.yaml -s /tmp/rdpgw-auth.sock
Restart=always
RestartSec=5

[Install]
WantedBy=multi-user.target

Docker Deployment

# docker-compose.yml
services:
  rdpgw-auth:
    image: rdpgw-auth
    volumes:
      - ./rdpgw-auth.yaml:/etc/rdpgw-auth.yaml:ro
      - auth-socket:/tmp
    restart: always

  rdpgw:
    image: rdpgw
    volumes:
      - auth-socket:/tmp
    depends_on:
      - rdpgw-auth

volumes:
  auth-socket:

Kubernetes Deployment

apiVersion: v1
kind: ConfigMap
metadata:
  name: rdpgw-auth-config
data:
  rdpgw-auth.yaml: |
    Users:
      - Username: "user1"
        Password: "password1"
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: rdpgw-auth
spec:
  template:
    spec:
      containers:
      - name: rdpgw-auth
        image: rdpgw-auth
        volumeMounts:
        - name: config
          mountPath: /etc/rdpgw-auth.yaml
          subPath: rdpgw-auth.yaml
      volumes:
      - name: config
        configMap:
          name: rdpgw-auth-config

Client Configuration

Windows (mstsc)

NTLM authentication works seamlessly with the default Windows Remote Desktop client:

  1. Configure gateway address in RDP settings
  2. Save gateway credentials when prompted
  3. Connect using domain credentials or local accounts

Alternative Clients

NTLM is widely supported across RDP clients:

  • mRemoteNG (Windows)
  • Royal TS/TSX (Windows/macOS)
  • Remmina (Linux)
  • FreeRDP (Cross-platform)

Security Best Practices

File Permissions

Secure the configuration file:

sudo chown rdpgw:rdpgw /etc/rdpgw-auth.yaml
sudo chmod 600 /etc/rdpgw-auth.yaml

Password Policy

  • Use strong, unique passwords for each user
  • Implement regular password rotation
  • Avoid reusing passwords from other systems
  • Consider minimum password length requirements

Network Security

  • Deploy gateway behind TLS termination
  • Use private networks when possible
  • Implement network-level access controls
  • Monitor authentication logs for suspicious activity

Access Control

  • Limit user accounts to necessary personnel only
  • Regularly audit user list and remove inactive accounts
  • Use principle of least privilege
  • Consider time-based access restrictions

Migration Path

For production environments, consider migrating to more secure authentication methods:

To OpenID Connect

  • Better password security (hashed storage)
  • MFA support
  • Centralized user management
  • SSO integration

To Kerberos

  • No password storage in gateway
  • Enterprise authentication integration
  • Stronger cryptographic security
  • Seamless Windows domain integration

Troubleshooting

Common Issues

  1. Authentication Failed: Verify username/password in configuration
  2. Helper Not Running: Check if rdpgw-auth process is active
  3. Socket Errors: Verify socket path and permissions

Debug Commands

# Check helper process
ps aux | grep rdpgw-auth

# Verify configuration
cat /etc/rdpgw-auth.yaml

# Test socket connectivity
ls -la /tmp/rdpgw-auth.sock

# Monitor authentication logs
journalctl -u rdpgw-auth -f

Log Analysis

Enable debug logging in rdpgw-auth for detailed NTLM protocol analysis:

./rdpgw-auth -c /etc/rdpgw-auth.yaml -s /tmp/rdpgw-auth.sock -v

Future Enhancements

Planned improvements for NTLM authentication:

  • Database Backend: Support for SQLite/PostgreSQL user storage
  • Password Hashing: Secure password storage options
  • Group Support: Role-based access control
  • Audit Logging: Enhanced security monitoring