Missing example on REMOTE_AUTH_*** parameters with a generic Oauth provider #3851

Closed
opened 2025-12-29 18:31:36 +01:00 by adam · 1 comment
Owner

Originally created by @strus38 on GitHub (Jul 10, 2020).

Change Type

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

Area

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

The newly available parameters for REMOTE_AUTH are nice, but it lacks details for implementation. It would be very nice to add an example based on a generic Oauth provider like Keycloak.

I am trying to implement that for a netbox running on kubernetes with Keycloak/ Keycloak gateway using OIDC to protect it. Of course, right now, without those headers, I can protect the access to the netbox endpoint, and it works, but then I fall back on the login screen of netbox, which is pointless.
Trying to use the REMOTE_AUTH parameters is not clear, especially for the REMOTE_AUTH_HEADER, which I cannot understand.

Thanks.

Originally created by @strus38 on GitHub (Jul 10, 2020). ### Change Type [X] Addition [ ] Correction [ ] Deprecation [ ] Cleanup (formatting, typos, etc.) ### Area [ ] Installation instructions [X] Configuration parameters [ ] Functionality/features [ ] REST API [ ] Administration/development [ ] Other <!-- Describe the proposed change(s). --> The newly available parameters for REMOTE_AUTH are nice, but it lacks details for implementation. It would be very nice to add an example based on a generic Oauth provider like Keycloak. <!-- Why I am asking --> I am trying to implement that for a netbox running on kubernetes with Keycloak/ Keycloak gateway using OIDC to protect it. Of course, right now, without those headers, I can protect the access to the netbox endpoint, and it works, but then I fall back on the login screen of netbox, which is pointless. Trying to use the REMOTE_AUTH parameters is not clear, especially for the REMOTE_AUTH_HEADER, which I cannot understand. Thanks.
adam closed this issue 2025-12-29 18:31:36 +01:00
Author
Owner

@jeremystretch commented on GitHub (Jul 10, 2020):

Providing details on how to configure the feature to work with any specific provider is outside the documentation's scope. Please consider posting to our discussion list if you'd like assistance with the configuration.

@jeremystretch commented on GitHub (Jul 10, 2020): Providing details on how to configure the feature to work with any specific provider is outside the documentation's scope. Please consider posting to our discussion list if you'd like assistance with the configuration.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3851