Upgrading to DefectDojo Version 2.0.x

Follow the usual steps to upgrade as described above.

BEFORE UPGRADING

• If you are using SAML2 checkout the new documentaion and update you settings following the migration section. We replaced django-saml2-auth with djangosaml2.

AFTER UPGRADING

• Usual migration process (python manage.py migrate) try to migrate all endpoints to new format and merge duplicates.
• All broken endpoints (which weren’t possible to migrate) have red flag 🚩 in standard list of endpoints.
• Check if all your endpoints was migrated successfully, go to: https:///endpoint/migrate.
• Alternatively, this can be run as management command: docker-compose exec uwsgi ./manage.py endpoint_migration --dry-run
• When all endpoint will be fixed (there is not broken endpoint), press “Run migration” in https:///endpoint/migrate
• Or, you can run management command: docker-compose exec uwsgi ./manage.py endpoint_migration
• Details about endpoint migration / improvements in https://github.com/DefectDojo/django-DefectDojo/pull/4473

We decided to name this version 2.0.0 because we did some big cleanups in this release:

• Remove API v1 (#4413)

• Remove setup.bash installation method (#4417)

• Rename Finding.is_Mitigated field to Finding.is_mitigated (#3854)

• Remove everything related to the old tagging library (#4419)

• Remove S0/S1/S2../S5 severity display option (#4415)

• Refactor EndPoint handling/formatting (#4473)

• Upgrade to Django 3.x (#3632)

• PDF Reports removed (#4418)

• Hashcode calculation logic has changed. To update existing findings run:

  ./manage.py dedupe --hash_code_only.

If you’re using docker:

docker-compose exec uwsgi ./manage.py dedupe --hash_code_only.

This can take a while depending on your instance size.

• See release notes: https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.0.0

Endpoints#

• The usual migration process (python manage.py migrate) tries to migrate all endpoints to new format and merge duplicates.
• All broken endpoints (which weren’t possible to migrate) have a red flag 🚩 in the standard list of endpoints.
• Check if all your endpoints were migrated successfully, go to: https:///endpoint/migrate.
• Alternatively, this can be run as management command: docker-compose exec uwsgi ./manage.py endpoint_migration --dry-run
• When all endpoint are fixed (there is not broken endpoint), press “Run migration” in https:///endpoint/migrate
• Or, you can run management command: docker-compose exec uwsgi ./manage.py endpoint_migration
• Details about endpoint migration / improvements in https://github.com/DefectDojo/django-DefectDojo/pull/4473

Authorization#

The new authorization system for Products and Product Types based on roles is the default now. The fields for authorized users are not available anymore, but you can assign roles as described in Permissions. Users are migrated automatically, so that their permissions are as close as possible to the previous authorization:

• Superusers will still have all permissions on Products and Product Types, so they must not be changed.
• Staff users have had all permissions for all product types and products, so they will be get a global role as Owner.
• Product_Members and Product Type_Members will be added for authorized users according to the settings for the previous authorization:
  • The Reader role is set as the default.
  • If AUTHORIZED_USERS_ALLOW_STAFF is True, the user will get the Owner role for the respective Product or Product Type.
  • If AUTHORIZED_USERS_ALLOW_CHANGE or AUTHORIZED_USERS_ALLOW_DELETE is True, the user will get the Writer role for the respective Product or Product Type.

The new authorization is active for both UI and API. Permissions set via authorized users or via the Django Admin interface are no longer taken into account.

Please review the roles for your users after the upgrade to avoid an unintended permissions creep.