Auth0 Logs Omit IP Address Contained in auth0-forwarded-for Header

Overview

The auth0-forwarded-for header value fails to appear in Auth0 dashboard logs after configuration for Resource Owner Password Grant (ROPG) authentication flows. Auth0 ignores this header for unauthenticated clients or when the client lacks explicit configuration to trust the header. Configure the client to use a valid token endpoint authentication method and enable the trust setting to capture the correct IP address.

Applies To

  • Auth0
  • Resource Owner Password Flow (ROPG)
  • auth0-forwarded-for Header

Cause

Auth0 ignores the auth0-forwarded-for header for unauthenticated clients, such as Single Page Applications (SPAs) or native applications that cannot provide a client secret. Auth0 also ignores the header if the client lacks explicit configuration to trust it.

Solution

What configuration allows the client to trust the auth0-forwarded-for header?

Configure the client application to use a valid token endpoint authentication method and enable the trust setting in the advanced OAuth settings.

  1. Open the Auth0 dashboard and navigate to the application settings.
  2. Verify the application uses a Token Endpoint Authentication Method other than None.
  3. Navigate to Credentials, and then scroll down to Advanced.
  4. Enable the Trust Token Endpoint IP Header setting.

 

NOTE: If the client lacks this configuration, Auth0 ignores the header and logs the actual IP address that makes the call to /oauth/token for anomaly detection.

 

Related References

Recommended content

No recommended content found...