REMOTE_AUTH_HEADER documentation unclear #4290

Closed
opened 2025-12-29 18:34:26 +01:00 by adam · 0 comments
Owner

Originally created by @mjuarez on GitHub (Nov 20, 2020).

Change Type

[ ] Addition
[X] Correction
[ ] Deprecation
[ ] Cleanup (formatting, typos, etc.)

Area

[ ] Installation instructions
[X] Configuration parameters
[ ] Functionality/features
[ ] REST API
[ ] Administration/development
[ ] Other

Proposed Changes

Documentation for usage of REMOTE_AUTH_HEADER is unclear that desired request header needs to be prefixed with HTTP_ in configuration. For example, to use the request header X-Remote-User it needs to be set to HTTP_X_REMOTE_USER.

Originally created by @mjuarez on GitHub (Nov 20, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. Please indicate the nature of the change by placing an X in one of the boxes below. --> ### Change Type [ ] Addition [X] Correction [ ] Deprecation [ ] Cleanup (formatting, typos, etc.) ### Area [ ] Installation instructions [X] Configuration parameters [ ] Functionality/features [ ] REST API [ ] Administration/development [ ] Other <!-- Describe the proposed change(s). --> ### Proposed Changes Documentation for usage of `REMOTE_AUTH_HEADER` is unclear that desired request header needs to be prefixed with `HTTP_` in configuration. For example, to use the request header `X-Remote-User` it needs to be set to `HTTP_X_REMOTE_USER`.
adam added the status: acceptedtype: documentation labels 2025-12-29 18:34:26 +01:00
adam closed this issue 2025-12-29 18:34:27 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4290