Update scope aliases example

Author: MarcialRosales

docs/oauth2-examples/index.md

@@ -531,6 +531,7 @@ make curl-with-token URL=http://localhost:15672/api/overview TOKEN=$(bin/jwt_tok
 ### Using Scope Aliases {#using-scope-aliases}
 
 This example demonstrates how to use custom scopes with RabbitMQ. 
+
 **UAA** identity provider has been configured with two clients (`producer_with_roles`
 and `consumer_with_roles`) with the following custom scopes:
   `producer_with_roles` with 

docs/oauth2.md

@@ -139,7 +139,7 @@ In chronological order, here is the sequence of events that occur when a client
 | `auth_oauth2.resource_server_type`         | The Resource Server Type required when using [Rich Authorization Request](#rich-authorization-request) token format
 | `auth_oauth2.additional_scopes_key`        | Configure the plugin to look for scopes in other fields (maps to `additional_rabbitmq_scopes` in the old format). |
 | `auth_oauth2.scope_prefix`                 | [Configure the prefix for all scopes](#scope-prefix). The default value is `auth_oauth2.resource_server_id` followed by the dot `.` character. 
-| `auth_oauth2.scope_aliases`                | [Configure scope aliases](#scope-aliases). 
+| `auth_oauth2.scope_aliases`                | [Configure scope aliases](#scope-aliases). See this [example](oauth2-examples#using-scope-aliases).
 | `auth_oauth2.preferred_username_claims`    | [List of the JWT claims](#preferred-username-claims) to look for the username associated with the token.
 | `auth_oauth2.default_key`                  | ID of the default signing key.
 | `auth_oauth2.signing_keys`                 | Paths to the [signing key files](#signing-key-files).
@@ -194,34 +194,33 @@ auth_oauth2.scope_prefix = ''
 An scope alias is a mapping between a custom scope and a RabbitMQ's scope. A custom
 scope is any scope which is not recogonized by RabbitMQ. 
 
-Scope aliases are necessary when you can create RabbitMQ scopes in your 
-identity provider. Instead you have to name scopes following a format which is not
+Scope aliases are necessary when you cannot create RabbitMQ scopes in your 
+identity provider. Instead you have to name them following a format which is not
 recognizable by RabbitMQ. 
 
 For instance, say you have these two roles in your identity provider:
   - `admin`. 
   - `developer`.
-An OAuth token may carry those roles in the claim `scope` or in the claim `roles`. 
-Either way you want to map those roles to the following RabbitMQ scopes:
+  
+Also say that you want to map those roles to the following RabbitMQ scopes:
   - `admin` to `rabbitmq.tag:administrator rabbitmq.read:*/` 
   - `developer` to `rabbitmq.tag:management rabbitmq.read:*/* rabbitmq.write:*/* rabbitmq.configure:*/*`
 
 You configure the scope aliases as follows. The mapping can be 1:1 or 1:many:
 ```ìni 
 # ...
-auth_oauth2.scope_prefix = rabbitmq.
 auth_oauth2.scope_aliases.admin = rabbitmq.tag:administrator rabbitmq.read:*/
 auth_oauth2.scope_aliases.developer = rabbitmq.tag:management rabbitmq.read:*/* rabbitmq.write:*/* rabbitmq.configure:*/*
 # ...
 ```
 
 Sometimes, the alias is not made of a single word but instead it uses special characters
-and symbols such as `api://admin` or `api://developer`. In those cases, you can configure the scope aliases as follows:
+and symbols including the separator character `.`. In those cases, you can configure the scope aliases as follows:
+```ìni 
 # ...
-auth_oauth2.scope_prefix = rabbitmq.
 auth_oauth2.scope_aliases.1.alias = api://admin 
 auth_oauth2.scope_aliases.1.scope = rabbitmq.tag:administrator rabbitmq.read:*/
-auth_oauth2.scope_aliases.2.alias = api://developer 
+auth_oauth2.scope_aliases.2.alias = api://developer.All
 auth_oauth2.scope_aliases.2.scope = rabbitmq.tag:management rabbitmq.read:*/* rabbitmq.write:*/* rabbitmq.configure:*/*
 # ...
 ```