anchor.diff:        }
         ```
       The `dashboard_client` field is a hash containing three fields:
  -    - `id` is the unique identifier for the OAuth client that will be created for your service dashboard on the token server (UAA), and will be used by your dashboard to authenticate with the token server (UAA). If the client id is already taken, <%= vars.platform_name %> will return an error when registering or updating the broker.
  +    - `id` is the unique identifier for the OAuth client that will be created for your service dashboard on the token server (UAA), and will be used by your dashboard to authenticate with the token server (UAA). If the client id is already taken, <%= vars.app_runtime_abbr %> will return an error when registering or updating the broker.
       - `secret` is the shared secret your dashboard will use to authenticate with the token server (UAA).
       - `redirect_uri` is used by the token server as an additional security precaution. UAA will not provide a token if the callback URL declared by the service dashboard doesn't match the domain name in `redirect_uri`. The token server matches on the domain name, so any paths will also match; e.g. a service dashboard requesting a token and declaring a callback URL of `http://p-mysql.example.com/manage/auth` would be approved if `redirect_uri` for its client is `http://p-mysql.example.com/`.
   
  
positive.code: 
  ### <a name='oauth2-flow'></a>OAuth Flow ###
  
  When a user navigates to the URL from `dashboard_url`, the service dashboard should initiate the OAuth login flow. A summary of the flow can be found in [section 1.2 of the OAuth RFC](http://tools.ietf.org/html/rfc6749#section-1.2). OAuth expects the presence of an [Authorization Endpoint](http://tools.ietf.org/html/rfc6749#section-3.1) and a [Token Endpoint](http://tools.ietf.org/html/rfc6749#section-3.2). In <%= vars.platform_name %>, these endpoints are provided by the UAA. Clients can discover the location of UAA from Cloud Controller's info endpoint; in the response the location can be found in the `token_endpoint` field.
  
  ```
  $ curl api.example.com/info
  
negative.code: ## <a name='restrictions'></a>Restrictions ##
  
   * UAA clients are scoped to services.  There must be a `dashboard_client` entry for each service that uses SSO integration.
   * Each `dashboard_client id` must be unique across the <%= vars.app_runtime_abbr %> deployment.
  
  ## <a name="resources"></a>Resources ##
  
  