Username / password
Primary access method on supported Mobile, Residential, and Corporate endpoints.
Access
Username/password and IP allowlisting for Proxy Grove
Explore authentication options that help businesses and technical teams connect to proxy infrastructure according to their workflow requirements.
Overview
Authentication is how your clients prove they may use a proxy endpoint. Proxy Grove supports username/password on supported products and may offer IP allowlisting depending on your plan.
Store credentials in environment variables or a secrets manager. Never commit them to source control or share them in public channels.
Documentation and Resources cover configuration patterns for common HTTP clients and automation tools.
Authentication methods
IP allowlisting
Where offered, restrict access to approved server or office IPs.
Account access
Manage who on your team can create and rotate credentials.
Developer workflows
Wire auth into CI, scripts, and apps with clear configuration.
Real-world use cases
Connection configuration
Set host, port, and credentials in your HTTP client.
Server allowlists
Lock proxy use to known egress IPs when available.
Team onboarding
Share setup docs without sharing secrets in chat.
Automation jobs
Inject credentials from your secrets store at runtime.
Configuration tips
- Prefer secrets managers over hard-coded credentials.
- Rotate credentials if they may have been exposed.
- Confirm allowlisting support on your plan before relying on it.
Relevant Proxy Grove products
Authentication patterns apply across the official product catalog.
Helpful links
Credentials vs allowlisting in real stacks
Username/password auth travels with the request and works well for laptops, containers, and changing egress IPs.
IP allowlisting fits fixed office or cloud runner IPs when you want fewer secrets in application config.
Many teams use both: allowlisting for servers, credentials for ad-hoc tools. Neither changes the fact that you still buy Mobile, Residential, or Corporate first.
- Never commit dashboard passwords to git.
- After rotating a password, update every worker that still holds the old value.
- If auth fails, verify protocol and host/port before assuming a network outage.
- Read the auth comparison article for a side-by-side walkthrough.
Migration tips
- When moving from credentials to allowlisting, keep credentials active until every worker is updated.
- When rotating passwords, deploy env updates and restart workers in the same change window.
- Test both HTTP and SOCKS5 after auth changes if your stack uses both.
- Record who owns each credential set in your runbook.
Frequently asked questions
Username/password is primary on supported endpoints. IP allowlisting may be available depending on your plan.
Use environment variables or a secrets manager. Never commit credentials to git or paste them into public tickets.
Yes—most HTTP libraries accept proxy host, port, and credentials from configuration or environment.
See Documentation and the Resources hub for configuration guidance.
Details can vary by product and plan. Check the product page and docs for the endpoint you use.