anchor.diff:      ./gradlew :cloudfoundry-identity-uaa:war
       ```
   
  -1. Run the cf CLI `cf push APP-NAME -m 512M -p PATH-TO-WAR-FILE --no-start` command to push the app to <%= vars.product_short %>. Replace `APP-NAME` with a name for your UAA app, and `PATH-TO-WAR-FILE` with the path to the WAR file you created in the previous step. For example:
  +1. Run the cf CLI `cf push APP-NAME -m 512M -p PATH-TO-WAR-FILE --no-start` command to push the app to <%= vars.platform_name %>. Replace `APP-NAME` with a name for your UAA app, and `PATH-TO-WAR-FILE` with the path to the WAR file you created in the previous step. For example:
   
       ```
       cf push MYUAA -m 512M -p uaa/build/libs/cloudfoundry-identity-uaa-1.8.0.war --no-start
  
positive.code: 
  ### <a id='demo-hosted'></a> Use Remote UAA
  
  You use a UAA server that you pushed as an app to <%= vars.product_short %> in a similar way to one you run locally. You do not need app token encoding because you do not have the client secret.
  
  To access and use a UAA server that you pushed as an app to <%= vars.product_short %>:
  
  1. Follow the procedure in [Deploy UAA to <%= vars.product_short %>](#cf). 
  
  1. From the project base directory, run `curl -H "Accept: application/json" APP-FQDN/login` to query the external login endpoint about the system. Replace `APP-FQDN` with the fully qualified domain name (FQDN) of your app. For example:
  
  
negative.code:     * `PASSWORD` is your password.
      If you do not specify a username and password, the UAAC prompts you to supply them.
      <br><br>
      The `uaac token client get` command authenticates and obtains an access token from the server using the OAuth2 implicit grant, similar to the approach intended for a standalone client like the cf CLI. 
  
  
  ## <a id='integration'></a> Integration Tests
  