I found a quick & easy workaround for this issue that only adds a couple of steps to test different environments.
1. Create your Dev/Staging environment properties using the Environments utility (you've probably already done this).
2. From the Environments utility, save each environment's set of properties to the property file you are creating and name the file according to the environment (DevProps or StgProps).
3. Go to your project and set the environment dropdown to Default Environment.
4. Go to your project's project level and import the Dev properties file you saved to the project (be sure Create Missing Properties is checked). Your whole project will now be aimed at dev, and the Auth tab will retain the Authorization Type you first set up and all options will be enabled. Note: for my setup, I imported them to the Custom Properties tab.
5. To test on Staging, leave the environment dropdown set to Default Environment. Import the Staging properties to the project level. Your project will now be aimed at staging, and the Auth tab will still work properly.
Switching environments will now be a matter of simply importing the dev or staging properties files at the project level.
Note: If you add new environment properties, be sure to still do that using the Environments utility and save off new Dev/Stg properties files from the utility (I would just overwrite the existing *Props file).
If you end up needing to roll this into a CI/CD system, you could simply clone the project to make a Dev and Staging version of it until Smartbear fixes the Auth Tab Environment Switching issue.
Once SmartBear fixes the issue, you can simply start using the Environments dropdown again as normal.
This is working for my team, if anyone has a better idea, please share.
