[bwang-icf]

JIRA Ticket:
BB2-5290

What Does This PR Do?

Upgrades oauthlib, django-oauth-toolkit, requests-oauthlib, and django-axes. Note that this does include a migration that will need to be ran prior to the deployment.

What Should Reviewers Watch For?

Any breaking portions of the site

Validation

Verified with local run and ensuring that oauthlib is at least version 4.0.0

What Security Implications Does This PR Have?

Please indicate if this PR does any of the following:

• Adds any new software dependencies
• Modifies any security controls
• Adds new transmission or storage of data
• Any other changes that could possibly affect security?

• Yes, one or more of the above security implications apply. This PR must not be merged without the ISSO or team
  security engineer's approval.

Any Migrations?

• Yes, there are migrations
  • The migrations should be run PRIOR to the code being deployed
  • The migrations should be run AFTER the code is deployed
  • There is a more complicated migration plan (downtime,
    etc)
• [] No migrations

[jimmyfagan]

@bwang-icf have you explored the migration steps here yet? when you do, just make sure you update the description with details about how the migration should be tested/deployed.

[bwang-icf]

@bwang-icf have you explored the migration steps here yet? when you do, just make sure you update the description with details about how the migration should be tested/deployed.

Yes, there will need to be a pre-migration happening. There was some cleanup I had to do since I had noticed some of the other migration files were effectively duplicating work. There are some new columns that upgrading django-oauth-toolkit brings, since we're going from 2.40 to 3.1.2 this time.