We have many classes that calls capabilities API before the user entered keys are saved. This means they will use the old saved keys instead of new user entered keys. This will cause issues like:
401 unauthorized access
Expired keys
To avoid such issue we first get the user entered keys from $_POST so that other classes calls the capabilities API from the user entered keys.
1. Objective
Fix the issue of user unable to set new keys when their old keys are expired.
Jira Ticket: #453
2. Description of change
We have many classes that calls capabilities API before the user entered keys are saved. This means they will use the old saved keys instead of new user entered keys. This will cause issues like:
To avoid such issue we first get the user entered keys from $_POST so that other classes calls the capabilities API from the user entered keys.
3. Quality assurance
🔧 Environments: