Allow the Django LOGIN_URL setting to be defined in configuration #8243

Closed
opened 2025-12-29 20:34:16 +01:00 by adam · 2 comments
Owner

Originally created by @slyngshede on GitHub (Jun 26, 2023).

NetBox version

v3.2.9

Feature type

Change to existing functionality

Proposed functionality

Allow the users to define the default Django LOGIN_URL variable in the Netbox configuration.

Use case

For organizations who deploy a single SSO provider it can confuse users that they are presented for both the username/password and the SSO option on the login page.

By allowing the LOGIN_URL to be defined in the configuration users can be redirect directly to the SSO provider, effectively hiding the non-functional username/password fields.

Database changes

None

External dependencies

None

Originally created by @slyngshede on GitHub (Jun 26, 2023). ### NetBox version v3.2.9 ### Feature type Change to existing functionality ### Proposed functionality Allow the users to define the default Django LOGIN_URL variable in the Netbox configuration. ### Use case For organizations who deploy a single SSO provider it can confuse users that they are presented for both the username/password and the SSO option on the login page. By allowing the LOGIN_URL to be defined in the configuration users can be redirect directly to the SSO provider, effectively hiding the non-functional username/password fields. ### Database changes None ### External dependencies None
adam added the type: featurepending closurestatus: under review labels 2025-12-29 20:34:16 +01:00
adam closed this issue 2025-12-29 20:34:17 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Oct 2, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Oct 2, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Nov 2, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Nov 2, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8243