Deploy banner not displayed when updating details of a Plan

[exalate-issue-sync]

Describe the bug :

When we edit a OAuth2 plan, in this case we add a required scope, after we save the modification of the plan, we do not get a 'deploy API' so that we can deploy the API, and for this reason the changes of the plan do not take effect, which initially led us to believe that this was a security concern.

To Reproduce :

Steps to reproduce the behaviour:

1. Create a simple API
2. You can create a resource just for the sake of creating an OAuth2 Plan
3. Create an OAuth2 plan.
4. Now edit the plan, change, enable check scopes and add a required scope, in my case I added openid.

Expected behaviour :

After I save the plan configuration I would expect to see 'deploy API' for the changes to take effect, otherwise my API would still validate tokens without scopes, because the required scopes I added are not taken into consideration.

Current behaviour :

When I click on save for the OAuth2 plan, notting appears and I have to go to policy studio and change something minor and deploy the API.

Desktop :

• Environment: [4.1.0 & 4.1.3]
• Browser [Chrome]

[exalate-issue-sync]

This issue will be fixed in versions 4.0.14, 4.2.0, 4.1.5