Remove django-simple-sso #467

New Issue

mpeltriaux · 2025-01-24T15:29:09+01:00

mpeltriaux commented

2025-01-24 15:29:09 +01:00

Status quo

Back in the day django-simple-sso has been used to implement SSO capabilities, until OAuth2 replaced it somewhere in early 2024 due to discontinuing of the package.

Currently there is always a hint message on missing migrations from this package whenever a new version of the project will be deployed:

Operations to perform:
  Apply all migrations: admin, api, auth, codelist, compensation, contenttypes, ema, intervention, konova, news, sessions, sso_server, user
Running migrations:
  No migrations to apply.
  Your models in app(s): 'sso_server' have changes that are not yet reflected in a migration, and so won't be applied.
  Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.

This is due to the fact, the maintainer did not include the latest migrations by themselve.

However, due to migrations the package could not easily be removed from the project so far.

ToDo

Get rid of related tables
Get rid of related migrations
Get rid of migration dependencies
Get rid of package dependency
Test everything
1. Problems are not to be expected, since there is no usage of django-simple-sso anymore on the project

# Status quo Back in the day `django-simple-sso` has been used to implement SSO capabilities, until OAuth2 replaced it somewhere in early 2024 due to discontinuing of the package. Currently there is always a hint message on missing migrations from this package whenever a new version of the project will be deployed: ``` Operations to perform: Apply all migrations: admin, api, auth, codelist, compensation, contenttypes, ema, intervention, konova, news, sessions, sso_server, user Running migrations: No migrations to apply. Your models in app(s): 'sso_server' have changes that are not yet reflected in a migration, and so won't be applied. Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them. ``` This is due to the fact, the maintainer did not include the latest migrations by themselve. However, due to migrations the package could not easily be removed from the project so far. # ToDo 1. Get rid of related tables 1. Get rid of related migrations 1. Get rid of migration dependencies 1. Get rid of package dependency 1. Test everything 1. Problems are not to be expected, since there is no usage of `django-simple-sso` anymore on the project

mpeltriaux self-assigned this 2025-01-24 15:29:12 +01:00

mpeltriaux commented

2025-01-24 16:20:49 +01:00

Merged in #468

Dropped rest of dependency linkage. django-simple-sso migration linkage seem to be already removed from project migrations.

Will be deployed on test server and old tables (from the removed package) will be deleted.

Merged in #468 Dropped rest of dependency linkage. `django-simple-sso` migration linkage seem to be already removed from project migrations. Will be deployed on test server and old tables (from the removed package) will be deleted.

mpeltriaux commented

2025-01-24 16:27:41 +01:00

Deployment on test server done and looks fine. DB Tables sso_server_token and sso_server_consumer has been successfully removed from database.

Close this issue, when deployment on production server has been finished properly.

Deployment on test server done and looks fine. DB Tables `sso_server_token` and `sso_server_consumer` has been successfully removed from database. Close this issue, when deployment on production server has been finished properly.

mpeltriaux commented

2025-03-14 10:45:54 +01:00

Deployment onproduction server has been finished in early week of march.

mpeltriaux closed this issue

2025-03-14 10:45:54 +01:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: IT-Naturschutz/konova#467