Prettify SSO login links

[jeremystretch]

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.

Database changes

No response

External dependencies

No response

[jeremystretch]

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

[oasys]

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.

[jeremystretch]

@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.