Hello,
Sorry if I am unclear, english isn't my mother tongue.
vCenter doesn't have to be in a domain. Actually, I even use the VCSA for ages (the new version is just what you need since the limitations are gone) which doesn't have to be part of a domain.
Composer doesn't have to be in a domain neither. You can install local MSDB (SQL Express is just fine even for huge pods but since huge pods surely already have a database server somewhere...) with SQL account for authentication, no need to be in a domain here.
Security Server can't be in a domain.
Connection Server MUST be in a domain. It is mandatory, you can't even install if you are not.
You'll also need a domain account for the composer to be able to add desktops to domain.
This is what is needed, now you have to put it in the right place in View configuration. When you declare your vCenter for instance, you only have to set the accounts needed to communicate with vCenter with enough rights (and rights have to be applied at ROOT level, not DATACENTER level), with composer with enough rights as well (typically, you'll use Composer server local administrator account). To configure correctly composer, you also need to declare the domain you'll compose into, this is where things can go wrong since composer must be able to resolve this domain, so my advice is to add domain DNS server (most of the time, DC) as a local DNS for domain resolution. Then, you'll need the domain account to be able to compose this domain;
