Proxy Authentication

Authentication controls proxy access. HTTP may use the Proxy-Authorization header; SOCKS5 has its own username/password authentication. IP allowlisting may authorize source IPs where the provider supports that mode, or serve as an additional restriction. Check the service policy: s4m currently requires username/password.

Credential format: USER:PASS. s4m SOCKS5 (1080) and HTTP (3128) require username/password authentication. An IP allowlist on a destination is a separate policy and does not replace these credentials. Keep proxy credentials out of shared code and logs. If exposed, revoke or replace them in your account. Address-assignment topic: dedicated IP. A dedicated address does not remove credentials or guarantee a clean history. Related topic: IP reputation.

Proxy credentials work with the endpoint issued in your account, subject to service and account policies. Destination IP rules are separate. Related topics: IP allowlisting, dedicated IP. The current s4m service does not offer IP-only authentication or a combined client-IP allowlist mode. A destination IP allowlist is separate from s4m proxy authentication. It does not enable password-free access to the current s4m proxy service. Keep proxy credentials out of shared code and logs. If exposed, revoke or replace them in your account.