starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Login page by default (including some updates) #5463

New Issue
Closed
opened 2025-12-29 19:28:20 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:28:20 +01:00
Owner
Copy Link

Originally created by @EHRETic on GitHub (Oct 4, 2021).

NetBox version

v3.0.3

Feature type

New functionality

Proposed functionality

Hi,

When there is no logged on user, the default landing page is not the one with the login.
Giving the option (it is in my opinion good to let the choice) to choose the login page as a default would be a good update. It spares one click to login and feels more logic to first login, then have access to something 😉

Also, it would be nice to not display the internal server name & version in footer for security reasons if server is used externally and user is not logged in. Having this as an option would also be great.

Use case

  • default page to login --> spare one click and feel more standard
  • hide the server name/version --> gives less information about the system when no user is logged

Database changes

No response

External dependencies

No response

Originally created by @EHRETic on GitHub (Oct 4, 2021). ### NetBox version v3.0.3 ### Feature type New functionality ### Proposed functionality Hi, When there is no logged on user, the default landing page is not the one with the login. Giving the option (it is in my opinion good to let the choice) to choose the login page as a default would be a good update. It spares one click to login and feels more logic to first login, then have access to something 😉 Also, it would be nice to not display the internal server name & version in footer for security reasons if server is used externally and user is not logged in. Having this as an option would also be great. ### Use case - default page to login --> spare one click and feel more standard - hide the server name/version --> gives less information about the system when no user is logged ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:28:20 +01:00
adam closed this issue 2025-12-29 19:28:20 +01:00
adam commented 2025-12-29 19:28:20 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 4, 2021):

If you want to force people to log into the UI, you can set LOGIN_REQUIRED = True in configuration.py. Otherwise, the home view will be displayed and they will have access to any views allowed under EXEMPT_VIEW_PERMISSIONS.

@jeremystretch commented on GitHub (Oct 4, 2021): If you want to force people to log into the UI, you can set `LOGIN_REQUIRED = True` in `configuration.py`. Otherwise, the home view will be displayed and they will have access to any views allowed under `EXEMPT_VIEW_PERMISSIONS`.
adam commented 2025-12-29 19:28:21 +01:00
Author
Owner
Copy Link

@EHRETic commented on GitHub (Oct 4, 2021):

LOGIN_REQUIRED

Hi,

Sorry for my misunderstanding and the "not trying", I didn't get the LOGIN_REQUIRED would actually do what I want.

But can we still consider the removal of server info as an extra optional security measure? 😉

@EHRETic commented on GitHub (Oct 4, 2021): > LOGIN_REQUIRED Hi, Sorry for my misunderstanding and the "not trying", I didn't get the LOGIN_REQUIRED would actually do what I want. But can we still consider the removal of server info as an extra optional security measure? 😉
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#5463
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?