Change Details

Currently netbox uses django-ca-ng to preform cas authentications. this is added via a cherry-pick we apply to every upgrade· however since we implemented this netbox has added support for djangi-social-auth. As such it makes senses for use to try and migrate to that. Currently the plug-in dose not support the CAS protocol but dose support OAuth, OpenID and a bunch of [[ https://python-social-auth.readthedocs.io/en/latest/intro.html#auth-providers | providers ]]. I suggest that we either work on adding cas support to python-social-app or migrate netbox to use OpenID connect or OAuth2

Currently netbox uses django-ca-ng to preform cas authentications. this is added via a cherry-pick we apply to every upgrade· however since we implemented this netbox has added support for djangi-social-auth. As such it makes senses for use to try and migrate to that. Currently the plug-in dose not support the CAS protocol but dose support OAuth, OpenID and a bunch of [[ https://python-social-auth.readthedocs.io/en/latest/intro.html#auth-providers | providers ]]. I suggest that we either work on adding cas support to python-social-app or migrate netbox to use OpenID connect or OAuth2 Some history on netbox sso and cas T244849

Currently netbox uses django-ca-ng to preform cas authentications. this is added via a cherry-pick we apply to every upgrade· however since we implemented this netbox has added support for djangi-social-auth. As such it makes senses for use to try and migrate to that. Currently the plug-in dose not support the CAS protocol but dose support OAuth, OpenID and a bunch of [[ https://python-social-auth.readthedocs.io/en/latest/intro.html#auth-providers | providers ]]. I suggest that we either work on adding cas support to python-social-app or migrate netbox to use OpenID connect or OAuth2 Some history on netbox sso and cas T244849