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

Implement a Banner / Disclaimer for Login page #1219

New Issue
Closed
opened 2025-12-29 16:30:10 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:30:10 +01:00
Owner
Copy Link

Originally created by @AnythingOverIP on GitHub (Sep 14, 2017).

Issue type

[x ] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 3.x
  • NetBox version: 2.1.4

Description

A detailed description of the proposed functionality:
Please provide a way to add a login banner for the user to accept prior login. Either thru:

  • Some text being showed on the login page before the username/password field (accepting the disclaimer by filling credentials & clicking the login button).
    or
  • A first page the user as to accept prior getting the login page. Ideally it should allow markup or HTML language to make it even more flexible... The look & feel of the page could be similar to the 404.html page

I would see 3 ways to achieve it:

  1. Implement a way to allow the TOP_BANNER to be displayed on the login page only, and reuse that field for the banner.

  2. Add another variable like LOGIN_BANNER to be configured in configuration.py for the login page

  3. Have a variable available for modification in the Admin site. This would be even more flexible, allowing an application admin to modify this behavior without needing a System Admin to do so.

Don't hesitate to brainstorm or comment if you have a better approach :)

A use case for the new feature:
This would help us to accommodate the corporate IT policy without trying to modify pages manually (and have to redo it at upgrades)...
https://linux-audit.com/the-real-purpose-of-login-banners-on-linux/

It could also be used to advertise on the login page (i.e.: If you require access, please contact Mr X.)

A rough description of any necessary changes to the database schema:
I don't believe this would require any db work.

Any relevant third-party libraries which would be needed:
I don't believe this would require any libraries addition.

Originally created by @AnythingOverIP on GitHub (Sep 14, 2017). ### Issue type [x ] Feature request <!-- Requesting the implementation of a new feature --> [ ] Bug report <!-- Reporting unexpected or erroneous behavior --> [ ] Documentation <!-- Proposing a modification to the documentation --> ### Environment * Python version: 3.x * NetBox version: 2.1.4 ### Description **_A detailed description of the proposed functionality:_** Please provide a way to add a login banner for the user to accept prior login. Either thru: * Some text being showed on the login page before the username/password field (accepting the disclaimer by filling credentials & clicking the login button). or * A first page the user as to accept prior getting the login page. Ideally it should allow markup or HTML language to make it even more flexible... The look & feel of the page could be similar to the 404.html page I would see 3 ways to achieve it: 1. Implement a way to allow the TOP_BANNER to be displayed on the login page only, and reuse that field for the banner. 2. Add another variable like LOGIN_BANNER to be configured in configuration.py for the login page 3. Have a variable available for modification in the Admin site. This would be even more flexible, allowing an application admin to modify this behavior without needing a System Admin to do so. Don't hesitate to brainstorm or comment if you have a better approach :) **_A use case for the new feature:_** This would help us to accommodate the corporate IT policy without trying to modify pages manually (and have to redo it at upgrades)... https://linux-audit.com/the-real-purpose-of-login-banners-on-linux/ It could also be used to advertise on the login page (i.e.: If you require access, please contact Mr X.) **_A rough description of any necessary changes to the database schema:_** I don't believe this would require any db work. **_Any relevant third-party libraries which would be needed:_** I don't believe this would require any libraries addition.
adam added the type: feature label 2025-12-29 16:30:10 +01:00
adam closed this issue 2025-12-29 16:30:10 +01:00
adam commented 2025-12-29 16:30:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 15, 2017):

Added a BANNER_LOGIN setting similar to BANNER_TOP and BANNER_BOTTOM.

@jeremystretch commented on GitHub (Sep 15, 2017): Added a `BANNER_LOGIN` setting similar to `BANNER_TOP` and `BANNER_BOTTOM`.
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#1219
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?