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

Prettify SSO login links #6349

New Issue
Closed
opened 2025-12-29 19:39:43 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:39:43 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Apr 13, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.2.0

Feature type

New functionality

Proposed functionality

Display a proper name (and possibly logo?) for any configured remote authentication backend. These could be stored in a static mapping. For example:

AUTH_BACKENDS = {
    'azuread-oauth2': {
        'name': 'Microsoft Azure AD',
        'logo': 'path/to/logo.png',
    }
}

The login template would attempt to resolve these attributes for the configured backend and render accordingly.

Use case

The current SSO login link, while functional, is rather spartan and conveys only the name of the configured backend. A proper name for the authentication service would be more user-friendly.

netbox_sso_login

Database changes

No response

External dependencies

No response

Originally created by @jeremystretch on GitHub (Apr 13, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.2.0 ### Feature type New functionality ### Proposed functionality Display a proper name (and possibly logo?) for any configured remote authentication backend. These could be stored in a static mapping. For example: ``` AUTH_BACKENDS = { 'azuread-oauth2': { 'name': 'Microsoft Azure AD', 'logo': 'path/to/logo.png', } } ``` The login template would attempt to resolve these attributes for the configured backend and render accordingly. ### Use case The current SSO login link, while functional, is rather spartan and conveys only the name of the configured backend. A proper name for the authentication service would be more user-friendly. ![netbox_sso_login](https://user-images.githubusercontent.com/13487278/163268859-d5164cab-6c41-4d5a-8ad7-8220b7a70c0b.png) ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:39:43 +01:00
adam closed this issue 2025-12-29 19:39:43 +01:00
adam commented 2025-12-29 19:39:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 14, 2022):

Opened python-social-auth/social-core#680 to see if there's any interest in defining canonical user-friendly backend names upstream.

@jeremystretch commented on GitHub (Apr 14, 2022): Opened python-social-auth/social-core#680 to see if there's any interest in defining canonical user-friendly backend names upstream.
adam commented 2025-12-29 19:39:44 +01:00
Author
Owner
Copy Link

@oasys commented on GitHub (Apr 14, 2022):

In my experience, many organizations will "brand" their SSO with a custom name, as something like "Company Foo OneLogin". The result is that the application users may not even know what the backend actually is. Because of this, I'd certainly prefer that the name is still customizable within NetBox, even if python-social-auth provides a friendly name.

@oasys commented on GitHub (Apr 14, 2022): In my experience, many organizations will "brand" their SSO with a custom name, as something like "Company Foo OneLogin". The result is that the application users may not even know what the backend actually is. Because of this, I'd certainly prefer that the name is still customizable within NetBox, even if `python-social-auth` provides a friendly name.
adam commented 2025-12-29 19:39:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 14, 2022):

@oasys we could certainly look into that, however proposing a new configuration parameter(s) would need a separate FR. For now I'm just focused on improving the cosmetic appearance.

@jeremystretch commented on GitHub (Apr 14, 2022): @oasys we could certainly look into that, however proposing a new configuration parameter(s) would need a separate FR. For now I'm just focused on improving the cosmetic appearance.
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 status: accepted 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#6349
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?