anchor.diff:  REST endpoints and configuring to authenticate against an OAUTH backend (_i.e: UAA/SSO running on Cloud Foundry_), please
   review the security section from the core http://docs.spring.io/spring-cloud-dataflow/docs/{scdf-core-version}/reference/html/getting-started-security.html[reference guide]. The security configurations can be configured in `dataflow-server.yml` or passed as environment variables through `cf set-env` commands.
   
  -[[getting-started-app-names-cloud-foundry]]
  -== Application Names and Prefixes
  -
  -To help avoid clashes with routes across spaces in Cloud Foundry, a naming strategy to provide a random prefix to a
  -deployed application is available and is enabled by default. The https://github.com/spring-cloud/spring-cloud-deployer-cloudfoundry#application-name-settings-and-deployments[default configurations]
  -are overridable and the respective properties can be set via `cf set-env` commands.
  -
  -For instance, if you'd like to disable the randomization, you can override it through:
  -
  -```
  -cf set-env dataflow-server SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_STREAM_ENABLE_RANDOM_APP_NAME_PREFIX false
  -```
  -
  -=== Using Custom Routes
  -
  -As an alternative to random name, or to get even more control over the hostname used by the deployed apps, one can use
  -custom deployment properties, as such:
  -
  -[[source]
  -----
  -dataflow:>stream create foo --definition "http | log"
  -
  -dataflow:>stream deploy foo --properties "app.http.spring.cloud.deployer.cloudfoundry.domain=mydomain.com,
  -                                          app.http.spring.cloud.deployer.cloudfoundry.host=myhost,
  -                                          app.http.spring.cloud.deployer.cloudfoundry.route-path=my-path"
  -----
  -
  -This would result in the `http` app being bound to the URL `http://myhost.mydomain.com/my-path`. Note that this is an
  -example showing *all* customization options available. One can of course only leverage one or two out of the three.
  -
   [[getting-started-security-cloud-foundry]]
  -== Authentication and Cloud Foundry
  +=== Authentication and Cloud Foundry
   
   When deploying Spring Cloud Data Flow to Cloud Foundry, you can take advantage of the
    https://github.com/pivotal-cf/spring-cloud-sso-connector[_Spring Cloud Single Sign-On Connector_],
  
positive.code: dataflow:>task launch mytask
  ```
  
  You will see the year `2016` printed in the logs. The execution status of the task is stored
  in the database and you can retrieve information about the task execution using the shell commands
  `task execution list` and `task execution status --id <ID_OF_TASK>` or though the Data Flow UI.
  
  
negative.code: 
  Simply set `security.basic.enabled` to `true` and in Cloud Foundry bind the SSO
  service to your Data Flow Server app and SSO will be enabled.
  
  [[getting-started-app-names-cloud-foundry]]
  == Application Names and Prefixes
  
  To help avoid clashes with routes across spaces in Cloud Foundry, a naming strategy to provide a random prefix to a
  deployed application is available and is enabled by default. The https://github.com/spring-cloud/spring-cloud-deployer-cloudfoundry#application-name-settings-and-deployments[default configurations]
  are overridable and the respective properties can be set via `cf set-env` commands.
  
  For instance, if you'd like to disable the randomization, you can override it through:
  
  ```
  cf set-env dataflow-server SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_STREAM_ENABLE_RANDOM_APP_NAME_PREFIX false
  ```
  
  === Using Custom Routes
  
  As an alternative to random name, or to get even more control over the hostname used by the deployed apps, one can use
  custom deployment properties, as such:
  
  [[source]
  ----
  dataflow:>stream create foo --definition "http | log"
  
  dataflow:>stream deploy foo --properties "app.http.spring.cloud.deployer.cloudfoundry.domain=mydomain.com,
                                            app.http.spring.cloud.deployer.cloudfoundry.host=myhost,
                                            app.http.spring.cloud.deployer.cloudfoundry.route-path=my-path"
  ----
  
  This would result in the `http` app being bound to the URL `http://myhost.mydomain.com/my-path`. Note that this is an
  example showing *all* customization options available. One can of course only leverage one or two out of the three.
  
  == Configuration Reference
  
  