Now that Orchestrator is up and running, we can start configuring it. We will configure Orchestrator to use SSO for authentication as well as an external database.
Wait! We did say that Orchestrator is preconfigured. So, what is already actually there ready to be used?
The Orchestrator Appliance comes with an embedded PostgreSQL database as well as a configured LDAP directory service. The LDAP contains the vcoadmin user that we just used to log in. In addition to this, Orchestrator has a self-signed packaged certificate and a 90-day trial license. Both of these items are stored in the embedded PostgreSQL database, which also means that these items have to be recreated when you use a new and empty external database.
What is not configured is any connection to the vSphere environment. We will do this in the next chapter. In this chapter, we will have a look at how one can replace the preconfigured database and authentication with...