This guide will help you understand what the Proxy Authentication method is and the different ways geonode provides to authenticate it.

​
What is Proxy Authentication?

Proxy authentication is a way to verify your identity before accessing a proxy server. It helps keep your connection secure and ensures only authorized users can use the proxy. Geonode provides two ways to authenticate:
  1. Using a username and password (Basic Authentication)
  2. Whitelisting your IP address (IP Authentication)
Each method has its advantages, depending on your use case.

​
1. Authenticating with Username and Password (Basic Authentication)

This method requires you to send your Geonode proxy username and password with every request. Many applications, APIs, and automation tools support this authentication method.

​
How Basic Authentication Works

  1. Format your credentials as: 
    username:password
  2. Convert this string to Base64 format (for security).
  3. Add the encoded credentials to your request header like this: 
    Authorization: Basic BASE64_ENCODED_STRING
➡️ For a full setup guide, check: Set Up Proxy Authentication in API

​
2. Authenticating with IP Whitelisting

IP whitelisting allows you to skip entering your username and password by authorizing a specific IP address to access the proxy. ➡️What is IP Whitelisting?

​
When to use IP Whitelisting

  • You have a static IP and want seamless authentication.
  • You are automating tasks and don’t want to include credentials in every request.
  • You want better security by restricting access to trusted IPs.
➡️ Learn How to Whitelist Your IP Address

​
Choosing the Right Authentication Method

Authentication MethodBest ForRequires Credentials?
Username & PasswordMost API calls, scripts, and browser extensions✅ Yes
IP WhitelistingTrusted networks, automation, and security-focused users❌ No

​
Final Tips

  • Use Username & Password for flexible authentication across different devices.
  • Use IP Whitelisting if you have a static IP and want to avoid entering credentials.
  • Always ensure your authentication details are kept secure and not exposed in scripts or public repositories.