anchor.diff:  :page-folder: am/installation-guide
   :page-layout: am
   
  -NOTE: For all these breaking changes, the Migration Guide can be found link:/am/current/am_installguide_migration.html[here].
  +NOTE: To take advantage of these new features and incorporate these breaking changes, **use the migration guide available link:/am/current/am_installguide_migration.html[here]**.
   
  -== Management REST API : Application scopes
  +== Management REST API: Application Scopes
   
  -Until now, the application oauth settings contained multiple collections about scopes:
  +Until now, the application OAuth settings contained multiple collections about scopes, such as:
   
  -* scopes: a list with all scopes authorized for the application
  -* defaultScopes: a list of scopes added as default one if the authorize request doesn't specify a list of scopes
  -* scopeApprovals: a map to specify the amount of time (in seconds) that a scope is considered as accepted per the enduser
  +* scopes: a list with all scopes authorized for the application.
  +* defaultScopes: a list of scopes added as default if the authorized request doesn't specify a list of scopes. 
  +* scopeApprovals: a map to specify the amount of time (in seconds) that a scope is considered acceptable by the end user. 
   
   [source,json]
   ----
  
positive.code: }
  ----
  
  Because there are more and more settings related to a scope, the oauth settings for an application has be refactor to provide a single list `scopeSettings` containing objects with scope settings. This object will have following attribtues: 
  
  * scope: the scope name
  * defautlScope : boolean to defined this scope as a default one if the authorize request doesn't specify a list of scopes
  * scopeApproval : the amount of time (in seconds) that a scope is considered as accepted per the enduser
  
  [source,json]
  ----
  
negative.code: ----
  
  
  If you are using the Management REST API directly, please make this change and adapt your application or scipts.
  